tips

Translating project documentation sites for free

Offering your project documentation in just one language doesn't work anymore in a world that gets more global by the minute. Once you want to expand into other markets, you need to offer your project documentation in several languages.


Offering your project documentation in just one language doesn't work anymore in a world that gets more global by the minute. Once you want to expand into other markets, you need to offer your project documentation in several languages.

Particularly, translating project documentation has some unique challenges:

  • Content needs to stay synchronized between all language versions.
  • You probably use a static page generator such as Jekyll, Hugo, MkDocs, Sphinx, or Sculpin for the documentation.

While static-page generators offer many benefits such as change management and easy editing using Markdown or reStructuredText they don't offer good solutions for multilingual content.

One approach for translating static pages is to copy the whole documentation into another folder and manually translate all content. The big problem with this is that the content will quickly be outdated, and any edits take a significant time.

A better solution would be to use software just made for translating static web pages. Such as Dilingual. Dilingual comes with an easy-to-use web interface to manage and serve your translated project documentation.


And the best thing? It is entirely free for you. Our team of humans will also happily help you get started. Schedule a demo with us now!

Similar posts

Get notified for updates

Subscribe to our newsletter to stay up to date on the latest industry insights and news.