Most website platforms keep your site inside their system. Edit, click publish, and the vendor’s servers show the new page. That works — until you want to see exactly what changed last March, host the site somewhere else, or leave.
Sentra CMS works differently. Editors still click publish. Behind the scenes, Sentra CMS builds the site into plain, static files and commits them to a Git repository that belongs to your city. Your host serves the site from that repository.
What you get
A complete history. Every publish is a commit with a readable message: what changed and who published it. Years later you can see the site exactly as it looked on any day — useful for records requests and disputes.
Rollbacks without panic. If a change goes wrong, roll back to any earlier publish. Sentra CMS does it with a new commit, so the history stays intact.
Hosting choice. Static files can be hosted almost anywhere: your own server, a cloud bucket, a static hosting service, or with us. Many hosts can deploy from a repository automatically.
Speed and resilience. Static pages are fast and have very little to break. If the editing system is down for maintenance, the public site keeps running.
An easy exit. Your site already lives in your account. If you ever leave, you take the repository with you — no export project.
What stays dynamic
Some things need a server: form submissions, alert sign-ups, search answers and the resident portal. Those post to Sentra CMS’s secure endpoints, so they keep working on a static site.
What your IT team needs
- A Git repository (for example on GitHub or GitLab) in the city’s account
- A deploy key, which Sentra CMS generates for you; you paste the public half into the repository settings
- A host that deploys from the repository, or our hosting
Not ready for Git? Sentra CMS can also publish over SFTP, to cloud storage, or host the site directly.