- Build each repeated section as a component. Structure and styles live in the main component; each instance gets its own content through props.
- Props cover text, rich text, images, links, video, numbers and switches to show or hide parts. Variants switch between set styles.
- Slots and page slots let marketers add approved components to a page without touching the design.
- Give each person the right site role: Marketers build pages from components, Content editors change content only.
- The legacy Editor is gone. Content editors now edit inside Webflow with a seat on the Workspace.
The short answer
To let marketers edit a Webflow site without breaking it, build every repeated section as a component and turn the parts they should change into props: the heading, the text, the image, the button link, a switch to hide a part. Give them the Marketer or Content editor role instead of Designer. They can then change content and build pages from your components, while the structure and styles stay locked in the main component.
Everything below is from Webflow's help pages on components, component properties and site roles.
The words you need
- Main component. The definition: structure, styles and which parts can change. Edit it and every instance updates.
- Instance. One use of the component on a page. It can have its own content through props and slots, but its structure and styles come from the main component.
- Props. The parts of a component that can take a different value on each instance.
- Slots. Placeholders inside a component where other components can go.
- Variants. Set style options for one component, such as a light and a dark hero.
Short definitions are also in our glossary under Webflow components and component properties.
Which props Webflow supports
Webflow lists three kinds of properties:
- Content props: Text, Rich text, Image, Link, Video, Number and Switch.
- Switch props for visibility: show or hide a button, an icon or a group of elements on each instance. Webflow says hidden elements are removed from the page code, so screen readers skip them.
- Collection list props: change filters, sort order, pagination, limits or curated items on each instance of a list.
Variants add one variant prop per component, with as many variants as you need. Styles set on the base variant are shared; styles on other variants apply only to them. To change other styles on one instance, Webflow points to the class custom attribute.
Props can also connect to CMS fields such as plain text, image, link, rich text and reference, so the same component works on Collection pages.
What to make a prop, and what to leave alone
| Make it a prop | Keep it in the main component |
|---|---|
| Headings, text, button labels | Layout, spacing and type styles |
| Images and their alt text | Animations and interactions |
| Button and card links | Navbar and footer content that is the same everywhere |
| Show or hide an extra button, badge or image | The order of elements |
| Light or dark, left or right (as a variant) | Colours outside your brand set |
A good test: if a marketer would ask a developer to change it each week, it should be a prop. If changing it would break the layout, it should not.
Name props in plain words, such as "Button label" and "Show second button". Webflow lets you group props and add a tooltip to each, which helps when a component has many.
Slots and page slots: building pages from blocks
Slots let a component hold other components, for example a card grid that accepts any card. Designers can set default content in a slot, and with the Designer role or higher they can restrict which components a slot allows. That limit applies to the Marketer role.
Page building takes it further. A designer places a page slot on a static page or page template, and marketers add, move and delete components inside it and fill in their props. Marketers can also start from a blank page, which comes with a page slot. Webflow notes a few limits:
- Page templates and page slots work on static pages only, not Collection pages.
- A site can have up to 40 static page templates.
- Marketers can only add components into a component's slot when it sits inside a page slot.
- Marketers can work on page branches and request review, but by default a designer merges them.
Roles: who can change what
| Can they... | Designer | Marketer | Content editor |
|---|---|---|---|
| Create new components | Yes | No | No |
| Change classes, components and variables | Yes | No | No |
| Create and edit pages using components | Yes | Yes | No |
| Add existing components to page slots | Yes | Yes | No |
| Edit component prop values | Yes | Yes | Yes |
| Edit global content inside components | Yes | Yes | Yes |
| Create and edit CMS items | Yes | Yes | Yes |
That is a short cut of Webflow's site roles table. Publishing depends on the Can publish setting for each person.
One thing to watch: "global content" is content not bound to a prop. Webflow's content editor guide says editing it changes every instance of the component. If a heading should differ per page, make it a prop. Designers can also lock single elements under Element settings, Editing permissions.
The legacy Editor is gone. Webflow's deprecation FAQ says it was fully deprecated on 5 October 2026, so everyone who edits needs a seat on the Workspace. Content editors can open a page by adding ?update to its URL.
A worked example: a hero component
Here is how we would set up a hero for Kookies, so a marketer can make a new landing page hero in a minute:
- Eyebrow (Text) and Heading (Text)
- Lead (Text, two lines at most)
- Button label (Text) and Button link (Link)
- Show second button (Switch), with its own label and link
- Image (Image), with alt text filled in per instance
- Variant: Light or Dark
The spacing, type sizes, colours and the animation stay in the main component. Ten landing pages can share the hero and still look like the same brand.
Mistakes we see
- Everything is a prop. Thirty props on a component make it as hard to use as the Designer. Keep to what really changes.
- Text that should differ is left global. Someone edits it on one page and it changes everywhere.
- Detaching instances to make one-off changes. The page drifts away from the design system. Add a variant or a switch instead.
- Designer seats for everyone. Give people the role that matches their job.
A clear system makes all of this easier. See Webflow design systems for how we plan classes, variables and components together.
What to do next
List the sections your marketers ask developers to change most often. Turn the top three into components with props, set the right roles, and let the team build one page on their own. You will find the gaps quickly.
We build component libraries in Webflow as part of Webflow development, and section libraries your team can reuse in our section library service. Tell us about your site.
Terms used: Webflow, Webflow components



