A site the client keeps building without me

Most Webflow sites start well and fall apart in the client’s hands. Someone duplicates a section, nudges a margin, invents a new heading style. Six months later there are fourteen shades of grey and nobody wants to touch the site.

I build so that doesn’t happen, and the approach is the same on every project.

It starts with variables: colours, type, spacing, radii, defined once, with names a non-developer can read. My setup is close to Lumos in spirit, but lighter. I kept what makes a system scale and dropped what makes it hard for anyone else to follow. A system only works if the next person can use it without me on a call.

On top of that sit the components. A typical build has 40 to 60 of them — around 30 to 40 section types and roughly 20 card variants. Each one takes content, not styling. The client changes the text, the image, the number of cards, and the layout holds.

Then the part that matters after handover. Every project gets a component library page with every section in one place, and a starter page to duplicate. To build a new landing page, the client copies the starter, pulls in the sections they need and fills in the content.

And they do. Clients on these builds regularly publish new marketing pages without calling a developer.