[blog] Blog post with MUI X v7.0.0 annoucement #41563
Conversation
joserodolfofreitas
requested review from
flaviendelangle,
cherniavskii and
alexfauquette
docs/pages/blog/mui-x-v7.md
Outdated
| On its first announcement, we showcased some of these improvements, but during the beta phase, we have further polished the scrolling performance for an even more significantly improved user experience. | ||
|
|
||
| <video preload="metadata" autoplay muted loop playsinline width="690" height="417" controls> | ||
| <source src="/static/blog/mui-x-v7/sticky-headers.mp4" type="video/mp4"> |
There was a problem hiding this comment.
The only thing I see (and it might be nitpicking) is that it might be better to have 2 videos, one for before and one for after instead of one that alters between the 2 states. My argument is that it's simpler to grasp and see the difference more clearly.
There was a problem hiding this comment.
I experimented with that in different constellations (now that we also have a before/after vertical scrolling), but the page got too noisy with two unsynced but related videos running at the same time, so I left a single video because I believe the page feels much cleaner with it.
Co-authored-by: Alexandre Fauquette <[email protected]> Co-authored-by: Flavien DELANGLE <[email protected]> Signed-off-by: José Rodolfo Freitas <[email protected]>
Co-authored-by: Andrew Cherniavskii <[email protected]> Signed-off-by: José Rodolfo Freitas <[email protected]>
|
|
||
| We're introducing a new API to customize Tree items through a hook called `useTreeItem2`. | ||
| It can be used with both `SimpleTreeView` and `RichTreeView`, and enables developers to fully leverage the TreeItem's subcomponents along with their default behaviors. | ||
| This approach ensures customization and flexibility are at the forefront without sacrificing the component's inherent features. |
There was a problem hiding this comment.
I would start from the pain people have with the current approach: people have to copy-paste a lot of the Tree Item's logic to do customization, stuff like expansion and selection events. This will be more and more painful in the future as we add new features.
| <RichTreeView items={myDataSet} slots={{ item: CustomTreeItem }} /> | ||
| ``` | ||
|
|
||
| You can check all the details of the given example on the [RichTreeView customization page](https://mui.com/x/react-tree-view/rich-tree-view/customization/#headless-api). |
There was a problem hiding this comment.
Clearly a nitpick but I would add both the SimpleTreeView and RichTreeView doc page here to make extra clear that we are supporting SimpleTreeView (even though you said it above)
There was a problem hiding this comment.
Looking great! Left a few remarks here & there. Let me know if you want help with the imagery; happy to do it. Also tagging @samuelsycamore for a more thorough writing review — I have a feeling we're using "we", "our", too much. Maybe we can be more centered around "what you are getting with this".
Co-authored-by: Danilo Leal <[email protected]> Co-authored-by: Flavien DELANGLE <[email protected]> Signed-off-by: José Rodolfo Freitas <[email protected]>
Co-authored-by: Andrew Cherniavskii <[email protected]> Signed-off-by: José Rodolfo Freitas <[email protected]>
Co-authored-by: Andrew Cherniavskii <[email protected]> Signed-off-by: José Rodolfo Freitas <[email protected]>
Summary
Blog post highlighting all the new developments delivered with v.7.0.0.
:::info
I chose to repeat (and update) the features announced in the beta blog post so that everything significantly relevant about the release is on a single page.
:::
Preview
https://deploy-preview-41563--material-ui.netlify.app/blog/mui-x-v7/