spotify-box VS Hugo

The inspiration to use the Spotify API for this project came to me when browsing Spotify related actions in GitHub Actions Marketplace. Spotify Box is an action that fetches the user's top tracks and updates those to a Gist. I took spotify-box as the basis and modified my fork according to my needs:

HUGO is a popular and open-source static site generator framework that makes it easy to organize your files and assets where you can also leverage a taxonomy system, multilingual support, fast assets pipeline, and more. HUGO is used by millions of developers and by websites such as Bootstrap, Litecoin, Smashing Magazine, and even Flowbite.

With that in mind, I quickly narrowed down to a few challengers Gatsby and Hugo being the usual suspects.

If you turn Javascript off, the Markdown-formatted text will not display as a clickable link, but like "[hugo](https://gohugo.io/)". You would need to copy and paste the link into a browser address bar to navigate there instead of just clicking the link.

Static sites are a thing of beauty and simplicity. They're fast, secure, and easy to manage. The JAMStack movement help made it popular (after SPAs) and static site builders like Hugo and Eleventy are making it simple to build websites in this manner. I dare not mention Astro because it's the new kid making building static sites cooler than ever.

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.