• 0 Posts
  • 3 Comments
Joined 3 months ago
cake
Cake day: February 27th, 2025

help-circle
  • I ended up with Hugo, a git repository, and a cron job for the build. I write an article, check it in, the server picks up the git change and rebuilds the site. What I like about the setup is that the server only has the binaries hugo and git, and a shell script for the rebuild. Also, I write in Markdown, add media to the git repository, and articles are published soon after I check in without any remoting on my part.

    I did look at WriteFreely after the setup, though. I find the minimalist design very beautiful. Didn’t switch to it, but may look at it again for another project. https://github.com/writefreely/writefreely



  • I went the same direction, from WordPress to static site generation. I did the same evaluation as you are trying to do and ended up with Hugo, mostly because there is a lot of support available for it. My runner up was Pelican, because I was fluent in Jinja2, but I didn’t want to mess around with the templates and Hugo’s were prettier. Sue me, I am shallow.

    The one regret I have about Hugo is that the templating language is challenging. I am trying to be as neutral as possible, but it seemed like even simple things were complicated to achieve. If someone would come up with a Hugo that speaks Jinja2, I’d be really delighted.

    Other than that, conversion from WordPress to Hugo was relatively straightforward, despite needing to find a gallery component and converting menus. Hugo is indeed very fast in processing, which become important when your blog has thousands of articles.

    I set up the blog as a private git repository. The server pulls from it, then runs Hugo and a full text search engine, and the content is visible and searchable within five minutes on update.