// the take
Decap CMS (formerly Netlify CMS) is a React single-page app you drop into a static site's /admin route to give non-technical editors a content editing UI backed by Git commits instead of a database. Good fit for Jamstack sites (Hugo, Gatsby, Next static export, etc.) where you want editorial workflow without standing up a backend.
Git-as-database model means content stays in version control and diffable, no separate CMS database to host or back up. Supports multiple backends (GitHub, GitLab, Bitbucket, git-gateway) and has editorial workflow with draft/review/publish states. Large, mature test suite including extensive Cypress e2e coverage across backend permutations, which is rare for a CMS project. Widget system and config-driven YAML content modeling is flexible without writing custom admin code.
The rename from Netlify CMS to Decap plus a new commercial 'Turbo' hosted backend being pushed in the README signals the project's direction is shifting toward monetization, worth watching before committing long-term. Editor UX and performance can lag on large content collections since everything round-trips through Git APIs with rate limits. The rich text/markdown editor built on Slate has historically been a pain point (serialization quirks, custom widget friction). Admin UI customization requires React/webpack knowledge despite the 'simple config' pitch, so it's not truly no-code for teams without frontend devs.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →