Alphabetize front page

[kbx81]

Description:

Organizes component listings after Sensor and Binary Sensor on the main page.

Related issue (if applicable): fixes

Pull request in esphome with YAML changes (if applicable): esphome/esphome#

Checklist:

• I am merging into next because this is new documentation that has a matching pull-request in esphome as linked above.
  or

• I am merging into current because this is a fix, change and/or adjustment in the current documentation and is not for a new component or feature.

• Link added in /index.rst when creating new documents for new components or cookbook.

[coderabbitai]

Walkthrough

The pull request introduces significant structural and content modifications to the index.rst file of the ESPHome documentation. It includes the renaming of several sections to better reflect their content, the addition of new sections for expanded functionalities, and the removal of outdated content. The overall organization of components has been refined to enhance user navigation and understanding, with an emphasis on clarity and current capabilities.

Changes

File

Change Summary

index.rst

- Renamed sections: Light Components to Alarm Control Panel Components, Audio DAC Components to Speaker Components, Media Player Components to Microphone Components, Climate Components to Home Assistant Components, Text Components to Text Sensor Components, Fan Components to Switch Components, Electromechanical to Valve Components. - Added new sections: Datetime Components, Media Player Components, Microphone Components, Energy/Solar Management, Electromechanical. - Removed outdated sections, including Output Components. - Updated text for clarity and readability.

Possibly related PRs

• Add a section about custom component deprecation #4247: This PR adds a section about custom component deprecation, which is directly related to the reorganization and clarification of components in the main PR.
• Add deadline for custom components #4446: This PR specifies the timeline for the deprecation of custom components, aligning with the main PR's focus on reorganizing and clarifying component documentation.

Suggested reviewers

• jesserockz
• frenck

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 1ddd7c9 and df84dba.

📒 Files selected for processing (1)

• index.rst (8 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

index.rst (1)

Pattern **: - Do not generate or add any sequence diagrams

🔇 Additional comments (2)

index.rst (2)

301-301: LGTM! Improved wording for sensor organization.

The change from "split into" to "organized into" is more professional and better reflects the intentional categorization of components.

Also applies to: 628-628

---

Line range hint 714-932: LGTM! Improved component organization and naming.

The reorganization of component sections achieves several improvements:

1. Alphabetical ordering makes navigation more intuitive
2. More accurate section names (e.g., "Speaker Components" instead of "Audio DAC Components")
3. Better categorization of related components

Also applies to: 934-1080

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[netlify]

✅ Deploy Preview for esphome ready!

Name	Link
🔨 Latest commit	df84dba
🔍 Latest deploy log	https://app.netlify.com/sites/esphome/deploys/67414f714cd71e000808ae63
😎 Deploy Preview	https://deploy-preview-4460--esphome.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.