Skip to content

feat: restructure docs into Getting Started, Guides, and Reference#24

Open
synchwire wants to merge 3 commits into
mainfrom
feat/docs-restructure
Open

feat: restructure docs into Getting Started, Guides, and Reference#24
synchwire wants to merge 3 commits into
mainfrom
feat/docs-restructure

Conversation

@synchwire

Copy link
Copy Markdown
Collaborator

Summary

  • Restructure the docs IA to match the design proposal: three top-level buckets — Getting Started, Guides, Reference (plus Architecture).
  • Split the single Getting Started walkthrough into five ordered pages: Introduction, Install, Bootstrap the orchestrator, Connect your first agent, Your first apply.
  • Add a Guides section: Writing state modules, Drift & plan mode, Secrets, and Progressive deployment.
  • Fold the "Concepts" stub into Guides; update the landing-page cards and sidebar config.

Accuracy

Every page is grounded in the ordo code, design docs, and the generated CLI reference. Verified before writing: resource kinds and module fields (against the module JSON Schema and examples/caddy-site.ordo.yaml), change triggers (reload_on/restart_on/rerun_on), the secret expression syntax (${{ secrets.name }}), server-side resolution + at-rest encryption + redaction + tag/node scoping, plan/drift semantics, and the exact CLI command surface (ordo state plan|apply|drift, ordo secrets …, ordo assignments …). Module upload is described as web-UI/API only — there is no CLI upload command, so none is invented.

Corrected vs. the design:

  • Progressive deployment is marked Planned / not-yet-available with a caution admonition — Fleet operations (rolling/canary/rollback) is unimplemented (Phase 9). The page describes intended behaviour only.
  • Dropped "complete" from the product description (pre-first-release).
  • No custom header/version widgets — Starlight already provides the themed header, search, theme toggle, and social links, so the design's header mock is native. (The v0.1.0 version pill in the mock is also ahead of the current v0.0.7.)

Verification

npm run build passes (100 pages, Pagefind index built). All authored internal links resolve, including the five Getting Started pages, four Guides, and /reference/api/.

@netlify

netlify Bot commented Jul 7, 2026

Copy link
Copy Markdown

Deploy Preview for ordo-docs ready!

Name Link
🔨 Latest commit 6abdb91
🔍 Latest deploy log https://app.netlify.com/projects/ordo-docs/deploys/6a4d48857be1890008c90333
😎 Deploy Preview https://deploy-preview-24--ordo-docs.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.

Split the single Getting Started walkthrough into five ordered pages
(Introduction, Install, Bootstrap the orchestrator, Connect your first
agent, Your first apply) and add a Guides section: writing state
modules, drift & plan mode, secrets, and progressive deployment.

Content is grounded in the ordo code, design docs, and generated CLI
reference. Progressive deployment is marked "Planned" and not-yet-
available (Fleet operations is unimplemented on the roadmap). The
"Concepts" stub is folded into Guides.
@synchwire synchwire force-pushed the feat/docs-restructure branch from 971c477 to 809481e Compare July 7, 2026 15:35
synchwire added 2 commits July 7, 2026 16:48
Bring the Starlight docs onto the marketing brand: dark navy palette
with cyan accents, Schibsted Grotesk / IBM Plex Mono fonts, the Ordo
arch mark as the logo, a "DOCS" pill on the wordmark, a filled-cyan
active sidebar entry, and a getordo.dev link in the header cluster.
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