How to build a Webflow site your marketing team can edit without a developer
Why many Webflow sites get hard to edit a month after launch, and the five things I build in so a marketing team can change pages, publish CMS content and launch landing pages on its own.
By Senad Secerovic
The problem
A lot of Webflow sites look great on launch day and get hard to change a month later. The marketing team wants a new landing page, but every section was built once, by hand, with its own one-off styles. So every small change goes back to a developer.
It doesn't have to work like that. Here are the five things I build into every site so your team can run it on its own.
1. A class system, not one-off styles
I use a consistent naming system based on Client-First, so classes describe what they are, like section_pricing or work_card-title. When the same card appears on three pages, it uses the same classes. Change it once and it changes everywhere, and new pages don't break the old ones.
2. Variables for spacing, type and color
Spacing, font sizes and colors are set as Webflow variables. If your design comes from Figma, the variables match your Figma styles. Your brand color or heading size is changed in one place, not on fifty elements.
3. Reusable sections as components
Hero sections, feature lists, pricing tables, FAQs and calls to action are built as components with editable fields. To build a new landing page, your team drops in existing sections and changes the text and images. No new design work, no developer.
4. CMS for anything you publish more than once
Blog posts, case studies, job openings and similar content go into CMS collections. Your team adds an item in a form, and the page is built from a template that already looks right.
5. A recorded walkthrough of the Editor
Every project ends with a recorded walkthrough of your site's Editor, made for your team. New people can watch it later instead of asking someone how the site works.
What your team can do after launch
- Edit any text, image or link in the Webflow Editor.
- Publish blog posts and CMS pages on their own.
- Build new landing pages from ready-made sections.
- Update pricing and feature pages the same day.
What still needs a developer
Some changes are real development work: a section type that doesn't exist yet, a new CMS collection, a new integration or a change to the site's structure. That's what monthly support is for, and it's a much shorter list than “everything.”
Questions to ask before you hire a Webflow developer
- Will the site use a consistent class system?
- Will sections be reusable components my team can add to new pages?
- Which content will live in the CMS?
- Do we get a walkthrough of the Editor at the end?
- Will the site be in our own Webflow account? It should be.
If you want a site built this way, book a 20-minute call.
Let's build it.
Have a Webflow project in mind? Tell me what you need on a 20-minute call and I'll tell you honestly if I'm the right fit, what it would cost and how long it would take.