silo.pgsty.com
silo.pgsty.com documents SILO, an S3-compatible
object store. The case snapshot counted 411 pages per language. A migration
manifest covering 387 upstream pages generates data/docs_nav.json, which then
drives the documentation sidebar. The site also has module taxonomy and a
download page.
What it demonstrates
- Migrating a large upstream manual without flattening its information design.
- Generating navigation from a checked manifest instead of hand-maintaining it.
- Layering local bilingual content, taxonomy, and downloads around imported docs.
Use this pattern when the upstream corpus remains authoritative but the local site needs its own navigation, language peers, and product surfaces.
Follow the navigation data boundary
The committed data/docs_nav.json
records its inputs in meta.generated_from (migration/reports/navigation.csv)
and meta.manifest (migration/minio-docs-manifest.csv). The site’s migration
scripts generate data/docs_nav.json from those CSV manifests, and OINK renders
the resulting navigation tree. Use the ordinary content tree for original
manuals, and reserve data/docs_nav.json for imported corpora where an external
manifest controls sidebar ordering.
