Purpose

Explain Decap CMS as an embedded single-page app that turns Git-backed content into a manageable editing workflow for static sites.

Composition

• Left: a content editor using /admin/.
• Center: a browser-based Decap CMS panel with collection list, editor form and publish status.
• Right: Git repository, branch or Pull Request, then static site build and CDN delivery.
• Use directional labels: config.yml, backend, commit/PR, static build.

Project-specific facts

• Git is the content source of truth.
• The CMS is a React SPA, not a hosted database server.
• Backends can include GitHub, GitLab, Bitbucket and Git Gateway.
• Editorial workflow may create draft branches or Pull Requests.

Style and constraints

Clean technical editorial illustration, restrained GitHub-inspired blue/green accents, high contrast, Chinese labels with short English code tokens, 16:9 landscape. Show concepts, not a fake screenshot. Do not imply that an image is an exact source architecture or that authentication is already configured.

Evidence

E01, E03, E04, E12