Preview:

• https://deploy-preview-27912--material-ui.netlify.app/blog/material-ui-is-now-mui/
• https://deploy-preview-27912--material-ui.netlify.app/blog/mui-core-v5/

A WIP on the v5 blog post. For now, I'm focusing on getting feedback on the high-level proposed structure, and the key information to communicate. cc @mui-org/core

• I wonder if the title should be MUI v5.0 or MUI Core v5.0.
• I wonder if we shouldn't have @mui-org/x release its stable X v5 version at the same time, using this blog post to cover Core and X, and then since we don't plan the major versions to match, have independent blog posts.
• Fix blog mentions to author, I can't include every core members
• Next up, before the release, I want to explore producing a "What's new in MUI v5?" dev advocacy video. A few examples: https://www.youtube.com/watch?v=Ac-HWBTtLAU, https://www.youtube.com/watch?v=DxcJbrs6rKk, https://www.youtube.com/watch?v=I7CfaDYzTVM. Something that stays around 20minutes and that we can link right inside the blog post. We will need to produce video content for presenting the features of the data grid too, e.g.: https://www.youtube.com/watch?v=29ja0liMuv4. Investing time on it, could help to hire for https://material-ui.com/company/developer-advocate/, show that we care and want to dedicate time to it.

Reflecting, it feels like we might want to work on new features: backward. It seems to be a great opportunity we are not leveraging. Meaning we could start with what the Tweet/blog post will be and if we find it boring, not relevant, reiterate until we do. Prior arts:

1. Amazon's press release backward method.
2. Tailwind's philosophy of working in the open, which forces the same outcome. You have to think about how you are going to market the value to the audience, right from the beginning.