Repository navigation
Conversation
🤖 PR meta 🤖🎉 PropsIf you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. Updated as activity occurs, without notifying anyone named here. Add the 📦 Bundle sizeSize Change: 0 B Total Size: 9.07 MB
|
simison
added
[Type] Developer Documentation
…ction Show Theming, Components, Icons, DataViews and Admin UI as cards with abstract SVG headers, a short description, and links to the Storybook page and the developer handbook.
Rework the copy, show the principles as cards, and tune the package cards.
b42b150 to
f7647a3
Compare
| - **Consistent visual language**: Drawn to a shared style so icons feel coherent wherever they appear across WordPress. | ||
|
|
||
| See the [`@wordpress/icons` README](https://github.com/WordPress/gutenberg/tree/trunk/packages/icons) for usage details. | ||
| <PackageCards only={ [ 'theming', 'components', 'icons' ] } /> |
There was a problem hiding this comment.
@ciampo 's feedback at #84864 (comment) got me thinking about how .mdx as its used to represent content can create issues when that content is obfuscated behind components. I don't know that we do or would use this page as raw content, but in a general sense it feels like Markdown is where the human text should live, not in the component implementation. And that we could use (sub-)components to handle the structuring. What would you think about moving some of that content back into this file?
What?
Essentially, trying to condense this as an "introduction" page that is easy to skim.
Why?
How?
Testing Instructions
Testing Instructions for Keyboard
Screenshots or screencast
Use of AI Tools
yes