Once #7362 lands, we'll have the ability to register new block variations (based on classes) with automated previews. With this foundation there are further ideas of how this functionality could be extended.

Register New Styles

Themes / Plugins should be able to easily register new variations from the client or server.

Unregister Existing Styles

Themes / Plugins should be able to unregister existing block style variations for a specific block. (A plugin may also want to disable style variations entirely across all blocks.)

Change the Default

A Plugin / Theme might want to make a specific variation the default one for that block type.

User Defaults

A user might want to make a specific variation the default whenever they insert a new block of the type.

• Allow setting a default variation for the user (locally stored?).

Custom User Styles

A user might be able to write a custom class (in the "Advanced" block tab) and register it as a block variation.

Concept:

Package Customizations as Classes

A user should be able to modify the aspect of a block (padding, font-size, etc) and save this not as inline styles but as a specific class to be reused. These don't necessarily have to become "style variations" but should be selectable in the advanced -> class input.

Show Style Variations in Class Selector

Style variations should also probably be exposed in the class selector.