This is fantastic news, and I'll definitely be taking a look. I do want to point out, however, that there are a number of benefits to having your content in a Git-backed file repository, rather than in a centralized database.<p>I understand why Ghost would want to promote using a headless CMS with a database—it's great PR—but I hesitate recommending this as a slam-dunk solution. For me, generally speaking, all the sites I build now are JAMstack (Jekyll, with a custom Rails-based content editor), and having all the website content in a Git repo is a huge part of that workflow and a major selling point.
Hi HN! John from Ghost here - happy to answer any questions about this. We rebuilt our docs using Gatsby and the Ghost API last year and ended up liking it so much that we rearchitected everything to make the the JAMstack workflow a first class citizen :)
I love this, while the rest of the industry is focussing on coupling admin interfaces with the front end, Ghost's focus on decoupling is a no-brainer.<p>Incredible work!