30 pages in three weeks, without cutting corners

The brief came in with the launch date already fixed. Around 30 pages, motion across every section, and a client who would notice if anything felt rushed. We had three weeks, revisions included.

I wasn’t building it alone. There was a second developer on the project, which sounds like it halves the work. It doesn’t, unless the foundation lets two people build in parallel without drifting apart.

So the first days went into things nobody would see. Project structure, variables, and a new CMS architecture — the content was coming over from the previous Webflow site, and it was the right moment to restructure it rather than copy the old collections as they were. Before a single page went up, the component library existed. Every section and card type was defined once, with spacing, type and states locked in.

That’s what made splitting the work possible. I assigned pages, and we both built from the same components. When something came back slightly off — a card with the wrong padding, a section built as a one-off instead of from the system — I flagged it straight away. On a three-week build, one inconsistency on day three turns into forty by launch.

The obvious place to save time was the animations. They took the longest and were the easiest to drop. The client insisted they stay, so they went back in. Because the system was already solid, adding motion meant working on top of clean components, not untangling the layout at the same time.

We launched on the date. The revision round was short, and most of it was content rather than build.