Replatforming from Gatsby to Zola!

1

Obsidian.md

So I've had my fair share of personal websites and blogs. I have built them on stacks ranging from the most basic HTML and CSS, to hosted frameworks like Wordpress and Laravel, to the more modern single page applications built in Vue and React. For a simple content blog I think you can't go wrong with a Static Site Generator though. These days I am almost exclusively writing everything in Obsidian. Which is great because its all in standard markdown format. This allows for a really neat and easy content publishing workflow.

#Knowledge Management #Knowledge Base #Markdown Editor 1454 social mentions

2

Netlify

Wait as the Netlify CI/CD robots work their magic to build and push my updated blog site with the shiny new post to the open internet.

#Cloud Computing #CDN #Content Distribution 104 social mentions

3

GatsbyJS

Since around 2019 I have used Gatsby as my static site generator. Its plugin system makes it super feature extensible. It uses React under the hood which makes components easy to write and has tons of community support. Once I had a Gatsby site styled and running, publishing blog posts is fairly trivial:.

#CMS #Blogging #Blogging Platform 14 social mentions

4

Bulma

After finding a few spare hours I decided to address the alerts and update some my dependencies. I spent several hours debugging my Gatsby site after doing some recommended npm package updates. My UI class library Bulma was not being loaded by my sass-loader module. (I later learned that they migrated to dart-sass so I guess the fix should have been a pretty easy). Nonetheless, this prompted me to rethink my entire static site generator stack and got me curious about some other options. Why have these unnecessarily complex dependency chains? At that point I was almost too hesitant to even touch my package.json file. That's just silly.

#CSS Framework #Development Tools #Design Tools 109 social mentions