Skip to content

Decap CMS Integration ​

Decap CMS is a Git-based admin UI for content. Laika ships a Decap-compatible backend (@laikacms/server) so you can pair that admin with any Laika storage repository — filesystem, R2, S3, WebDAV, and more.

Laika works with upstream Decap CMS and maintains a standalone @laikacms/decap-cms fork. The fork follows the same separation of an agnostic core from opinionated outer packages and can be used without Laika. It is a general-purpose continuation of Decap CMS, not an admin UI coupled exclusively to this project. See the fork overview for its documentation and the boundary between the admin UI and the Laika backend.

Two integration shapes are supported, in increasing order of complexity:

PatternWhen to useBackend hostAuth
Hosted gatewayMultiple sites sharing one Decap admin + Laika backendA separate Worker / server you operate (the laika-gateway app moved to its own repo)GitHub OAuth (or other provider)
Standalone WorkerYou want full control of storage, auth, and routingYour own Hono/Worker appJWT (or your scheme)

The primary documented integration path is the Standalone Worker (BYO storage) wiring: you construct a StorageRepository, wrap it in the Catalog document/asset repos, and expose them through laikaApi(...). Everything else (admin shell, OAuth2, framework bridges) builds on top of that handler.

In this section ​

Released under the MIT License.