Start with what you are thinking, and let the structure follow
A new blueprint starts with only the sections its template requires, and collections, groups, templates, and properties are made from where you work, so you rarely need to open Framework Settings.
New
Required sections
A template marks the sections every blueprint needs, and a new blueprint starts with those alone; the Health Check asks for the others only if you turn that on. Templates →
Add a missing section in one click
The Editor shows the sections a blueprint lacks, greyed in their place; hover one and press + to add it with its default content.
Make things where you work
The + beside Collections makes a collection, New group… in the New form makes a group, and a property the framework lacks is promoted from its row. Templates are added, renamed, and removed on the Templates page. Browser →
A diff viewer in the app
A change in Source control or a commit in File history opens side by side or inline, and a change is discarded from its row. Git →
Improved
A template builder in your words
Build a template from sections and sub-sections down to H6, each required or not, without picking heading levels. Templates →
Readable property names
date_createdreads Date Created in panels and tables; turn Readable property names off under Preferences → General.Collections say what they make
Edit or delete a collection from the ⋮ beside its New, and the New form and the palette name the unit (New spec) rather than blueprint.
Changed
Unknown properties are quiet
A property the framework does not declare is no longer a warning; turn on Warn on unknown properties to see them again. Canvas node styles moved to Canvas settings. Canvas →
Fixed
Settings that tidy up after you
Removing a folder in Framework Settings deletes it, asking first when it holds files, the toolbars stay put while you scroll, and a custom property's name stays in its column.