Purpose

Visualize the representative save path from the editor form through Decap CMS core and a selected backend to a Git commit or Pull Request and static-site build.

Composition

Use five horizontal stages: Editor form -> Redux/action -> Backend API -> Git branch/PR -> Static build. Add a small side branch for media upload and a warning marker at OAuth / permissions.

Project-specific facts

• decap-cms-core bootstraps config and authentication before rendering the app.
• Entry actions choose the current backend or integration provider.
• GitHub backend has REST and GraphQL implementations.
• Git Gateway adds an external identity/gateway boundary.

Style and constraints

Technical flow diagram, flat vector shapes, white background, blue for application steps, gray for Git, green for successful build, amber for permission boundary, 16:9. Keep labels short and legible. Do not draw unverified runtime metrics, real user data, or a literal UI screenshot.

Evidence

E12, E13, E16, E17, E18