What problem does this address?
Some development workflows strongly rely on keeping theme changes out of the database, so that dynamic content in patterns can be executed on the frontend and rendered into templates.
It's possible to see which templates have database changes in themer, but you need to search for this. It's possible for this to be missed and users to wonder why dynamic content is no longer showing correctly inside templates.
What is your proposed solution?
Consider showing more prominent warnings to users, either in the block/site editor or on the frontend (when logged in) to indicate when a template has database changes.
Consider moving the template/pattern/template part management outside of the theme.json editor and into a dedicated settings page.
What problem does this address?
Some development workflows strongly rely on keeping theme changes out of the database, so that dynamic content in patterns can be executed on the frontend and rendered into templates.
It's possible to see which templates have database changes in themer, but you need to search for this. It's possible for this to be missed and users to wonder why dynamic content is no longer showing correctly inside templates.
What is your proposed solution?
Consider showing more prominent warnings to users, either in the block/site editor or on the frontend (when logged in) to indicate when a template has database changes.
Consider moving the template/pattern/template part management outside of the theme.json editor and into a dedicated settings page.