[flowcool]

Summary

A little repotting for the docs — no extra watering required. 🌱

The README points to missing images, and the first-install guide hides the useful steps between long technical notes. This refresh shows the finished product, makes Label-maker easy to find, and gives new users a continuous path from assembly to their first readings.

README.md                 Product photo and direct start/label/hardware links
docs/source/
  index.rst               Clear documentation entry points
  getting_started.rst     First-install route
  programming.rst         Configure, flash, verify, calibrate and update
  labels.rst              Generate one background and match its gauge scales
  files/lemon-tree-label.json  Ready-to-use, firmware-matched generator input
  faq.rst                 Current setup, display, sleep and battery answers

The instructions match the firmware currently on V2R1. They do not require the pending display changes in #31 or fork-only Maintenance commands. Existing explicit programming/flashing/support anchors are preserved.

Evidence

• Before: README images target absent Documentation/Images/Top.png and Bottom.png; the FAQ asks users to copy font files although the YAML uses Google Fonts; the label generator is buried in a note.
  After: existing repository product photos render, the label workflow has its own page, and setup instructions match the supplied YAML.
• Strict Sphinx 8.2.3 HTML build: all 11 pages pass with nitpicky=True, warningiserror=True, original intersphinx mappings and a numeric 5-second inventory timeout. The legacy pinned Sphinx 5.0.2 environment was not exercised.
• 172 internal HTML links, anchors and image references pass, as do README local targets. All 13 external RST links returned HTTP 200 during preparation.
• Executed the documented single-label command from Label-maker and generated a label from the downloadable local JSON with YAML-matched gauge ranges: 296 × 128 PNG, visually inspected.
• ESPHome 2026.9.0 configuration validation passes on an isolated copy of the current upstream standalone YAML with the documented Wi-Fi secrets and generated local image. Test values are synthetic. No firmware upload or hardware test was performed.
• Original CRLF/LF styles preserved; semantic diff, numstat and git -c core.whitespace=cr-at-eol diff --cached --check pass. Only the seven documentation files above change.
• AI assistance: Codex helped write the documentation and execute these checks. Claims were checked against the supplied firmware, Label-maker implementation and official ESPHome sources. Browser layout was not tested.

CodeRabbit findings on the fork were also checked: calibration defaults are explicit, and the generator now uses a local, firmware-matched JSON instead of relying on changes in the companion repository. The firmware-tests badge is valid on upstream; the fork uses its own YAML-check badge.

Merge Danger

Door: two-way

Revert the documentation commit to restore the previous pages. Firmware, board files and live devices are unchanged.

Blast Radius: documentation

Navigation and first-install instructions change. The PR introduces no firmware dependency and can be reviewed independently of #31.

[flowcool]

@JGAguado This one is for you as it's a bit more cosmetic and make it a bit more sexy - need to have an external view on this ;)

[JGAguado]

Big improvement to the entry points and first-install path; the referenced images and files all exist. Approving.