Package / shared
- 01 Base + docs layouts
- 02 Header, footer + search
- 03 Themes + reading styles
- 04 Page actions + enhancements
Shared documentation infrastructureAstro package + scaffold
ZueDocs / system 01
One docs shell.
Every product in sync.
A reusable Astro documentation package for teams that want one considered interface across many products—without moving product knowledge out of the repositories where it belongs.
Shared source of truth ready to compose
A
zuedocsshell / behavior / styles
B
your repositorycontent / config / product voice
bunx zuedocs init my-docs01 — configure locally02 — inherit the shell03 — publish statically
01LayoutsBase and article framing
02ComponentsHeader, footer, search, actions
03EnhancementsTables, code, diagrams, navigation
04ScaffoldA clean starting point for new sites
The shared contract
Package-owned where consistency matters. Repository-owned where context matters.
Standardize the frame.
Keep the knowledge local.
ZueDocs owns the durable interface layer: layouts, navigation, search, theme behavior, page actions, and reading styles. Each consumer keeps its own Markdown, product voice, and deployment configuration.
Repository / local
- 01 Markdown documentation
- 02 Navigation + site config
- 03 Homepage + product copy
- 04 Deployment configuration
Built for both sides of the screen
Human-readable by default. Agent-usable by design.
Documentation is infrastructure now.
The same source should support the engineer scanning a guide and the agent gathering exact implementation context. ZueDocs gives both a clean route through the material.
For developers
Keep the shell centralized, leave product content in the product repo, and ship a consistent documentation experience without maintaining another frontend fork.
For agents
Expose a legible content structure, raw Markdown routes, and predictable page actions so documentation is as useful to automated readers as it is to people.
Documentation index
The system explains itself.
Start with the map.
Go as deep as needed.
View all documentation 01Launch02Launch03Structure04Structure05Structure06Operations07Operations
Quickstart
The shortest path from fresh clone to a local docs site you can edit confidently.
Scaffolding and migration
Agent-ready setup paths that preserve the shared shell instead of creating local layout forks.
Content model
A map of the files that matter when you adapt the template to a real product.
Shared shell configuration
The supported configuration seam for branding a consumer while retaining the shared ZueDocs theme.
Page authoring
Lightweight editorial rules for turning markdown pages into a coherent docs experience.
Deployment workflow
A practical deployment path that matches the Vercel and Cloudflare workflow patterns already used around Gooselake.
Release checklist
A durable checklist for content, styling, and deployment validation before you cut a release.
Begin with a working system
Build the docs once.
Let every release benefit.
Scaffold a new Astro docs site, or migrate an existing one to the shared package.
Open the quick start