Docs on OINK

pigsty.cc

Fri, 14 Aug 2026 00:00:00 +0000

pigsty.cc publishes Pigsty in Simplified Chinese. The case snapshot counted more than 1,490 content files and over 300 blog posts, with its own data-driven pricing page and Chinese as the default content language.

What it demonstrates

Splitting a very large bilingual corpus into two independently deployed, single-language sites.
Connecting the pair through the alternate-site control and version menu.
Letting each language keep its own publishing cadence and landing-page data.

This pattern trades same-domain language switching for clearer ownership and smaller builds. It is useful when both languages are already substantial products rather than occasional translations.

pigsty.io

Thu, 13 Aug 2026 00:00:00 +0000

pigsty.io is the English home of Pigsty, the open-source PostgreSQL distribution. At the snapshot used for this case, it contained more than 1,400 Markdown files, over 200 blog posts, an extension catalogue, and a data-driven pricing page.

What it demonstrates

A large documentation tree and editorial blog living in one Hugo site.
Structured catalogues whose content and data are maintained separately.
A layout: landing pricing page assembled from data/landing.
Taxonomies and a version menu that also link to sibling and historical sites.

Choose this pattern when one English-first site must serve reference material, news, catalogues, and commercial landing pages without splitting the toolchain.

silo.pgsty.com

Wed, 12 Aug 2026 00:00:00 +0000

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.

oink.pgsty.com

Tue, 11 Aug 2026 00:00:00 +0000

oink.pgsty.com is the site you are reading. It is the theme’s public manual and a real consumer used for regression coverage. Its component pages render live examples; the same repository also carries design contracts, Book fixtures, download data, and home and landing-page data.

What it demonstrates

Documentation examples that are executable regression fixtures, not screenshots.
One site serving users, content authors, theme developers, and reviewers.
Component, Docs, Blog, Book, Case, download, and landing surfaces together.
Bilingual content checked against a pinned Hugo Module dependency.

Use this repository as the broad reference implementation; use the narrower cases when starting a site that needs only one or two OINK content models.

pig.pgsty.com

Sun, 09 Aug 2026 00:00:00 +0000

pig.pgsty.com documents PIG, the PostgreSQL extension package manager. Its core manual is deliberately compact—18 pages per language in the case snapshot—while a 50-post bilingual blog carries updates and deeper explanations. The home page is assembled from data/home.

What it demonstrates

A shallow, mostly single-file documentation tree for a focused CLI product.
English and Chinese peers without duplicating navigation design.
A data-driven home page paired with a larger stream of blog content.

Choose this pattern when the reference manual is small and stable but product news, tutorials, and release context need room to grow.

sow.pgsty.com

Sat, 08 Aug 2026 00:00:00 +0000

sow.pgsty.com documents SOW, an APT and YUM repository manager. The case snapshot contained 55 pages per language and a dedicated download page whose versions, tags, and release artifacts are generated from structured release data.

What it demonstrates

Keeping operational documentation bilingual at a moderate scale.
Giving downloads their own content type instead of embedding links in prose.
Reusing release data so package metadata has one source of truth.

This pattern fits software that distributes many platform-specific artifacts and needs installation instructions, repositories, and downloads to evolve together.

exp.pgsty.com

Fri, 07 Aug 2026 00:00:00 +0000

exp.pgsty.com documents PG Exporter, a Prometheus metrics collector for PostgreSQL. The case snapshot counted 15 pages per language and 37 bilingual blog posts. Generated navigation, home-page data, and a structured metric catalogue do most of the organizational work.

What it demonstrates

Using data/docs_nav.json for a small but deliberately ordered manual.
Rendering a domain catalogue from structured data rather than repeated prose.
Selecting typography: system when a site should make no brand-font request.

This pattern suits technical products whose reference data is as important as their narrative documentation, especially where a lightweight font stack is preferred.

pgsql.cc

Mon, 03 Aug 2026 00:00:00 +0000

pgsql.cc brings the operating manuals for Patroni, HAProxy, etcd, PgBouncer, pgBackRest, and pgBadger into one PostgreSQL-focused library. The case snapshot counted 217 English pages and 80 Chinese pages.

What it demonstrates

Giving several upstream products a consistent local information architecture.
Publishing English first while Chinese coverage grows over time.
Keeping partial translation useful instead of blocking publication on parity.
Using subtrees to preserve clear product boundaries inside an aggregate site.

Choose this pattern for a curated technical library where sources and translation maturity vary, but readers benefit from one search and one visual system.

pgsty.pro

Sun, 02 Aug 2026 00:00:00 +0000

pgsty.pro documents Pigsty v5 in English and Chinese. The case snapshot counted 343 documentation pages per language and 67 bilingual blog posts. Its release archive is the distinctive part: 128 localized pages render version data through the reusable release-card component.

What it demonstrates

Keeping a long product history navigable without hand-building every card.
Sharing structured release data between download, archive, and detail pages.
Maintaining documentation and editorial posts as bilingual peers.

Use this pattern for products with many supported or historical versions where release metadata must stay consistent across several surfaces.