Ask HN: What's your blog / portfolio stack?
11–20 of 49 posts
Re: Ask HN: What's your blog / portfolio stack?
#12It uses Astro SSG, deployed to netlify. I want to eventually move to deploy on Hetzner VPS via GitLab CI/CD.
Re: Ask HN: What's your blog / portfolio stack?
#13It'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.
Re: Ask HN: What's your blog / portfolio stack?
#14My 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.
Re: Ask HN: What's your blog / portfolio stack?
#15All 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
Re: Ask HN: What's your blog / portfolio stack?
#16Re: Ask HN: What's your blog / portfolio stack?
#17OpenBSD, httpd, acme-client.
Re: Ask HN: What's your blog / portfolio stack?
#18Blog: rnikhil.com
Re: Ask HN: What's your blog / portfolio stack?
#19No database, nothing to manage. Just write, commit, and push to deploy.
Re: Ask HN: What's your blog / portfolio stack?
#20If something gets mathy I'll use LaTex.