Docs are Migrating from Jekyll to Hugo
Author:
After nearly a year of investigating how to enable multilingual support for Kubernetes docs, we've decided to migrate the site's static generator from Jekyll to Hugo. What does the Hugo migration mean for users and contributors? Hugo's Markdown parser is . As a consequence, some Markdown formatting that rendered fine in Jekyll now produces some unexpected results:
If you encounter any site weirdness or broken formatting, please specific to Hugo migration. Our initial search focused on finding a language selector that would play well with Jekyll. The projects we found weren't well-supported, and a prototype of one plugin made it clear that a Jekyll implementation would create technical debt that drained resources away from the quality of the docs. We chose Hugo after months of research and conversations with other open source translation projects. (Special thanks to Andreas Jaeger and his experience at OpenStack). Hugo's
Another advantage of Hugo is that
Again, if you encounter any broken, missing, or unexpected content, please
Changing the site framework
Things will break
Multilingual support is coming
Pain now, relief later