I built Commitspark, a Git-based headless CMS that runs on top of GitHub.
The primary purpose is to enable non-technical content editors to take advantage of Git workflows based on branches, pull requests and merges, without them having to learn Git.
Behind the scenes, everything content-related is driven by GraphQL and an open source library I released ( https://github.com/commitspark/graphql-api ), and for all the workflow features like PRs, commenting and diffs, I built a CMS-centric view onto GitHub using the GitHub API.
For content editors, this should feel the same as working in any other headless CMS, except now with support for much more powerful workflows. For developers, this means all the strengths of Git and GitHub can now also be applied to content (pipelines, tags, commit hashes for caching, branches for migrations, etc.).
There are many other things I am also excited about here that I'm happy to discuss, so please leave your questions below.
I built Commitspark, a Git-based headless CMS that runs on top of GitHub.
The primary purpose is to enable non-technical content editors to take advantage of Git workflows based on branches, pull requests and merges, without them having to learn Git.
Behind the scenes, everything content-related is driven by GraphQL and an open source library I released ( https://github.com/commitspark/graphql-api ), and for all the workflow features like PRs, commenting and diffs, I built a CMS-centric view onto GitHub using the GitHub API.
For content editors, this should feel the same as working in any other headless CMS, except now with support for much more powerful workflows. For developers, this means all the strengths of Git and GitHub can now also be applied to content (pipelines, tags, commit hashes for caching, branches for migrations, etc.).
There are many other things I am also excited about here that I'm happy to discuss, so please leave your questions below.