While we work on the baseline content only experience, it would be helpful to isolate the inspector/editable fields feature in order to:

• compare the user experience with and without this feature
• allow folks to solidify the on-canvas experience and focus on polishing/bug fixing without the added distraction of another editor interface
• following on from the above, it could enable the baseline feature to land first rather than trying to juggle two large pieces of functionality

One idea was to create an experiment within an experiment. Gutenberg inception.

See related design proposals for the integrated approach:

• Design idea: Pattern editing and contentOnly interactivity #73466