I suspect that anyone who’s deploying a Hugo/Jekyll or whatever also has their own special workflow that involves updating the content and potentially tracking the changes and maybe a build step.
There are 1000s of permutations of CMS/version tracking/editors/hosting solutions but I feel like none of them cater specifically to developers because we find our own way.
I love my custom scripts. Every part of my blogging process was pieced together by me because I was interested in building the pieces. Custom editor, terminal, server in the cloud, site generator. I didn’t make all of it but it’s still unique to me.
It seems odd to me that there isn’t an open source solution to CMS.
OK, so I’ve actually heard of this one - it’s called Ghost and they did a blog a while back that explained how it can be deployed locally as a headless CMS…
Wait a minute… Ghost uses JSON. JSON? It uses JSON. What. WHY?
so that you don’t have to rely on messy microformats in your markup to provide semantic context…
Oh OK, so fair enough. And also it uses JSON for features like integration with 3rd parties and because using a preamble of TOML at the top of a markdown file is too cool I guess.
So Ghost isn’t exactly what I want because I DO NOT want JSON. I like text files, they’re simple.
I even tried using YAML for some content on my (shudders) personal website and it felt very wrong.
Markdown is where I live now, it’s cozy and basic. Comforting.
JSON is like the corporate enterprise and markdown is the hipster dev journalist trying to deploy his damn markdown website.