The main issue with Jekyll is the blog post system. It requires all the blog posts to live under `_posts/<date>-<slug>.md`. So now the user has to invoke a comm

The main issue with Jekyll is the blog post system. It requires all the blog posts to live under `_posts/<date>-<slug>.md`. So now the user has to invoke a command-line tool to create the proper slug. Then if the post doesn't get published on the same day or the title changes the user has to rename the filename. Images live in a different folder and get all put together. A better implementation would be: render all the markdown files in the repository and map README.md to index.html. Now you can create your own file structure, have your images with the article, and optionally add them to the RSS feed by adding a `published_at` in the frontmatter. Or even better use the git history to find out when it was added (and changed) in the repo. You get all the "admin" and rendering for free from GitHub. I guess my point is that there is a lot of friction inherent to Jekyll's blog post publishing system. Since I adopted that other approach it's much easier for me. I love to only focus on the text and not worry about the rendering. And be able to edit it with my favourite text editor.