| You mentioned that content changes are versioned in Git using the Netlify workflow. Why would that be useful if not for being part of an editor workflow? If it's not part of the editor workflow, is it part of the development workflow? What are we comparing this to? versioning in Google Docs? MySQL? How is it something I should "love?" > Migrating static sites where the content + theme are all stored in Git is a dream compared to WordPress. Wordpress (and similar) site migration has been a well solved problem for quite some time. Sure, there might be easier ways to do migration but that's a long ways down my list of things to worry about when choosing my tooling. Ease of migration isn't much of a consideration. > A lot of WordPress sites aren't even under source control... A lot of Wordpress sites are a dumpster fire actively attacking the internet. That's not the sites I build and manage. I'll create static websites for my own usage, but not for buyers of my services. Any headless CMS service (as opposed to self hosted) is really just an option of interfaces on the market. Of the things which matter to buyers, that interface is everything on the back-end (the site as a whole has more important goals.) The buyer doesn't care about ease of migration, how content is stored, etc. Only developers care about these things. So, let's talk about what buyers want, not developers. If a X headless CMS service can provide the best UI for the buyer, then that's what everyone should default to. If not, then all other bullet points don't matter. |
All state is stored in Git and Netlify CMS is just a client-side JS script that talks directly to GitHub. It's an interesting approach that suits some projects. Don't read into this comment more than that.