Ask HN: What's your blog / portfolio stack?
Many people here post in some frequencies on their sites.
I wonder what kind of frameworks you are using and what you can recommend.
In a shared web hosting environment I'm building a React site myself, but found myself not updating it as much as I can't build on the go and am thinking about returning to a classic CMS solution. Even though I dislike all the clutter WordPress comes with, I'm used to it after all these years.
48 comments
[ 3.2 ms ] story [ 101 ms ] threadOnce it's published, Brevo automatically picks up the RSS Feed to send out my daily newsletter, since I switched from long-form sporadic blog posts to a shorter-form daily newsletter.
I've used Hugo/Jekyll in the past and liked it, but I'm used to SvelteKit now so I just stick with it, plus I could always hook up a Headless CMS still if necessary.
I might migrate to Hugo or another static site generator at some point because I'm too lazy to commit the Ruby/Gem stuff to long-term memory and I'm not using it for anything else.
A personal blog.
Stack is Django server and Sveltekit for the frontend.
I could have just used Django for everything, but I initially had bigger plans for the blog with lots of interactivity, I ended up just keeping it simple.
And apart from the domain, it’s free.
It uses Astro SSG, deployed to netlify. I want to eventually move to deploy on Hetzner VPS via GitLab CI/CD.
[0] https://yieldcode.blog/
It's not anything anyone would build today, and I would not recommend it to anyone, but it does have some very interesting properties that make some things that are often difficult very easy. Embedding dynamic content mid-article for instance is very easy because of a processing pass before a page gets handed to the view. It has a concept of ordered content filters, so by post I can declare what filters get applied and in what order. Filters include markdown parsing, as well as a syntax for injecting dynamic elements.
It's kind of my Frankenstein's monster at this point, but as an tinkerer I enjoy maintaining it. If I didn't enjoy it, I would have switched to something sane years ago.
https://donatstudios.com/
My one mark against it is the learning curve is sharp. That's okay for me, since I plan to use it to the end of my days, and so I can amortize the cost of learning it once against many decades of productivity. I have an old GitHub page for people struggling to get to base camp on its learning curve: https://github.com/Siilikuin/minimum-viable-hugo
And here are some sites I run in it:
https://andrew-quinn.me/, my barebones personal blog.
https://hiandrewquinn.github.io/til-site/, my much more frequently updated TILs. Think of this as halfway between a blog and Twitter.
https://hiandrewquinn.github.io/selkouutiset-archive/, a daily updating news archive for the Simple Finnish broadcast, happily running since 2023. The pipeline for this one is interesting, since it uses not only Hugo but Git submodules under the hood. One Git repo exists purely to curl the page I'm watching every night, and I try to mess with that one as little as possible because messing up might mean a night goes unarchived. An intermediate one submodules repo #1 and cleans up the HTML to Hugo-friendly Markdown with pandoc and sed. The final one imports this slimmed down, Markdownified version directly into its content/ directory as a Git submodule and redeploys the whole shebang every night. So far we're up to over a thousand unique HTML pages and this refinery has continued to work with only minimal changes, because we've stuck with such reliable and slow-changing tooling.
All the blog posts are just written in markdown and would be easy to migrate, but some of the fancier stuff would be harder.
Luckily if you just write drivel like me, the free tier lasts a long time
https://johnscolaro.xyz
OpenBSD, httpd, acme-client.
Blog: rnikhil.com
No database, nothing to manage. Just write, commit, and push to deploy.
https://wjgilmore.com
If something gets mathy I'll use LaTex.
https://stephango.com/vault#publishing-to-the-web
https://datbdo.com
Usually Sveltekit + Vercel for blogs and bigger projects.
- Jekyll => which generates static pages -> amazing to deploy it on Github Pages or any web server
- Rails 8 with Sitepress => for when I want to have some extra dynamic functionality. With Rails 8 running with defaults like SQLite and import maps there is little to be done for server config/installation
I prefer Markdown syntax for blogposts. It is the most "transferrable" way for blog content. Multiple other blog engines are supporting it, so if you want just to use something else, you can just take the MD files and put them there.
I also use Listmonk for my newsletter and Umami for analytics, both open source and easy to run from Pikapods.
I wrote about my publishing process here:
https://sampatt.com/blog/2025-02-18-Listmonk