A collection schema is a user interface. It is just one that only a handful of people ever see, which is why it so often escapes the scrutiny applied to the public pages.
Name fields after the content, not the layout
A field called Hero Subtitle Left is describing where it currently renders. When the design changes, the name becomes a lie that nobody can safely correct. Name it Summary and it survives every redesign.
Help text is not optional
Every field that has a constraint should say so in its help text. Ideal length, whether it appears in search results, what happens when it is left empty. Without that, the first writer works it out by trial and error and the second one works it out again.
Make the empty state safe
Assume every optional field will be left blank by someone in a hurry. If a missing cover image produces a broken layout rather than a tidy text-only card, the schema has handed a design problem to a writer who cannot fix it.
Fewer fields than you think
Each additional field is another decision at publishing time. Fields that exist for a single past article are pure cost. Prune them.
