Public Site Structure
This page keeps the public information architecture simple and visible.
The site should stay English-first, wiki-led, and selective about what reaches the public layer.
The public shape
The site has three jobs:
- Home explains the system and sets expectations
- Wiki holds durable, public-safe knowledge pages
- Blog holds selective notes, essays, and dated publishing output
That structure is intentionally narrow.
Routing rule
The wiki is the main public knowledge surface.
Use the Wiki when the page is meant to stay relevant beyond a news cycle:
- concepts
- system explanations
- frameworks
- durable comparisons
- operating principles
Use the Blog when the page is time-bound, essay-shaped, or publication-led:
- notes
- dated essays
- release-style writing
- selective research outputs
What should stay out
The public site should not become:
- a mirror of the private vault
- a generic docs portal
- a dumping ground for thin drafts
- a mixed-language structure without intent
"Wiki, not Docs" means the structure should serve knowledge and publishing clarity, not documentation theater.
Navigation standard
Keep navigation small and obvious:
- Home
- Wiki
- Blog
- Source link only when useful
If a new section does not clearly improve public understanding, it probably should not exist yet.
Deployment implication
A small structure is easier to review before publishing.
That helps the release path stay boring:
- add or revise public-safe content
- keep the page in the right surface
- run a production build
- verify output
- deploy when ready
Near-term direction
For now, keep the site centered on the wiki and selective blog publishing.
Cloudflare Pages can be evaluated later if it becomes the cleanest deployment target, but the public structure should stay stable regardless of hosting choice.