Bilingual on OINK

pgsty.com

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

pgsty.com is the bilingual corporate site behind Pigsty. It has only about ten pages: a type: home front page assembled from data/home/{en,zh}.yaml, followed by focused pages for solutions, company information, and pricing.

What it demonstrates

Using OINK as a landing-page theme with almost no documentation tree.
Maintaining compact English and Chinese marketing pages as peers.
Building the home-page narrative from reusable data sections.

This pattern is appropriate when a project wants OINK’s brand, navigation, search, and multilingual conventions but primarily needs a small public-facing site rather than a manual.

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.

caps.vonng.com

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

caps.vonng.com is a two-page-per-language site for the Capslock keyboard enhancement: a home page and an interactive configuration generator. The generator reads data/capslock-v3.json and uses a custom customizer shell type alongside the regular documentation shell.

What it demonstrates

The practical lower bound of an OINK site: a tiny project needs no front-end application just to publish a tool and its introduction.
Extending the shell registry for one purpose-built interactive page.
Keeping generator data separate from its presentation and bilingual prose.

Use this pattern when documentation is small but one interactive tool deserves the same navigation, theme, and language controls as the rest of the site.

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.

tpme.vonng.com

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

tpme.vonng.com publishes The Product-Minded Engineer in English and Chinese, with 18 chapters per language in the case snapshot. Its configuration narrows the supported shell types to [book].

What it demonstrates

A publication with exactly one content model and no documentation shell.
Bilingual chapter peers with a shared visual and navigational system.
A smaller Book implementation than the multi-edition DDIA site.

This is the clearer starting point for a single-title tutorial or translated book: keep the site architecture narrow, then add numbering and indexes only as the manuscript needs them.

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.