https://lxghost.github.io/tags/large-site/Recent content in Large Site on OINKHugoen-USFri, 28 Aug 2026 00:08:16 +0800https://lxghost.github.io/case/pigsty-cc/Fri, 14 Aug 2026 00:00:00 +0000https://lxghost.github.io/case/pigsty-cc/<p><a href="https://pigsty.cc/">pigsty.cc</a> 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.</p> <h2 id="what-it-demonstrates">What it demonstrates </h2> <ul> <li>Splitting a very large bilingual corpus into two independently deployed, single-language sites.</li> <li>Connecting the pair through the alternate-site control and version menu.</li> <li>Letting each language keep its own publishing cadence and landing-page data.</li> </ul> <p>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.</p>https://lxghost.github.io/case/pigsty-io/Thu, 13 Aug 2026 00:00:00 +0000https://lxghost.github.io/case/pigsty-io/<p><a href="https://pigsty.io/">pigsty.io</a> 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.</p> <h2 id="what-it-demonstrates">What it demonstrates </h2> <ul> <li>A large documentation tree and editorial blog living in one Hugo site.</li> <li>Structured catalogues whose content and data are maintained separately.</li> <li>A <code>layout: landing</code> pricing page assembled from <code>data/landing</code>.</li> <li>Taxonomies and a version menu that also link to sibling and historical sites.</li> </ul> <p>Choose this pattern when one English-first site must serve reference material, news, catalogues, and commercial landing pages without splitting the toolchain.</p>