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)