Webflow Editor vs Designer: what your marketing team can change
For marketing leads and teams on Webflow: see what the Editor lets you change alone, what still needs the Designer and how to build a CMS that keeps you independent.
On this page
Your launch date is fixed, the new landing page is written, and the only person who can put it live is a developer with a full queue. Marketing teams on Webflow meet this wall often. It usually has less to do with Webflow than with how the site was set up.
Webflow Editor vs Designer is the question behind it. The Editor is where your team writes and publishes. The Designer is where layout and structure are built. The short answer: your team can change text, images, links, CMS items and the SEO fields your templates expose, and a designer or developer handles layout, interactions and new templates.
This article shows who works where, which jobs are already yours, how to set up the CMS so that list grows, and what to check before handing the site to your team. You will be able to sort your own change requests into two piles and decide whether you need a small fix or a rebuild.
Key takeaways
- The Editor covers text, images, links, CMS items and the SEO fields your templates expose, so most weekly content work needs no developer.
- The Designer is for layout, styles, interactions and new templates, which is work best planned in a regular batch.
- How the CMS is structured decides how much stays editable: the more content lives in fields, the less lives in the layout.
- A handover checklist with roles, fields and a test edit makes day one independent for your team.
Webflow Editor vs Designer in plain words
Webflow gives one site two working areas: one for writing and publishing, one for building. Knowing which is which tells you who can do what on the day you need a page live.
The Editor: where your team writes and publishes
The Editor is the mode where you click on the live page and change what is there. You type into a headline, swap an image, fix a link or add a new post to the CMS. Layout controls are simply not offered, so a content change cannot move a section by accident. Webflow University's intro to the Editor (opens in a new tab) is a good first page to share with a new team member.
The Designer: where layout and structure live
The Designer is the visual builder. Someone sets grids, spacing, fonts, breakpoints, interactions and the structure of every template. It gives full control over the design, which is why it suits a trained person. A small change to a shared style can alter every page that uses it, so it deserves a check before it goes live.
Workspace and site roles: who gets which door
Webflow sets access at two levels: the Workspace that holds your sites, and each site inside it. Roles at those levels decide who can open the Designer, who can use only the Editor and who can publish. Roles, seat types and limits change over time, so check the current list on Webflow University (opens in a new tab) before you invite people. Give each person their own login, so every change has a name next to it.
Write and publish
The Editor
You change words, images, links and CMS items on the live page. You can publish a campaign page the day it is approved.
Build and structure
The Designer
Your designer or developer sets layout, styles and templates. You can ask for structure changes in one planned batch.
Who gets which access
Workspace and site roles
Each person gets the access their job needs. You can invite a writer without handing over the whole design.
Think of it as two desks in the same office. Writers sit at one with a publish button. Builders sit at the other with the grid and the layers. Both work on the same site, so what the builder prepares at one desk, the writer fills at the other.
What your marketers can edit alone
Most of a marketing team's week is content: new posts, updated offers, corrected details, fresh photos. All of that belongs to the Editor, as long as the site was built with the content in editable places. Every request your team has follows one of two paths, shown below.
Where a change goes
- 01Change request arrivesText, image, link, CMS item or SEO field?
- AEditorSame-day publish
- More CMS fieldsEditor share grows
- BDesignerWeekly batch
- Layout or interactionNew template also goes here
Decision flow showing content requests going to the Editor for same-day publishing and structure requests going to the Designer in a weekly batch
Text, images and links on any page
Open the page in the Editor and click what you want to change. Headlines, paragraphs, button labels, image swaps and links are yours. A campaign page built from an existing template can be rewritten in an afternoon. Add alt text when you swap an image, so search engines and screen readers still understand it.
CMS items: posts, case studies, team pages
Each item in a CMS collection is one record: a post, a case study, a team member. You create a new item, fill the fields, and the template lays it out in the same design as the rest. That is how a new case study goes live without anyone touching the layout. Items can stay as drafts until you are ready, so preparing content never waits on a developer. The explainer on how Webflow's CMS works covers the concepts behind collections.
SEO fields, titles and descriptions
On CMS pages, the page title and meta description can be fields on each item, so you set them while you write. This works only when the build binds the template to those fields, which is a small job for a developer and part of the checklist below. For static pages, what your editors can change depends on current Webflow permissions, so check the documentation or ask whoever built the site.
Publishing and previewing a change
Before anything goes live, you can look at the change in the Editor. Whether editors publish live or only save work for someone else to publish depends on the permissions you set. Decide this on purpose. A team that publishes alone moves faster, and a review step suits legal pages or high-traffic pages. If this is the outcome you are after, our page on editing without a developer shows how we plan for it.
What still needs the Designer
Some jobs change how the site is built, not what it says. They belong in the Designer, and it helps to know them so you can plan them instead of being surprised on a launch morning.
Our pick for weekly content work
Editor
- Text, images and links on existing pages
- New CMS items, saved as drafts or published
- SEO fields that the template exposes
- Publishing, according to your permissions
Planned in batches
Designer
- Layout, spacing and shared styles
- Interactions and animations
- New page templates and collection pages
- Collection fields and structure
Layout and style changes
Moving a section above another, switching a grid from three columns to two or updating the brand colour is Designer work. Shared styles touch many pages at once, so a person who knows the system should make the change. Collect these requests in one list and send them together instead of one by one.
Interactions and animations
Scroll effects, hover states and menu animations are built in the Designer, and they can affect how fast a page feels. A heavy animation on a landing page can slow it for visitors, so plan them with someone who watches speed. Our post on launch speed and design control for marketing teams covers that balance.
New page templates and collection pages
A new type of content, such as a webinar page or a resource library, needs a new collection and a template to display it. That is a one-off build, and afterwards your team fills it alone. If the structure is more involved, a Webflow developer who knows CMS architecture and custom code is the right person to brief. Many teams settle on a regular slot for this work, for example every two weeks, so Designer jobs never block a Tuesday publish.
Set up the CMS so marketers publish alone
The size of your editable area is decided before anyone opens the Editor. If content lives in fields, your team owns it. If it lives in the layout, a developer does. A well-structured CMS is the most useful thing you can ask for, and it is often a smaller job than a rebuild.
One collection per content type
Give posts, case studies, team members, FAQs and testimonials a collection each. Every collection has fields that match what you write: a case study gets a client, a challenge, a result and an image, and a post gets an author, a category, a date and a body. When types stay separate, your team always knows where to add something new.
References that connect related content
A reference field links one item to another: a post to its author, a case study to its service, a team member to their role. Update an author's bio once and every post shows it. Related content blocks also fill themselves, so nobody edits a list by hand on each page. The Webflow University intro to the CMS (opens in a new tab) explains collection and reference fields step by step.
Rich text for long pages and posts
A rich text field holds headings, lists, images, quotes and links in one place. It suits posts, guides and legal pages, where the length changes each time. The builder styles each element once, and your writers get consistent formatting just by using the field. For content with a fixed shape, such as a pricing row, separate fields work better than one long block.
Fields for everything that changes often
Write down what changes more than once a quarter: the announcement bar, button text and link, badges such as 'New' or 'Sale', the hero headline, featured items. Each of these deserves a field or a CMS item. A small collection with a single item for site settings is a handy home for global values.
For example, a services firm has a promo banner typed into the layout, so each new offer means a ticket. Move the banner into one CMS item with a text field, a link field and an on and off switch, and the team changes it whenever the offer changes. The example is illustrative, and the effect is easy to check on your own site.
A launch checklist for handing over the site
Handing a site to a marketing team works best as a short routine run before launch day. It turns the idea of independence into a list someone can tick.
Before launch: roles, fields and a test edit
Run the list below with the person who built the site, in the order that suits you. The test edit matters most: if a real change is hard on the quiet day before launch, it will be harder on a busy one.
- Give each team member their own login with the access their job needs
- Decide who can publish live and who saves work for review
- Create a field for every block that repeats or changes: banners, calls to action, badges, testimonials
- Bind the SEO title and description to fields on every CMS template
- Fill the help text of each field so it says what to write there
- Run a test edit: change a headline, add a CMS item, preview and publish
- Write a one-page guide with screenshots of your own site
- Agree a routine for Designer work: one list and one regular slot
In the first month: training and a request routine
In the first week, sit with the team while they publish a real post, and note every moment they hesitate. In the second week, turn those questions into fields or lines in the guide. By the end of the month, review the requests that still reached a developer and sort them. If most could have been fields, add the fields.
On sites we run, Client Feedback lets your team click an element and ask for a change, so the list for the next batch builds itself. A short training session and a few new fields often remove most tickets before any rebuild is needed.
Mistakes that send every change to a developer
These setup errors are common and fixable. None of them means the site was built badly: they usually come from a launch under time pressure, when content was typed in where it looked right.
Content typed into the layout
A team list built as eight copied blocks looks fine until you need a ninth person. Now adding one is a layout job. Built as a collection, it is one new item. The same goes for testimonials, service lists and logos: if you see the same block repeated by hand, a collection should replace it.
Duplicated pages instead of one template
Copying a page for each location, service or case study works on day one. Later, a layout fix has to be made on every copy, and each new page needs a Designer to duplicate it. One template plus a collection means a new page is a new item, and a layout fix reaches all pages at once.
Missing fields for banners, CTAs and badges
The smallest elements cause the most tickets. A button that says 'Book a call' today and 'Get a quote' next month, a banner for a seasonal offer, a badge on featured items: each should be a field. Ask your team which small changes they waited for last quarter, and you have the field list.
One shared login for the whole team
A shared login leaves no record of who changed what, and it cannot be closed for one person who leaves. It also gives everyone the same access, including to the Designer, where a stray click can alter a shared style. Separate logins with the right access keep your team fast and your design safe.
When custom code limits what you can edit
Custom code adds things Webflow does not do alone: a calculator, a booking widget, a script that formats prices. It also hides content from your team. A value written inside code is not a field, so the Editor never shows it.
Embeds and scripts hidden from the Editor
A phone number inside a script, a price inside a calculator, or text inside an embed block all stay out of the Editor's reach. Each change then goes to whoever has Designer or code access. Third-party widgets, such as a booking tool, usually have their own settings in their own dashboard, so know which tool holds which value.
Rule of thumb
Any value written inside custom code is invisible to the Editor. Ask your developer to read it from a CMS field instead, and your team keeps control of it.
Asking for code that reads from CMS fields
A developer can add a CMS field, pass its value to an element as a custom attribute, and have the script read that attribute. Your team then edits the value in the Editor, and the code picks up whatever they wrote. Put one sentence in every brief: every value that marketing changes must be a CMS field. The same sentence is worth repeating when you review a developer's work before launch.
Where to start this week
List the last ten change requests your team sent to a developer. Next to each, write Editor or Designer. Then mark the Designer ones that one extra field would have turned into Editor jobs.
For example, if four of the ten were banner or button changes, four fields may remove a large part of the queue. That count is only an illustration, and your own list gives the real one.
Bring that list to werun.dev and tell us your goal. We reply within 2 hours on business days, and we tell you in writing whether you need a training session, a few new fields or a rebuild. If you want the wider picture of how we look after these sites, see our Webflow work.
Frequently asked questions
Can marketers edit a Webflow site without a developer?
Yes, for content: text, images, links, CMS items and the SEO fields your templates expose, all through the Editor. Layout, interactions and new templates still need the Designer, so a designer or developer stays involved for those jobs.
What is the difference between the Webflow Editor and the Designer?
The Editor is where you change and publish content on the live page. The Designer is the visual builder where layout, styles, interactions and templates are made.
Can the Webflow Editor change the layout or design of a page?
The Editor offers content changes only, so layout and style controls are not there. Layout changes go to the Designer, ideally in a planned batch.
Who can publish changes in Webflow, and how do permissions work?
Access is set at Workspace level and at site level, and roles decide who opens the Designer, who uses only the Editor and who publishes. Roles and seats change over time, so check the current list on Webflow University.
How do I set up Webflow CMS collections so my team can edit them?
Create one collection per content type, with a field for each thing you write. Add reference fields to connect related items, use rich text for long bodies and write help text on every field. Then test the template with one real item.
Do we need a developer after the Webflow site launches?
For a small, planned amount of work: new templates, interactions, integrations and custom code. Day-to-day publishing should not need one when the CMS holds your content in fields.