[docs] Improve Support page #11556
[docs] Improve Support page #11556
Conversation
|
Deploy preview: https://deploy-preview-11556--material-ui-x.netlify.app/ Updated pages: |
| ### GitHub | ||
|
|
||
| We use GitHub issues as a bug and feature request tracker. | ||
| If you think you've found a bug, or you have a new feature idea, please start by [making sure it hasn't already been reported or fixed](https://github.com/mui/mui-x/issues?utf8=%E2%9C%93&q=is%3Aopen+is%3Aclosed). |
There was a problem hiding this comment.
Remove all of that, I don't see the value of it, it looks best to link to the docs, to have 1. no duplication 2. something always up to date, even on older npm packages releases.
|
|
||
| ## Community | ||
|
|
||
| We have a [Discord Server](https://mui.com/r/discord/) to allow the MUI X community to gather. | ||
| Our tools are used by thousands of developers and teams all around the world, many of whom actively engage with the community. | ||
|
|
||
| You can join Discord to engage in lively discussions, share your projects, and interact with developers just like you from all around the world. We'd love for you to be a part of our community! |
There was a problem hiding this comment.
It feels like we can still link to Discord, but further buried and with a clear purpose statement.
| ### Long-term support (LTS) | ||
| ## Long-term support (LTS) |
There was a problem hiding this comment.
Looks like a mistake
| Bug fixes, performance enhancements, and other improvements are delivered in new releases. However, MUI remains committed to providing security updates and addressing regressions for the immediate predecessor of the current major version. | ||
| Bug fixes, performance enhancements, and other improvements are delivered in new releases. However, we remain committed to providing security updates and addressing regressions for the immediate predecessor of the current major version. |
There was a problem hiding this comment.
I try to fade the company name (MUI) from the docs. My idea is that we probably don't want to have it referenced, to reach a point where it's almost not visible anywhere.
Go to https://react.dev/, you won't find the docs using "Meta", it uses "We" or "React team". Same observation on https://nextjs.org/. The value I see is that:
- Keep the audience focused on learning MUI X
- As MUI grows, it feels weird to reference an organization that is bigger than the project, as a reader of the docs, I would want to hear the team's voice directly.
cc @danilo-leal this would likely further help with the confusion. For example in https://mui.com/material-ui/getting-started/support/#github:
The immediate conclusion I make is that MUI is the name of the open-source project.
| When purchasing a MUI X Pro or Premium license you get access to technical support until the end of your subscription. | ||
| When purchasing a MUI X Pro or Premium license you get access to technical support until the end of your active license. |
There was a problem hiding this comment.
A change we are making with @rluzists1 we are taking steps to define this "active license" notion https://github.com/mui/mui-private/pull/332. Avoiding "subscription" as it has a bad-rep.
|
|
||
| [Post a question about MUI X](https://stackoverflow.com/questions/tagged/mui-x) on Stack Overflow using the "mui-x" tag. | ||
| If you can't find your answer, [ask a new question](https://stackoverflow.com/questions/ask?tags=reactjs%20mui-x) using the relevant tags. |
There was a problem hiding this comment.
I too often see developers opening questions with the wrong tag.
github-actions
bot
added
the
PR: out-of-date
|
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
Co-authored-by: Sam Sycamore <[email protected]> Signed-off-by: Olivier Tassinari <[email protected]>
oliviertassinari
force-pushed
the
stack-overflow-labels
branch
from
5cfe929 to
90d122e
Compare
github-actions
bot
removed
the
PR: out-of-date
oliviertassinari
force-pushed
the
stack-overflow-labels
branch
from
90d122e to
bcdc3da
Compare
Co-authored-by: Sam Sycamore <[email protected]> Signed-off-by: Olivier Tassinari <[email protected]>
oliviertassinari
force-pushed
the
stack-overflow-labels
branch
2 times, most recently
from
26549c1 to
1b68f56
Compare
oliviertassinari
force-pushed
the
stack-overflow-labels
branch
from
1b68f56 to
2c87975
Compare
Signed-off-by: Olivier Tassinari <[email protected]> Co-authored-by: Sam Sycamore <[email protected]>
Apply mui/mui-x#11556 in core as well.
Apply mui/mui-x#11556 in core as well.
Signed-off-by: Olivier Tassinari <[email protected]> Co-authored-by: Sam Sycamore <[email protected]>
Apply mui/mui-x#11556 in core as well.
My idea is to create a standard for the Support page, starting with MUI X.
To then go to the core and update Material UI support, create Base UI, MUI System support pages, etc. I'm not a fan of https://mui.com/material-ui/getting-started/support/.
Preview: https://deploy-preview-11556--material-ui-x.netlify.app/x/introduction/support/