[blog] Add post about v5 Migration guide update#33063
[blog] Add post about v5 Migration guide update#33063mnajdova merged 17 commits intomui:masterfrom mapache-salvaje:migration-update-post
Conversation
mapache-salvaje
added
v5.x migration
blog
|
@samuelsycamore would be great if we can also merge #33005 before the blogpost :) |
|
Also on the tweet we could mention:
|
mnajdova
left a comment
mnajdova
left a comment
There was a problem hiding this comment.
Looks great, left one suggestion, feel free to disregard if you don't think it's worth mentioning :)
danilo-leal
left a comment
danilo-leal
left a comment
There was a problem hiding this comment.
Content-wise it's great! Short and simple!
My only consideration is: I wonder if we shouldn't add a couple of examples for the new styling engine (what's the difference from a code perspective); global class names (how does that look like); and IntelliSense (maybe a gif of VS Code with it working?).
Additionally, I added the OG image card but I'm not sure if it'll work given the image is not used within the .md file... @siriwatknp would you know about that?
@danilo-leal The path looks good except for the image extension. It should be |
All great ideas, thanks @danilo-leal! I always struggle to come up with ways to add visual appeal to articles like this! I'll incorporate these suggestions into the next draft. |
Co-authored-by: Siriwat K <siriwatkunaporn@gmail.com>
danilo-leal
left a comment
danilo-leal
left a comment
There was a problem hiding this comment.
Looking awesome, excellent work!
Added an additional image there just so the post is a bit more eye-catching and also edited a bit the IntelliSense one 👌
siriwatknp
left a comment
siriwatknp
left a comment
There was a problem hiding this comment.
👍 Updated the thumbnail to .png to show on social preview.
oliviertassinari
left a comment
oliviertassinari
left a comment
There was a problem hiding this comment.
Great idea!
I have seen some people looking for moving to v5 because of the new components/features in MUI X. I wonder if it's something that can resonate.
| Emotion unlocks many new customization options that developers had been requesting for years, such as custom style utility props, color variants, and custom theme variants. | ||
| Check out [this RFC on GitHub](https://github.com/mui/material-ui/issues/22342) for details about this change. | ||
|
|
||
|  |
There was a problem hiding this comment.
I have tried to click on this image 😁
Co-authored-by: Olivier Tassinari <olivier.tassinari@gmail.com>
Co-authored-by: Olivier Tassinari <olivier.tassinari@gmail.com>
Co-authored-by: Olivier Tassinari <olivier.tassinari@gmail.com>
Co-authored-by: Olivier Tassinari <olivier.tassinari@gmail.com>
Co-authored-by: Olivier Tassinari <olivier.tassinari@gmail.com>
This reverts commit 43350da
6 participants
Preview: https://deploy-preview-33063--material-ui.netlify.app/blog/migration-update/
This PR adds a post to the blog to inform users that we've updated the Migration guide.
Since this wasn't substantial enough to flesh out into a whole article, I've framed it in terms of "top reasons why you should migrate to v5" as a way to provide the reader with more value and ideally strengthen the call to action (to check out the new migration guide).