A Clean Collection Rarely Stays Clean on Its Own
A CMS collection that starts clean rarely stays that way. A field gets added for one blog post that needed something special. A second collection duplicates half the fields from the first because copying was faster than reusing. Eighteen months later, editing content means guessing which field actually does what.
None of this is a Webflow limitation. It's what happens when a content model gets built reactively, one item at a time, instead of planned before the first entry goes in.
Model Relationships, Don't Duplicate Data
When an author's name, a category, or a team member's bio shows up in more than one place, it belongs in its own collection, referenced from wherever it's used - not typed in fresh each time. Change the bio once, and it updates everywhere it's referenced.
Reference fields also keep the data honest. A blog post linked to an actual Author item can't misspell the name; a post with the author typed as plain text can, and eventually will.
Keep Fields Minimal and Consistent
Every collection type should share a consistent shape with the others - similar field names, similar structure, similar naming conventions - so an editor working in one doesn't have to relearn the pattern in another.
A field added for a single item is usually a sign the content model needs a rethink, not a workaround. Rich text fields for anything that's genuinely long-form, plain text for anything that's a label - mixing the two up is a common source of formatting inconsistencies that are hard to trace later.
Planned Before the First Entry, Not After the Hundredth
This is exactly what CMS architecture means as part of Webflow Development here - collections modeled around how the content actually relates, before your team starts filling them in.
If an existing CMS has turned into a maze of one-off fields, get in touch and we'll help sort out what it should actually look like.