One of the side benefits of the Gutenberg project has been the creation of a growing library of components that take accessibility as a primary concern and seek to make building rich interfaces for WordPress easier, more consistent, and more maintainable.

Most of these have grown organically as the interface needs evolved. We are at a point where it makes sense to circle back and refine the set in a more holistic way. These are the areas I think need most immediate attention.

Component Library

• Build or adopt a live component gallery (playground) where:
• • Components can be easily found, previewed, and its properties explored.
• • Documentation and guidelines on how to use them can be accessed.
• Ensure corresponding libraries in design tools (like Figma) are in sync.

Audit

• Review component semantics and structure:
• • Are the component names clear and appropriate?
• • Are properties well thought out and consistently applied?
• • Are there gaps that need to be addressed?
• • Is documentation exhaustive?
• Coordinate with mobile group to make sure components are meaningful cross-platform.

Related: #7534

Grouping

• Define meaningful groups (for example, a "buttons" group would include Button, ButtonGroup, ClipboardButton, IconButton, FormFileUpload, etc) to simplify discovery and navigation.