[website] Copyedit Docs and Product menu taglines #43075
Conversation
samuelsycamore
added
the
website
Netlify deploy previewhttps://deploy-preview-43075--material-ui.netlify.app/ Bundle size report |
samuelsycamore
changed the title
| @@ -148,14 +148,14 @@ const coreProducts = [ | |||
| { | |||
| id: 'joy-ui', | |||
| name: 'Joy UI', | |||
| description: 'Beautiful foudational components.', | |||
| description: 'Delightful modern components.', | |||
There was a problem hiding this comment.
I wonder if this wouldn't be closer to the product vision, so clearer. Thoughts?
| description: 'Delightful modern components.', | |
| description: 'Material UI with a modern look.', |
There was a problem hiding this comment.
I think that mentioning Material UI there could be confusing, as users might expect the same API with a different look. For now, I believe the current approach works better, since we don't have a long-term vision for Joy UI yet. Therefore, I wouldn't position it closer to Material UI—who knows, in the future it might become something like 'Base UI with copy-and-paste styles.' 🤷
There was a problem hiding this comment.
The upside with referencing Material UI could be:
- it will make it clear why there are two libraries that seems to do the same thing
- it will speak more directly to the people used to Material UI (from the perspective of my friend who uses Joy UI, both are more or less equivalent in terms of API / learning curve)
we don't have a long-term vision for Joy UI yet
True, not completely, what we defined as a cap is that it won't exist standalone. It will either be rewritten as a skin of Material UI, and MD3 will be another skin, or be a styled extension of Base UI. Long term, what Joy UI and Material UI are today will be skins of each other under one brand.
Fix typos, eliminate repeated words, standardize descriptions, match style and structure across the menus.