The @laikacms/decap-cms Fork
The admin UI itself is a maintained fork of Decap CMS, published as @laikacms/decap-cms. It is a single-package build of the former decap-cms-* monorepo: every former package is exposed as a subpath export, and the root export is the classic app bootstrap.
The fork has been rebuilt from the ground up and little of the original implementation remains. It uses the same layered approach as Laika CMS: an agnostic core with opinionated outer layers. The Decap CMS core remains, while its opinionated parts have been extracted into separate packages. That separation is deliberate. The fork should not work only with Laika CMS; it remains completely usable as a standalone CMS without any Laika packages.
Maintaining that standalone path is also a thank-you to the Decap CMS maintainers for creating a CMS that was already mostly backend-agnostic and headless. The fork continues that work rather than turning Decap CMS into a private frontend for Laika CMS.
The fork is developed in its own repository and keeps its own documentation there. Rather than mirror that content here (and let it drift out of date), this page links straight to the live docs on GitHub — they always reflect the version you get from npm.
Fork documentation
- Overview & what's different from upstream — the single-package layout, subpath exports, and how it relates to Decap CMS v4.
- Skills index — the authored guides for working against the fork.
- Content Security Policy notes — serving the admin bundle under a strict CSP.
- Contributing — building and contributing to the fork.
- Changelog — release history.
Backend vs. admin This page covers the admin UI fork. For wiring the LaikaCMS-compatible
backend (storage, API, OAuth2) that the admin talks to, see the rest of this Decap CMS section. :::