Skip to content

Design System #253

@johnhooks

Description

@johnhooks

The questions

How does the current design take into account the Gutenberg design? Can it be adapted to fit that design system? It is the new system and seems to be the direction the new Admin will be heading, see the Thinking Through the WordPress Admin Experience post on the Make WordPress Design blog. If this project introduces a new design system I feel we are just compounding the issue raise by Joost de Valk in his post WordPress’ admin UI needs to be better.

The proposals

  • Use the WordPress Design Library.
  • Use @wordpress/components where possible, and contribute back any components we design to help fill out the component library.
  • Remove the concept of Dashboard notifications. How they are rendered is problematic (see Issue Layout shift on page load #183) and we should focus on rendering notifications out of the normal page flow. We can leave that type of admin alert to that old system, hopefully guiding everyone towards the new.
  • Add toast and modal notifications. They would be good replacements for the traditional Dashboard notices. Toasts can display temporal information that doesn't have to persist on the server. Modals are helpful for notifications that require user attention at the moment they are emitted.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions