Hugo VS Jekyll

I used Hugo to convert markdown to html as with this it was very easy to do as I just did installed Hugo locally created a project added a pre-build theme and just copy-paste markdown files to content folder inside Hugo project that's it. Quickly pushed code to GitHub wrote a simple GitHub Workflow to deploy Hugo Site on GitHub Pages and That's it.

Like some other commenters here who started with Bootstrap/jQuery/etc., I feel stuck in the stone ages at times. My most recent content-based site uses Hugo (https://gohugo.io/), but I'm starting to tire of the magic and gotchas I keep running into.

Can someone that has used Astro and an older static site generator framework explain the pros/cons of Astro in that context?

I decided to go with Hugo to build my personal website. The only thing I based my choice on was the build time. I thought Hugo was in the same league as Astro when it comes to content management perks, but it isn't quite there yet. Or, I can say it has its own path since it's older than most of the other static site generators I've encountered. Moreover, it's a Go application, which is another important factor to consider when evaluating technology choices.

Hugo got a WASM based plugin system, but real scripting plugins that would be needed for SQLite are still a feature request: https://github.com/gohugoio/hugo/issues/5510

https://gohugo.io/

It's written in go but what's great about it, unlike many competitors written in Javascript or Python, is that it is just a simple binary you download and run, you do not need to get a PhD in the go build system to start a web site also it is crazy fast. It can publish a site to something like S3 or Azure Storage behind a CDN and you do not have to worry about anything other than paying the storage and bandwidth bills.

Myself I've been procrastinating on getting myself a blog and my take is Hugo is not customizable enough for me without learning a lot of Go, so I have looked at are either Python-based or oriented towards scientific publishing oriented systems such as

https://getpelican.com/

https://www.sphinx-doc.org/en/master/

https://quarto.org/

(I want to write stuff like https://ontology2.com/essays/PropertiesColorsAndThumbnails.h...)

I've given this list to people in your shoes and they usually react with information overload

https://jamstack.org/generators/

part of that is that there are 355 generators (there have to be some good ones in there somewhere) but it also uses the kind of miscommunication patterns we're used to in webtech where, for instance, you'd think they are pushing Javascript down your throat (the "J" stands for Javascript but the generators I've mentioned generate mostly HTML with just a little Javascript.)

Pick something simple and run with it, if I did that 2 years ago I'd be blogging now.

I'm satisfied with Hugo: https://gohugo.io/ It is very fast and has a lot of features. The syntax highlighting for code looks also very good.

For my personal site, I use Hugo, and I host the markdown files on GitHub. Publishing is done whenever I push to the repository using Netlify.

Hugo, one of the most popular open-source static site generators, is written in Go and optimized for speed, flexibility, and ease of use. In this guide, we’ll walk through how to seamlessly integrate Uniqrate into a Hugo-powered website, giving you a simple way to gather user feedback and improve your content.

Several years ago static site generators were all the hotness. Around then I switched to Hugo [1] from Wordpress and it's been a good experience. You do all editing locally with the CLI then chuck it to Git to be built and hosted by Netlify.

[1] https://gohugo.io/

That would be an improvement, but it still wouldn't be equivalent to what you can do with Ruby and Jekyll. For example I do [1] so I don't need to put dates in my post names, which also fixes a bug [2] I encountered but was never fixed.

[1]: https://stackoverflow.com/a/68287682/660921

[2]: https://github.com/jekyll/jekyll/issues/8707

In your repository settings you need to turn on GitHub Pages to make it pull Jekyll content (that's the magic✨ default GitHub Pages build tool) from your GitHub repository.

If you're looking to start a blog (or if you're thinking of redesigning yours although you haven't posted in 2 years), you'll stumble upon a lot of options and it can be incredibly daunting; and if you stumble with the newest Josh's post about his stack it is easy to feel overwhelmed with the shown stack.

Here I am, signing off from a self-hosted WordPress site and finding a welcome change in Jekyll, a blog-aware static site generator. There is nothing new about this, several well-known bloggers have already migrated to Jekyll in the last few years. Ever since Tom Preston Werner created this software in 2008 and published his infamous article about Blogging Like a Hacker, it has become the go-to thing for at least the small and indie bloggers.

First I've looked at the tools I was already familiar with. I have some old blog where I've posted updates during my Google Summer of Code projects. It uses Jekyll to generate static files, automatically published by GitHub Pages. It works very well when you have the website tied to a version-controlled repository, but it's cumbersome when you need to rebuild container images or replace files in a remote volume even for small changes

I like Jekyll [1]. It is simple and open source. I am not sure about the SEO part though.

[1]: https://jekyllrb.com/

I use Jekyll (https://jekyllrb.com).

I'd switch to Hugo, but every time I try, I give up. It's not that I can't, it's too much up-front investment and fiddling than I care to deal with (recommendations and tips appreciated).

Jekyll - that I used for The ephemeral miniconf (source)

Publishing tools. By utilising a simple structure of notes stored in a local directories or online repositories like github or gitlab, with the help of the static site generators like Quartz or Jekyll it is only a matter of few minutes and you can have your own digital garden, collection of personal knowledge and everything you written. Feeling inspired? Read this: A Brief History and Ethos of the Digital Garden, a newly revived philosophy for publishing personal knowledge on the web.