Given that we are alright with using a build process for the style guide (T164246), we should consider using a static site generator. It will:
* Reduce repetition of markup - header, footer, parts of the sidebar
* Improve i18n support
* Remove the need to keep built files in the repo (we currently have just one btw)
|Name|Language|i18n support|File format|
|--|--|--|--|
|[[ https://middlemanapp.com/ | Middleman ]]|Ruby|Yes (falls back to the default language if there are no strings for the language it is looking for)|YAML|
|[[ https://hexo.io/ | Hexo ]]|Node.js|Only for `layout`, not for `source`, which is not helpful to us. Couldn't get it to work though.|JSON or YAML|
|[[ https://webpack.js.org/ | Webpack ]] build ([[ https://webpack.js.org/loaders/html-loader/ | html-loader ]], [[ https://github.com/webpack-contrib/i18n-webpack-plugin | i18n-webpack-plugin]])|Node.js|Yes (no fallbacks, I am guessing this does a simple replace)|JSON|
It shouldn't be too hard to get these to work with http://translatewiki.net/.