Our great sponsors
-
-
gutenberg
A fast static site generator in a single binary with everything built-in. https://www.getzola.org
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
eleventy 🕚⚡️
A simpler site generator. Transforms a directory of templates (of varying types) into HTML.
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
-
pandoc-ssg
Pandoc-SSG is a Make driven Pandoc static site generator. It features basic functionality in a trivial implementation.
Am I missing something, or is Jekyll still receiving fairly active contributions[1]?
Even by that (misleading) metric, it doesn't seem to be dead. Expecting maintainers to tilt at the newest windmill instead of actually maintain is a critical part of why so many in the open source community burn out.
[1]: https://github.com/jekyll/jekyll/commits/master
I loved Jekyll, and still do. This is a sad state, and I hope both that it improves and Jekyll survives.
I switched to Zola for most of my stuff a while back, and while there are still gaps, it does everything I need and is production ready.
https://www.getzola.org/
Personally I don't find static site generators worth the effort. I end up just writing my own for each site in 1-200 lines of Python. It's normally just a markdown library and a template engine wrapped with a file system walker.
Here's an example: https://github.com/eatonphil/notes.eatonphil.com/blob/master.... It's longer than usual since it embeds parts of the home page html inside it.
These scripts last for years and only change slightly over time. Very low maintenance.
Good technology alone isn't enough to lead to adoption. Tiddlywiki, imo, is the best personal blogging tools. It is a static site, it got an embedded editor, it got cool concepts realised like transclusion, among many others. Go ask around, I bet hardly anyone talks about it. If a tree falls in a forest and no one is around to hear it, does it make a sound?
https://tiddlywiki.com/
I was using Middleman for a while, but then grew tired of all the dependencies I had to always keep up-to-date. I did the completely illogical thing and built my own static site generator, https://sitepress.cc/
A few years later and I ended up deleting most of it and replacing the internals with Rails. Now Sitepress is just a tiny rails application sitting on top of a bunch of files. Most of the maintenance and dependencies are handled by major Rails lib maintainers.
When you deploy it, you can compile it into static files and deploy as you’d expect, but you can also deploy it as a rails or rack app … or even embed it into an existing rails app.
When Rails 7.0 gets released I’ll drop JS importmaps into the default install for free and have my dream static site generator that doesn’t have a huge asset compilation step.
Just don't do any of that stuff if you don't want to. If you're writing software because it's useful to yourself and others and making it open to others to use you do not owe them a place to chat, engagement, a roadmap, a release cycle (or any given release).
You can weigh whether you want to do those things
Those things are often set up when people want to run software projects with certain goals and if those goals are not yours then that is fine, just know that there is a tradeoff.
One nice example is litestream[0]. It's open source, not open contribution -- similarly you can have open source without built in community/discord/project-management/etc.
[0]: https://github.com/benbjohnson/litestream#open-source-not-op...
> Those concerns led me to fork Jekyll and create Bridgetown.
Please, Jared, contribute to Jekyll instead. There are many contributors, and you will probably get better code reviews. Bridgetown is your one-person show where you contribute the most commits (https://github.com/bridgetownrb/bridgetown/graphs/contributo...). Who is reviewing your changes? :)
YOU can revive Jekyll :)! I would like that. No offence, but Bridgetown is probably on "hiatus" sooner or later as well. I, as a user, have no trust in these forks.