The editor handbook we ship with every project
A look at the 14-page document we hand to marketing teams on day one — and why content velocity doubles when you write it before launch.
Every Factor1 project ships with a 14-page document we call the Editor Handbook. It's not a manual — it's an agreement between the development team and the marketing team about how the site works and who owns what.
Content model reference One page per content type: what each field is for, character limits, image dimensions, which fields are required vs optional.
Editorial guidelines House style for headlines, CTAs, and alt text. Just the decisions we made in the component library that editors need to know about.
Referenced in this article
Twelve programs, one shared component library, zero accessibility regressions.
Common workflows Step-by-step for the five things editors do most: publish a new page, update a homepage section, add a team member, create a journal entry, roll back a mistake.
What to do when something looks wrong A decision tree. Is it a content problem? Is it a code problem? Is it a permissions problem? The document takes us about three hours to write. Content velocity doubles in the first quarter.
Related work