Decap CMS

Purpose: Managing and publishing content for static websites without relying on a proprietary hosted CMS.

Inferred · not functionally tested

Audience: developers and editorial teams managing static websites

Inferred · not functionally tested

Functions: collaboration

Inferred · not functionally tested

Interfaces: API: unknown · MCP: unknown · CLI: unknown · Self-hosting: indicated (inferred, not tested)

Recorded constraints: pricing: open_source · license: MIT · platforms: WEB · deployment: browser, self_hosted

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: decapcms.org · github.com. These links do not verify the individual claims.

In the Knowledge base & wikis space, Decap CMS takes a focused approach. Inferred · not functionally tested: It focuses on managing and publishing content for static websites without relying on a proprietary hosted CMS. Inferred · not functionally tested: It is built as an open-source project for developers and editorial teams managing static websites. Basis unknown · not verified: The project is open source (MIT). Basis unknown · not verified: It runs on the web, and it can be self-hosted.

Behind Decap CMS is Decap Project, and it first shipped in 2016. Development happens publicly on GitHub with 19.3k stars and 57 commits in the last 90 days. Inferred · not functionally tested: Among its 6 catalogued features are visual editor, structured fields, and rich text editing.

Summary written by a language model from the project’s public pages.