Site architecture
Three repositories
connectome-fs publishes documentation from a dedicated hub, not from the marketing site.
| Repository | Role |
|---|---|
|
Product source (Rust crates, CLI) and the Antora component under |
|
Docs hub — Antora playbook (Valentus + Facto), home portal, GitHub Pages deploy for |
|
Organization website (SolidStart) — news, about, roadmap; Antora is not embedded here |
connectome-fs/connectome-fs/docs/ ← Antora component (authoring)
connectome-fs/docs/ ← Hub playbook + Pages deploy
connectome-fs.github.io/ ← Marketing / news site only
https://connectome-fs.github.io/ ← Website
https://connectome-fs.github.io/docs/ ← Docs hub
https://connectome-fs.github.io/docs/connectome-fs/ ← This component (alias)Why not Antora inside SolidStart?
Antora is a build-time docs site generator (AsciiDoc → static HTML + UI bundle + extensions). SolidStart is an app framework. They do not share a runtime component model.
Embedding Antora into the website repo forced a second docs pipeline and made the marketing site responsible for versioned docs UX. The hub owns that UX now; the website links to it.
Live updates
Antora output is static. “Live on source update” means rebuild the docs hub (push → Actions → Pages), not hot-reloading Antora inside Solid at runtime. Pushing this product repository alone does not refresh the aggregator until the docs hub workflow runs (or a hub redeploy is triggered).