Core Concepts
Git Sync
Understand how Broslunas CMS interacts with your repositories. Each major action is a commit, ensuring total traceability.
Lifecycle of a Change
1. Draft
When you edit content and press Save (without publishing), changes are stored in our Cache Database (MongoDB).
No changes are made to GitHub. Your repository remains clean while you work.
2. Commit & Sync
By pressing Publish or Save and Sync, we compile the final file (with its Frontmatter and body) and send a direct commit to the GitHub API.
commit message: "Update post-slug from CMS"
3. Revalidation
GitHub confirms the new SHA of the file. We update our internal reference to ensure we are synced with the source of truth.
Conflicts and External Changes
If you or your team edit a file directly in GitHub or VS Code, the CMS will detect that its cached version is old. You will see a prompt to "Sync from GitHub", which will discard your local drafts and bring in the latest version of the repository.