A CMS for static sites — without migrating anything
Your static site doesn't need a rebuild to become editable. Unfreez connects to the repo, finds every text and image, and gives your client a safe editor. Every change is a clean commit.
Why “add a CMS” usually means “rebuild the site”
Traditional content management assumes it owns your content: templates, schemas, databases, build pipelines. Retrofitting one onto a finished, hand-coded static site means rewriting the site around the CMS.
Unfreez inverts the relationship. The site stays exactly as you coded it — a folder of HTML, CSS and JavaScript in a Git repository. Unfreez scans the files, anchors every human-facing value in the markup, and exposes them in a visual editor your client can actually use.
What your client gets
A live preview of their own site. Editable zones highlight on hover; a tap opens a plain editor for text, photos, and list items (add a testimonial, remove a menu entry — within the bounds you set). Publish turns the whole basket into a single commit.
What you keep
Everything. The repo, the history, the deploy pipeline you already have — or none at all: a publish is just a commit, deploy it however you like. If a target is ambiguous after you changed the code, Unfreez refuses to write and asks you to revalidate. It never guesses.