Jekyll can be used for much more than blogging, too. Ribose, for example, has a network of sites for its open-source initiatives[0] built on top of Jekyll. Sit

Jekyll can be used for much more than blogging, too. Ribose, for example, has a network of sites for its open-source initiatives[0] built on top of Jekyll. Sites are integrated with each other and also with Git repos of relevant software packages, pulling e.g. latest commit times & documentation in AsciiDoc at build time. Each site does have a blog/newsroll, but in the end is much more than that. The implementation involves a gem-based theme with accompanying helper plugin, which are open source[1]. Going the static site route, on one hand, introduces new constraints—for example, build times become important—but on the other hand allows to build blazing-fast websites without having to worry as much about ongoing server maintenance. (Currently each site gets built on Travis CI and delivered via AWS S3/CF.) Disclaimer: I work with Ribose currently and participated in Ribose Open development. [0] See for example https://www.metanorma.com/ https://www.metanorma.com/, https://www.rnpgp.com/ https://www.rnpgp.com/ or https://www.cryptode.com/ https://www.cryptode.com/ [1] https://github.com/riboseinc/jekyll-theme-open-project/ https://github.com/riboseinc/jekyll-theme-open-project/