Case Guide
The canonical Case library turns fifteen production sites into short, reusable implementation patterns, and the home page mirrors the same fifteen. Fourteen of them run OINK, including this documentation site itself as a self-referential case; pgext.cloud is carried as the boundary case, because it deliberately is not one.
Use this guide when you know the shape of the site you want to build. Follow a case for its architecture and trade-offs, then use the linked documentation for the exact configuration. Counts in individual cases describe the audited snapshot rather than a permanent property of a live site.
Distribution documentation
pigsty.io
A very large English site combining a distribution manual, editorial blog, extension catalogue, taxonomies, version navigation, and pricing landing pages.
pigsty.cc
The Chinese peer deployed as an independent single-language site—a useful trade-off when both language corpora have become products in their own right.
pgsty.pro
A bilingual version archive that renders many release pages from reusable, structured release data.
Product documentation
PIG
A compact bilingual CLI manual with a data-driven home page and a much larger companion blog.
SOW
A bilingual operations manual with a dedicated download content type fed by release metadata.
SILO
A large upstream migration whose checked manifest generates the bilingual documentation navigation.
PG Exporter
A metrics manual combining generated navigation, a structured catalogue, and a system-font presentation.
Books
Designing Data-Intensive Applications
A multilingual, multi-edition book and the strongest example of numbered figures, cross-references, chapter navigation, and indexes.
The Product-Minded Engineer
A focused bilingual publication that needs only OINK’s Book shell.
PG Internal
A finished Chinese translation published as a deliberately single-language Book, with no documentation tree and nothing to switch languages to.
Aggregate, landing, and custom sites
pgsql.cc
An aggregate operations library where several upstream manuals and partially translated language trees share one search and visual system.
pgsty.com
A small bilingual corporate site showing that OINK can primarily be a data-driven landing-page system.
Capslock
A two-page-per-language project whose custom shell hosts an interactive, data-driven configuration generator.
oink.pgsty.com
The full reference site: public documentation, live component examples, design contracts, multiple content shells, and regression coverage in one repository.
pgext.cloud
Not an OINK site: a bespoke single-page extension catalogue, kept in the library to mark where a queryable dataset outgrows a documentation theme.
Choosing a starting point
- For a conventional product manual, begin with PIG or SOW.
- For a large migration, compare SILO and pgsql.cc.
- For a book, compare TPME with the more elaborate DDIA implementation, or PG Internal for a single-language one.
- For a landing or interactive site, start with pgsty.com or Capslock.
- For the broadest reference, use OINK Docs.
- If readers arrive to query a dataset rather than to read, see why pgext.cloud is not a Hugo site.
The theme repository’s tests/site/ is an internal CI fixture, not a starter
template. Its pages exist to exercise rendering behavior; the production cases
above are the better design references.
→ Browse all cases · Quick start · Repository tour