Building technical knowledge bases is easy.
Maintaining them across seven languages is not.
During the last year, I’ve been working on a public VPN documentation project that spans EN-GB, EN-US, PL, DE, ES, FR and NL-BE. The goal is simple: keep all locales synchronized, readable and consistent — without relying on heavy CMS systems.
🔧 Why I chose GitHub Pages
• clean folder structure
• no database
• instant publishing
• Markdown-first workflow
• version control for every change
• perfect for open documentation
🏗️ How the project is structured
Each locale has its own mirrored folder and its own URL namespace.
Hreflang relations are handled manually to keep full control.
The EN-GB version is the “canonical” source, and all other languages map directly onto it.
You can view the English version here:
👉 https://dloran1.github.io/en-gb/
📦 Advantages of this approach
• consistent multi-locale SEO
• transparent change history
• Git-level collaboration
• extremely fast page serving
• no vendor lock-in
This setup has been surprisingly stable even as the project grew to dozens of articles per locale.
More details about internal tools will come soon — especially around orchestrating updates across languages.
Top comments (0)