Start with one concrete slice
A working page is a better test of an authoring model than a menu of proposed capabilities.
For a new publishing feature, begin with one reader journey. Here it is: choose a section, open a short entry, and return to the section index without losing the distinction between a note and an article.
That slice checks the things readers actually encounter: the content schema, generated path, header navigation, readable text width, and the route back to the collection. More fields only become justified once a real entry needs them.
The same discipline applies to scientific components. A chart, model, or theorem block should earn its public API by carrying one real piece of work all the way from source to a reader’s browser.