[blog] Introducing Material UI and MUI X v9#48157
[blog] Introducing Material UI and MUI X v9#48157joserodolfofreitas merged 65 commits intomui:masterfrom
Conversation
Netlify deploy previewhttps://deploy-preview-48157--material-ui.netlify.app/ Bundle size report
|
1d11e81 to
a412d54
Compare
|
Nice! It would be helpful to include a section highlighting the changes to the terms of use and telemetry. |
mapache-salvaje
left a comment
There was a problem hiding this comment.
comments for chatbox and half of scheduler - ran out of time but will circle back ASAP, and I figured some of this feedback may apply to the other posts as well
rita-codes
left a comment
There was a problem hiding this comment.
I left a couple of suggestions on specific wording (virtualization, DnD details, recurrence/timezone framing). Other than that, this is great!! It presents the Scheduler in a really appealing way and makes it look super compelling ✨
Thank you for putting this together! I'm excited to see it out there!
4fdc319 to
29f1253
Compare
9bcf2d9 to
6b2c5b8
Compare
There was a problem hiding this comment.
I have updated the structure of the posts to it feel like the main one could be a conference keynote, and the other posts would be different product announcements: WWDC26 vibe.
I have also tried to clean up the rest of the structure, so we have a great backbone to fill with content.
The main gaps I see now are:
- Filling the content. There are a lot of sentences that I couldn't make sense of. They felt marketingish (unclear value, or value with no proof). So we need to replace the vague sentences with concrete value descriptions, simple messages, and proofs anytime we make important statements.
- Visuals, making it easier to understand what we shipped.
- Covering the price changes that ships at the same time, in the main header, we need to reference https://mui.com/blog/2026-MUI-X-price-changes/.
- We have each component team review the post. If maybe the leads can add their names to the posts, kind of like ✍️ our work, this could be great too. For example, I have added myself as a second author to the main post.
- (what I plan) The date formatting improvement. I'm planning (hopefully find time) to remove this from this PR to its own PR; it's a valuable change on its own.
I think we are on the right track, we are 1/2 there 👍
- If we really wanted to show proof of work, we would have an intro video like https://heroui.com/docs/react/releases/v3-0-0 (without the sounds, god that's horrible to be on by default) or even better: https://bun.com/blog/bun-v1.0. But, yeah, that's time-consuming.
There was a problem hiding this comment.
Does it make sense to update the notifications.json in this PR?
I'd do it on a separate PR, just because the moment we merge, the notifcation is there, but the blog post might not be there yet. |
I see, that makes sense. |
Co-authored-by: Siriwat K <siriwatkunaporn@gmail.com> Signed-off-by: José Rodolfo Freitas <joserodolfo.freitas@gmail.com>
Co-authored-by: Rita <47579513+rita-codes@users.noreply.github.com> Co-authored-by: Jose C Quintas Jr <juniorquintas@gmail.com> Co-authored-by: Nora <72460825+noraleonte@users.noreply.github.com> Co-authored-by: Flavien DELANGLE <flaviendelangle@gmail.com> Signed-off-by: José Rodolfo Freitas <joserodolfo.freitas@gmail.com>
Co-authored-by: Marija Najdova <mnajdova@gmail.com> Signed-off-by: José Rodolfo Freitas <joserodolfo.freitas@gmail.com>
8f3985c to
a2ab131
Compare

Previews