How we structure Webflow classes for handover
A naming system your next agency or your own team can actually read.
Webflow handover fails in the class panel, not the CMS. A developer leaves. A new agency arrives. The first thing they open is the Navigator, and if what they see reads like a database schema, the project is already in trouble. We structure classes for the person who inherits the site - not for the person who built it.
Our naming system is deliberately boring. Client-First gives us the skeleton: block, element, modifier. We add one layer of semantic naming that matches how the marketing team talks about the site. A hero section is section_hero, not div-block-47. A pricing card is pricing_card, not flex-vertical-gap-24.
Rules we actually follow
One class per job. Combo classes for state, not for layout hacks. No utility soup - if you need more than three classes on an element, the component is wrong, not the naming. Custom attributes get documented in a shared Notion page the client keeps after we leave.
A class list that reads like a sentence is a class list someone else can maintain.
We also resist nesting components more than two levels deep. Deep nesting looks organized in the Designer and becomes a nightmare in the exported code. Flat structures with clear parent-child relationships hand over cleanly.
What the receiving team gets
Every project ships with a one-page class map: which components exist, what they are called, and which CMS fields feed them. The next developer - whether that is the client's in-house team or another agency - can find what they need without a walkthrough call. That is the bar. If they need us on a screen share to change a button color, we did not hand over; we just paused.
When should you break a CMS collection into multiple?
When two kinds of content genuinely have different fields and different places they get used — not just because one has slightly more variety.
How do you handle nested references in Webflow?
Keep references to one hop wherever possible. If you find yourself needing two hops to render a single field, flatten the second collection into the first.
Do CMS items count toward site plan limits?
Yes — every collection item counts toward your CMS item limit regardless of whether it renders a page.
Enjoyed this? We build the systems we write about.
Fixed monthly retainers on Webflow and Medusa JS — by the same people who wrote this.