Skip to content

Iterating on the "Options" settings #24965

@mtias

Description

@mtias

The settings screen has been growing gradually over time. It harbors important features and new items are already being worked on (like text only buttons). We should improve a bit its design to make it more usable and scalable.

image

Thoughts:

  • Length of options name is all over the place. Some options require additional context, but it should be provided by proper description text.
  • Some of these options should be toggles and not checkboxes compared to their function in other places of the user interface.
  • Categorization can be improved: a name like "Keyboard options" is redundant when we are already within an "Options" modal. It could make sense, for example, to have a "Blocks" category for the "most used" item and to also link to the "block manager". Disabling the "block directory" as a whole is also something that might be required here.
  • Some of the settings explored in Add more writing flow options: Reduced UI, theme styles, spotlight #22494 also make sense to be configured here.
  • We need designs for things that might have more than one state (like buttons: icon only, text only, icon + text).
  • It's likely the design would need higher level navigation as it grows in categories. Perhaps a design like what @dubielzyk is exploring for the document header could be a good fit down the road.

Example from iOS on a good use of description text to contextualize settings:

image

Metadata

Metadata

Assignees

Labels

General InterfaceParts of the UI which don't fall neatly under other labels.[Status] In ProgressTracking issues with work in progress[Type] EnhancementA suggestion for improvement.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions