-
Notifications
You must be signed in to change notification settings - Fork 4.6k
Description
In Global Styles > Browse styles, it should be possible to import, export, and save styles. The interface should accommodate all these flows:
- Allow saving user variations for each bundled style (i.e. customized “dark” variation) (same as Global Styles: Managing style variations #38333)
- Load style variations from a file
- Provide access to styles from other themes without switching to them (related to Global Styles: Allow access to style variations from any theme #45452)
- Provide an implicit warning about losing style customizations (related to Warn that customisations will be lost on style variation switch #45210, Custom colors are lost when styles are changed #48407, Style Variations: Add warning when custom styles will be lost #40561)
- Allow exporting, deleting styles
The following mockups take a stab at the above, and may in some cases replace them. Here's importing a file:
- Import file exists in ellipsis menu
- Plus exists to create a style from scratch (separate future feature)
Styles from other themes can be surfaced:
- The "Theme styles" section acts as a ToolsPanel, showing by default the active theme styles, letting you toggle on styles from other installed themes.
Saving customizations:
- Activating a style from a theme doesn't automatically save it as a custom style.
- But making any customizations to the style makes it show up under "Custom styles", with a blue dot. If you save using Multi Entity saving, or using the dropdown, the blue dot disappears.
- The ellipsis under custom styles allow saving, deleting, exporting.
As a starting point, styles imported or copied from other themes retain their stylenames from those sources. But in the future, we could explore a create from scratch + rename flow, such as this:
Issue updated Nov 3.
Initial proposal
This issue has a great deal of overlap with #38333, but takes a slightly different approach in that it is meant to include a flow for importing and exporting from files. The goal is to use the same interface to accomplish three separate flows:
- Allow saving user variations for each bundled style (i.e. customized “dark” variation)
- Load style variations from a file (import)
- Copy global styles from another theme without switching to that theme (import)
- Export, to enable items 2 and 3
Incidentally, these flows may also solve #45210, and depending on feedback, we may merge this issue into 38333, or vice versa.
In the first case, a user has picked a style variation that's bundled with a theme, but has made no other customizations to it:
- Chosen style shows as active in the list of bundled theme styles
- An ellipsis menu allows importing, exporting, and saving a style
If customizations are made to a style, or if a style is imported:
- Customized style shows up in "Unsaved styles" section, clearly delineated as separate from the them bundled styles
- Ellipsis menu shows uption to save or delete
- If saved, the style will appear in a new section, called "Custom styles"
- If further customizations are made, the "Unsaved styles" section appears again
This is a first iteration, let me know your thoughts.
Metadata
Metadata
Assignees
Labels
Type
Projects
Status



