Move off Webflow without losing the editor
Moving a client's site to code cuts their hosting bill and gives you a faster site you fully control. What they lose is the Webflow Editor: clicking the live page, changing the words, pressing Publish.
The problem
The hosting bill is the reason to move
A coded site on Cloudflare or Vercel costs a fraction of a platform plan. The saving disappears if you add a CMS subscription to replace the editor.
They expect to click the page
Clients who edited on Webflow or Framer will not learn a form-based CMS. They want the live site, a click and a text box.
You still want a safety net
On a platform, clients could break a layout. In code they should not be able to touch anything but content.
Worked example
A dental practice moving from Webflow to Astro
The practice edited opening hours and the team page themselves on Webflow. After the rebuild, Tova gives them the same thing on the coded site: click the hours, change them, publish.
Home
All changes savedSavedSea Point, Cape Town
Eight studios, a short walk from the beach
Each studio has a kitchen, a desk and its own bathroom. Stay a week or a season.
You turn review on for the first month, approve their changes from an email, then switch to direct publishing once they are comfortable. The repo stays yours, and so does the relationship.
What you get
The editor they already know
Click any text or photo on the live site, change it, publish. Works on a phone.
Clients can only touch content
Text, photos, links and list items. Never code, settings, deploys or the database. Anything else goes to you as a request.
Review when you want it
Direct publishing by default, or changes go to an approver first: you, someone at the client, or the editor themselves.
One site is free, so the first migration costs nothing. $9 a month per site after that, or an Agency plan for ten sites. Unlimited editors on every plan, so the whole practice can have a login.
Questions
- Can they still break the layout?
- No. Editors can change text, images, links and list items. Structure, styles and code are off limits, and anything that would change them is sent to you as a request instead.
- What about their blog or team list?
- List items (a team member, a post, a testimonial) can be added, edited and removed when the site keeps them in code or content files. Sites on a headless CMS keep using that CMS for those parts.
- Will they need a GitHub account?
- No. Editors sign in with an email link. Only the person connecting the repo needs GitHub.
Hand over the site, keep the repo.
Connect one repository and see what your client could edit, in about a minute.