[RFC] Versioned Documentation Platform (PR #399): Multi-Version Architecture, HA Standards & Feedback Request 📖 #400
GreenGrassBlueOcean
started this conversation in
Ideas
Replies: 1 comment
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hey everyone! 👋
To give our community and installers clear, modern, and reliable guidance across both production v0.9.4 and the next-generation v2.0 Beta, we have built and deployed a dedicated versioned documentation platform (PR #399, merged into
v2-phase1-architecture).Tip
🌐 Explore the Live Site!
The documentation platform is now officially live on GitHub Pages:
(Notice the interactive version selector dropdown in the top header to switch seamlessly between v2.0 Beta and v0.9.4 Legacy!)
I merged PR #399 into
v2-phase1-architectureand enabled GitHub Pages so everyone can browse the real live website directly rather than reading through 47 raw markdown diffs.Note
Please treat this as an open draft / collaborative RFC!
Nothing is set in stone. I am completely open to any changes, adjustments, additions, or removals. The goal is to agree together on the best documentation and support platform for MyHOME moving forward.
🏛️ Why This Architecture? (Aligned with Home Assistant Best Practices)
As our codebase moves toward the Home Assistant Diamond Quality Standard, our documentation model needs to match the same high standards seen in mature Home Assistant projects (ESPHome, Zigbee2MQTT, Z-Wave JS):
Strict Version Segregation (
mike+mkdocs-material):master): Retained in its own dedicated tree (docs-v0.9/) and aliased aslatest,legacy, and0.9.4. Unsuspecting production users visiting the site root are automatically directed to stable v0.9.4 documentation.v2-phase1-architecture): Isolated under/beta/and/dev/. The wordstablehas been deliberately removed from beta documentation to avoid any confusion until v2.0 is officially released.manifest.jsonand in-app Repair issues (repairs.py) point permanently to stable, version-pinned URLs.100% UI-First for v2 (ADR-0010 Compliance):
myhome.yaml) have been removed from v2 guides to prevent user confusion, while clearly explaining that existingmyhome.yamlfiles remain safe transitional overlays for friendly names and physical SCS lighting groups (#G).Frictionless 0.9.4 → v2.0 Migration Path:
<mac>-<who>-<where>) are deterministically preserved across upgrades.myhome.yamlhandling and details the rollback path.Complete Gateway Options & Services Reference:
worker_count,transition_mode,generate_events,broadcast_resync,decoders)..storagecleanup guide for users who need a fresh start.💬 We Want Your Feedback!
Before we ship this with
v2.0.0b13, we would love to hear from fellow maintainers, testers, and installers:latest= 0.9.4 vsbeta= v2)?Please test the live site at openwebnet-ha.github.io/MyHOME and share your thoughts, suggestions, or critique below!
Looking forward to your input! 🚀
All reactions