Model collections, references, and templates before content becomes expensive to change.
Updated Aug 1, 202616 min readGutoFlow editorial
Model the content relationships before building collection templates; CMS flexibility comes from clear responsibilities, not more fields.
Start with content responsibilities
List the objects editors manage—projects, people, services, locations—and give each collection a single clear purpose. Repeated information deserves a reference only when it is independently maintained.
Name fields in editorial language
Separate reusable entities from page decoration
Document required and optional values
Use references deliberately
Multi-reference fields are useful for real many-to-many relationships, but they make filtering and conditional visibility harder. Test the desired collection lists before committing to a model.
Stress-test templates
Fill templates with the shortest, longest, missing, and unexpected content. Confirm empty states and migration steps while changes are still inexpensive.