Skip to content

docs(roadmap): reframe for shipped v1.0 + sequenced v1.1–v1.6 release line - #9

Merged
VijitSingh97 merged 1 commit into
mainfrom
roadmap-post-v1.0-release-line
Jun 15, 2026
Merged

docs(roadmap): reframe for shipped v1.0 + sequenced v1.1–v1.6 release line#9
VijitSingh97 merged 1 commit into
mainfrom
roadmap-post-v1.0-release-line

Conversation

@VijitSingh97

Copy link
Copy Markdown
Contributor

Why

v1.0 has shipped (v1.0.0–v1.0.3 are out), but the landing-page roadmap section was doubly stale:

  1. It still framed v1.0 as pre-launch"v1.0 — feature-complete, at the release gate", "The finish line", "Left: the GHCR release pipeline … then tag v1.0."
  2. It lumped every post-1.0 feature into one "v1.1 — Control & insight" card — which no longer matches the milestone restructure, where the old 37-issue v1.1 mega-milestone was re-sliced into themed point releases v1.1 → v1.6 → v2.

This PR makes the public roadmap reflect reality and the new release sequence.

What changed

data/content.yaml (copy) + layouts/index.html (one template block):

  • v1.0 lane → shipped. Wave 05 status The finish line → Shipped, the ship node pill SHIP → LIVE, and the section title/sub/labels moved to past tense ("v1.0 is live. Now, the road to the appliance era.").
  • Beyond v1.0 → a sequenced release line. Replaced the single lumped card with v1.1–v1.6, each landing one theme, leading to the v2 appliance era:
    • v1.1 — Privacy, by default (Next) · v1.2 — Operator alerts · v1.3 — Trends & insight · v1.4 — Control from the dashboard (one-click upgrades) · v1.5 — Fleet management · v1.6 — Deploy anywhere · v2 — The appliance era
  • Rendered with the existing "wave" timeline component (a second lane) — no new CSS, just a second range + a ship_beyond node.

Verification

  • hugo --gc --minify --panicOnWarning (strict, CI parity) — passes, zero warnings.
  • htmltest (internal links/anchors/images) — passes.
  • Visually checked both lanes in a local hugo server.

Note: data/releases.json is intentionally untouched — it's auto-refreshed by scripts/refresh-releases.py at deploy.

🤖 Generated with Claude Code

… line

v1.0 has shipped (v1.0.0–v1.0.3), but the landing-page roadmap still
framed it as pre-launch ("feature-complete, at the release gate") and
lumped every post-1.0 feature into a single "v1.1 — Control & insight"
card. That no longer matches the milestone restructure (v1.1 split into
themed point releases v1.1–v1.6 → v2).

- Mark the v1.0 lane shipped: wave 05 "Shipped", ship node "LIVE",
  title/sub/labels moved to past tense.
- Replace the single horizon card with the sequenced v1.1–v1.6 release
  line (Privacy → Alerts → Trends → Control → Fleet → Deploy-anywhere),
  each landing one theme, leading to the v2 appliance era.
- Render the new line with the existing "wave" timeline component
  (a second lane) — content-driven, no new CSS.

Strict Hugo build (--gc --minify --panicOnWarning) and htmltest both
pass locally.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@VijitSingh97
VijitSingh97 merged commit 1a2e00e into main Jun 15, 2026
2 checks passed
@VijitSingh97
VijitSingh97 deleted the roadmap-post-v1.0-release-line branch June 15, 2026 19:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant