Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[docs] Standardize getting started docs across all packages #16302

Open
wants to merge 53 commits into
base: master
Choose a base branch
from

Conversation

mapache-salvaje
Copy link
Contributor

@mapache-salvaje mapache-salvaje commented Jan 22, 2025

Follow-up to #15757, applying the same patterns from the Data Grid getting started docs to the other X components for a more consistent and predictable experience.

  • "Getting started" page becomes "Quickstart": how to install the package, render your first component, work with TypeScript, and how to use the documentation itself
    • These pages are almost identical now in terms of structure and copy across all 4 packages, with some notable differences in the "Rendering a {{X}} component" section since the implementations are quite varied
  • FAQ pages are eliminated in favor of more specific locations for their content

With this PR, all 4 packages now have 2 pages in the Getting Started sequence:

  • Overview
  • Quickstart

Considerations:

  • The Date Pickers have a really sleek Overview page that will eventually be replicated for the other 3 packages, so I'm not especially worried about the Tree View's Overview which is somewhat sparse at the moment
  • The Date Pickers also have a Base Concepts page that needs a thorough overhaul, and I'm not sure whether to remove the page and relocate its content, or create a similar page for the other packages, but it does feel like it should go one way or the other
  • The Data Grid has a third page in the sequence, Feature Showcase, which might be nice to replicate for the other packages if it would make sense to do so

Questions:

  • Base UI includes their Accessibility page in this sequence—should we do that here? I guess it's mostly about signaling this aspect as a high priority

Notes:

@mapache-salvaje mapache-salvaje added docs Improvements or additions to the documentation enhancement This is not a bug, nor a new feature labels Jan 22, 2025
@mapache-salvaje mapache-salvaje marked this pull request as ready for review January 29, 2025 16:36
Comment on lines +3 to +11
- https://mui.com/x/react-charts/getting-started/
- https://mui.com/x/react-data-grid/#premium-plan
- https://mui.com/x/react-data-grid/getting-started/
- https://mui.com/x/react-data-grid/getting-started/#feature-comparison
- https://mui.com/x/react-date-pickers/fields/#accessible-dom-structure
- https://mui.com/x/react-date-pickers/getting-started/
- https://mui.com/x/react-tree-view/#rich-tree-view
- https://mui.com/x/react-tree-view/#simple-tree-view
- https://mui.com/x/react-tree-view/getting-started/
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As I understand things, we should fix those

Suggested change
- https://mui.com/x/react-charts/getting-started/
- https://mui.com/x/react-data-grid/#premium-plan
- https://mui.com/x/react-data-grid/getting-started/
- https://mui.com/x/react-data-grid/getting-started/#feature-comparison
- https://mui.com/x/react-date-pickers/fields/#accessible-dom-structure
- https://mui.com/x/react-date-pickers/getting-started/
- https://mui.com/x/react-tree-view/#rich-tree-view
- https://mui.com/x/react-tree-view/#simple-tree-view
- https://mui.com/x/react-tree-view/getting-started/

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

They're all coming from the Material UI docs and MUI blog - PR to fix them here: mui/material-ui#45145

Copy link
Member

@oliviertassinari oliviertassinari Jan 29, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, thanks for the context. This seems related to mui/base-ui#552.

Copy link
Member

@LukasTy LukasTy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice improvement and alignment between products. 👍
I'm not 100% sure about FAQ removals, but if you really think that they don't make sense, I don't mind. 👌

docs/data/charts/quickstart/quickstart.md Outdated Show resolved Hide resolved
docs/data/date-pickers/date-picker/date-picker.md Outdated Show resolved Hide resolved
Comment on lines +35 to +36
{ pathname: '/x/react-data-grid/quickstart', title: 'Quickstart' },
{ pathname: '/x/react-data-grid/features', title: 'Features' },
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nitpick: Explicit title is not needed if it aligns with the path/slug. 😉

On that same note: have you considered only renaming the title, but keeping the existing pathnames?
We would avoid the URL changes, redirects, and maybe even some SEO implications... 🤷 🙈

Suggested change
{ pathname: '/x/react-data-grid/quickstart', title: 'Quickstart' },
{ pathname: '/x/react-data-grid/features', title: 'Features' },
{ pathname: '/x/react-data-grid/quickstart' },
{ pathname: '/x/react-data-grid/features' },

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah I was on the fence about changing the path names and originally planned to leave them alone. I just figured it would be more annoying for maintainers in the future if they're looking for a page called "Features" (for example) but all the related files are called "Demo."

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Gotcha. Well, if no one sees problems (SEO) with redirects, I'm all for this. 🙌

docs/data/date-pickers/quickstart/quickstart.md Outdated Show resolved Hide resolved
@github-actions github-actions bot added the PR: out-of-date The pull request has merge conflicts and can't be merged label Jan 30, 2025
Copy link

This pull request has conflicts, please resolve those before we can evaluate the pull request.

@github-actions github-actions bot removed the PR: out-of-date The pull request has merge conflicts and can't be merged label Jan 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Improvements or additions to the documentation enhancement This is not a bug, nor a new feature
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants