Ask HN: What stack is your personal blog built on?
1–10 of 80 posts
Re: Ask HN: What stack is your personal blog built on?
#2What I learned from my experience: I should have stuck to Wordpress. SSH'ing into my server, loading the environment variables, and running the generation script was often friction enough for me to file a post under "finish later", from where it never came back. For all its faults, Wordpress made it super easy for me to share an idea right there and then. Technology was not my problem - friction and writer block were.
Re: Ask HN: What stack is your personal blog built on?
#3Also I used Docker for containerizing and Jenkins for Continous Integration but it was only in order to practice DevOps skills.
Re: Ask HN: What stack is your personal blog built on?
#4Re: Ask HN: What stack is your personal blog built on?
#5Re: Ask HN: What stack is your personal blog built on?
#6Re: Ask HN: What stack is your personal blog built on?
#7Re: Ask HN: What stack is your personal blog built on?
#8Re: Ask HN: What stack is your personal blog built on?
#9Built using:
- gatsby (static site generator)
- netlify CMS (git-based headless CMS)
- GitHub (git remote for netlify)
It was dead easy to set this up, as someone had already done the work: https://github.com/alxshelepenok/gatsby-starter-lumen
I tried to set up something similar from scratch myself, using Strapi as the CMS, but I found myself re-inventing too many wheels (e.g. how to allow a blog post to include an arbitrary number of inline images).
So when I found this great starter project, I went with it. There's zero maintenance for hosting the site or CMS. But I can still customise whatever I like, and deploy with a simple git push.
Re: Ask HN: What stack is your personal blog built on?
#10It's my favourite stack because hosting and running a website / blog is neither my core business nor my core expertise.
Last time I checked, WordPress was still easier to use and to maintain than static site generators. The plugin ecosystem is huge and provides ready-to-use solutions for common (and not so common) use cases that I therefore don't have to implement myself.