The standard website process goes: design, then write. The designer produces layouts using placeholder text, the client approves the layouts, and then the real content is written to fit the approved design. This produces websites where design and content are in constant tension.
Content-first reverses this. The content is defined — at least in outline — before the design begins. The design is built to serve the content, not the other way around.
What content-first actually requires
Content-first does not mean all the copy has to be written before design starts. It means the content structure has to be defined: what pages exist, what each page needs to communicate, and roughly how much content each section contains.
The payoff
The payoff for content-first is visible at launch. The copy fits the layout. The layout serves the content. The hierarchy is clear. And the project took less time because there were fewer rounds of revision to reconcile design and content developed independently.