Skip to content

Add Understanding boards in ESPHome guide#6744

Open
bdraco wants to merge 1 commit into
currentfrom
understanding-boards-guide
Open

Add Understanding boards in ESPHome guide#6744
bdraco wants to merge 1 commit into
currentfrom
understanding-boards-guide

Conversation

@bdraco
Copy link
Copy Markdown
Member

@bdraco bdraco commented Jun 5, 2026

Description

Revives #6743 (closed because it was opened from the fork's protected current branch) and adds the "Understanding boards in ESPHome" guide that the Device Builder's "I don't know what board I have" link points to.

The original page broke the build because the eight images were imported with hyphenated identifiers that are not valid JavaScript; this imports each with a camelCase identifier matching the other guides, adds alt text to the figures for accessibility, title cases the section headings, and switches internal links to relative paths. The first commit is the original work by @Erioldoesdesign; the cleanup is layered on top. Builds clean locally and the page was verified in the browser.

Related issue (if applicable): esphome/device-builder-frontend#114 (this is the page its "I don't know what board I have" link needs)

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

  • N/A

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 /src/content/docs/components/index.mdx when creating new documents for new components or cookbook.

@esphome esphome Bot added the current label Jun 5, 2026
@netlify
Copy link
Copy Markdown

netlify Bot commented Jun 5, 2026

Deploy Preview for esphome ready!

Name Link
🔨 Latest commit e2079cc
🔍 Latest deploy log https://app.netlify.com/projects/esphome/deploys/6a23533dfbd14800083dc221
😎 Deploy Preview https://deploy-preview-6744--esphome.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

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

@esphbot
Copy link
Copy Markdown

esphbot commented Jun 5, 2026

Previous review — superseded by a newer review below.

@bdraco bdraco force-pushed the understanding-boards-guide branch from e9420ab to cafa2c3 Compare June 5, 2026 21:31
@bdraco
Copy link
Copy Markdown
Member Author

bdraco commented Jun 5, 2026

@esphbot
Copy link
Copy Markdown

esphbot commented Jun 5, 2026

Previous review — superseded by a newer review below.

@esphbot
Copy link
Copy Markdown

esphbot commented Jun 5, 2026

Previous review — superseded by a newer review below.

@bdraco bdraco force-pushed the understanding-boards-guide branch from b69b9d7 to e23ce4d Compare June 5, 2026 22:07
@esphbot
Copy link
Copy Markdown

esphbot commented Jun 5, 2026

Previous review — superseded by a newer review below.

@bdraco bdraco force-pushed the understanding-boards-guide branch from e23ce4d to 0630add Compare June 5, 2026 22:16
@esphbot
Copy link
Copy Markdown

esphbot commented Jun 5, 2026

Previous review — superseded by a newer review below.

@bdraco bdraco force-pushed the understanding-boards-guide branch from 0630add to 69c3d12 Compare June 5, 2026 22:26
@bdraco bdraco marked this pull request as ready for review June 5, 2026 22:26
Copilot AI review requested due to automatic review settings June 5, 2026 22:26
@esphbot
Copy link
Copy Markdown

esphbot commented Jun 5, 2026

Previous review — superseded by a newer review below.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jun 5, 2026

Too much diff to scan? Review this PR in Change Stack to start with the highest-impact changes.

Review Change Stack

Warning

Review limit reached

@bdraco, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 3 minutes and 53 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 747a3de5-38fc-4f9a-b5ed-89029b90ee41

📥 Commits

Reviewing files that changed from the base of the PR and between c2ba04f and e2079cc.

⛔ Files ignored due to path filters (8)
  • src/content/docs/guides/images/board-variants-pill-list.png is excluded by !**/*.png
  • src/content/docs/guides/images/change-board-platform-dropdown.png is excluded by !**/*.png
  • src/content/docs/guides/images/create-a-new-project-fig-1.png is excluded by !**/*.png
  • src/content/docs/guides/images/generic-boards-examples.png is excluded by !**/*.png
  • src/content/docs/guides/images/i-dont-know-what-board-i-have-fig-1.png is excluded by !**/*.png
  • src/content/docs/guides/images/i-dont-know-what-board-i-have-fig-2.png is excluded by !**/*.png
  • src/content/docs/guides/images/i-dont-know-what-board-i-have-fig-3.png is excluded by !**/*.png
  • src/content/docs/guides/images/yaml-board-variant-screenshot.png is excluded by !**/*.png
📒 Files selected for processing (2)
  • src/content/docs/guides/index.mdx
  • src/content/docs/guides/understanding_boards.mdx

Walkthrough

Adds a new "Understanding Boards in ESPHome" guide and registers it in the guides index; the guide MDX includes frontmatter, Figure and image imports, sections on identifying boards, starting with generic variants, changing variants (UI/YAML), and "See Also" links.

Changes

Understanding Boards Guide

Layer / File(s) Summary
Register guide in index
src/content/docs/guides/index.mdx
The new "Understanding Boards in ESPHome" guide is added as a list entry linking to /guides/understanding_boards/.
New guide document and content
src/content/docs/guides/understanding_boards.mdx
A complete guide is created with frontmatter metadata, Figure component and image imports, introduction explaining ESPHome boards, step-by-step board identification instructions with figures, guidance on starting with generic variants and changing variants via the device navigator UI or YAML, and a "See Also" section linking related docs.

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and concisely describes the main change: adding a new guide about understanding boards in ESPHome.
Description check ✅ Passed The description is directly related to the changeset, explaining the guide's purpose, how it fixes build issues, and its connection to the Device Builder frontend.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch understanding-boards-guide

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@src/content/docs/guides/understanding_boards.mdx`:
- Line 103: Replace the user-facing phrase "drop down" with hyphenated
"drop-down" wherever it appears, starting with the sentence fragment "input
fields and places to type you should find a drop down that allows you to
select"; also update any related captions and alt text that use "drop down" to
maintain consistent UI terminology throughout the document
"understanding_boards.mdx".
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: fd31f6b2-3e3e-4040-be8d-e57ce5fec516

📥 Commits

Reviewing files that changed from the base of the PR and between 8eda4df and 69c3d12.

⛔ Files ignored due to path filters (8)
  • src/content/docs/guides/images/board-variants-pill-list.png is excluded by !**/*.png
  • src/content/docs/guides/images/change-board-platform-dropdown.png is excluded by !**/*.png
  • src/content/docs/guides/images/create-a-new-project-fig-1.png is excluded by !**/*.png
  • src/content/docs/guides/images/generic-boards-examples.png is excluded by !**/*.png
  • src/content/docs/guides/images/i-dont-know-what-board-i-have-fig-1.png is excluded by !**/*.png
  • src/content/docs/guides/images/i-dont-know-what-board-i-have-fig-2.png is excluded by !**/*.png
  • src/content/docs/guides/images/i-dont-know-what-board-i-have-fig-3.png is excluded by !**/*.png
  • src/content/docs/guides/images/yaml-board-variant-screenshot.png is excluded by !**/*.png
📒 Files selected for processing (2)
  • src/content/docs/guides/index.mdx
  • src/content/docs/guides/understanding_boards.mdx

Comment thread src/content/docs/guides/understanding_boards.mdx Outdated
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds a new “Understanding Boards in ESPHome” guide intended to support the ESPHome Device Builder flow (specifically the “I don't know what board I have” link), and makes it discoverable from the Guides index.

Changes:

  • Added a new guide page explaining how to identify boards/variants and how to change board selection in the UI/YAML.
  • Added the new guide to the Guides landing page list.

Reviewed changes

Copilot reviewed 2 out of 10 changed files in this pull request and generated 7 comments.

File Description
src/content/docs/guides/understanding_boards.mdx New guide content with figures/screenshots and internal links for identifying/changing board variants.
src/content/docs/guides/index.mdx Adds a nav entry so the new guide is discoverable from the Guides index.

Comment thread src/content/docs/guides/understanding_boards.mdx Outdated
Comment thread src/content/docs/guides/understanding_boards.mdx
Comment thread src/content/docs/guides/understanding_boards.mdx Outdated
Comment thread src/content/docs/guides/understanding_boards.mdx Outdated
Comment thread src/content/docs/guides/understanding_boards.mdx Outdated
Comment thread src/content/docs/guides/understanding_boards.mdx Outdated
Comment thread src/content/docs/guides/understanding_boards.mdx Outdated
@bdraco bdraco force-pushed the understanding-boards-guide branch from 69c3d12 to c2ba04f Compare June 5, 2026 22:35
@esphbot
Copy link
Copy Markdown

esphbot commented Jun 5, 2026

Previous review — superseded by a newer review below.

Copilot AI review requested due to automatic review settings June 5, 2026 22:40
@bdraco bdraco force-pushed the understanding-boards-guide branch from c2ba04f to 24af3f7 Compare June 5, 2026 22:40
@esphbot
Copy link
Copy Markdown

esphbot commented Jun 5, 2026

Previous review — superseded by a newer review below.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 2 out of 10 changed files in this pull request and generated 4 comments.

Comment thread src/content/docs/guides/understanding_boards.mdx Outdated
Comment thread src/content/docs/guides/understanding_boards.mdx Outdated
Comment thread src/content/docs/guides/understanding_boards.mdx Outdated
Comment thread src/content/docs/guides/understanding_boards.mdx Outdated
A guide that explains how to identify your board, what to do when you do
not have one yet, and how to change the board variant; linked from the
guides index and from the Device Builder board wizard.
@bdraco bdraco force-pushed the understanding-boards-guide branch from 24af3f7 to e2079cc Compare June 5, 2026 22:52
@esphbot
Copy link
Copy Markdown

esphbot commented Jun 5, 2026

PR Review — Add Understanding boards in ESPHome guide

Clean, merge-ready documentation-only PR. No blocking issues.

  • New guide follows MDX/style conventions: quoted frontmatter, Title Case headings, no H1 in content, camelCase image imports, relative internal links with trailing slashes.
  • Verified link targets resolve: /guides/faq/, /guides/physical_device_connection/, and /components/esp32/#variants (esp32.mdx has a ## Variants heading).
  • Prior bot findings already resolved in current diff: dropdown (one word), Wikipedia capitalized, [Board name] Platform rendered as inline code, Figure blocks indented under their list items.
  • Guide added to guides/index.mdx for discoverability; all 8 images present.
  • Minor/non-blocking: CONTRIBUTING routes new docs to next, but current is defensible here since this documents already-shipped Device Builder behavior with no matching esphome YAML change — maintainer's call, and the author justified it in the checklist.


Checklist

  • Follows MDX/style conventions (frontmatter, Title Case, line length)
  • Internal links use relative paths with trailing slashes and resolve
  • Images imported with valid camelCase identifiers
  • Guide added to index.mdx for discoverability
  • Prior bot findings resolved (dropdown, Wikipedia, inline code, list indentation)

Automated review by Kōan (Claude) HEAD=e2079cc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants