[docs][base] Add pages for coming soon components

[danilo-leal]

• I have followed (at least) the PR section of the contributing guide.

This PR is adding pages for coming soon Base UI components ⎯ the ones starred in the umbrella issue: Checkbox, Radio, and Accordion. These are the ones that might come super close after the stable release.

Preview: https://deploy-preview-37575--material-ui.netlify.app/base-ui/react-checkbox/ related to mui/base-ui#10

[mui-bot]

Netlify deploy preview

• docs/data/base/components/accordion/accordion.md
• docs/data/base/components/checkbox/checkbox.md
• docs/data/base/components/radio-button/radio-button.md

Bundle size report

No bundle size changes

Generated by 🚫 dangerJS against 744312e

[michaldudak]

I have just one remark. Besides that (and the info message improvement), I think it's good to go!

[danilo-leal]

@michaldudak & @brijeshb42 mind giving this one a second look, please? 🙌

[michaldudak]

Looks fine to me now!

[brijeshb42]

LGTM

[oliviertassinari]

Great to see these pages!

Regarding how we could improve them:

• I think that it would be much better if we had one GitHub issue for each unstyled component that is left to be built. This would allow:

  • To collect more refined upvotes and linked issues on each case, knowing which component to build first.
  • Allow the developers to subscribe to only the components that haven't been built yet, getting notified when we close them.
  • Collaborate with the community on the right API & solution for each.
  • We could also work with the developers from the community to build some of them as they did in the past. They have built most of the components in Material UI (in their first version). Typically, we could instruct them to extract Material UI logic and adopt Base UI patterns, the sooner we get them in an unstable state, the better. So: we can build Material UI v6 on it, so we can differentiate with other headless libraries.

• I think that we miss more pages:

  • Tooltip
  • Pagination
  • Rating

[danilo-leal]

@oliviertassinari for the first part of your message, maybe a better place to drop this feedback would be on the all-encompassing unstyled components progress issue (mui/base-ui#10)? I agree with it, though!

As for the other part, I can add pages for them, no problem!

[oliviertassinari]

for the first part of your message, maybe a better place to drop this feedback would be on the all-encompassing unstyled components progress issue (#27170)? I agree with it, though!

@danilo-leal mui/base-ui#10 is the umbrella issue, it's definitely connected 👍.

@michaldudak What do you think about we create one GitHub issue for each unstyled components left to build? As far as I know each takes a lot of work, so we wouldn't have overkill small GitHub issues 😁.

[michaldudak]

What do you think about we create one GitHub issue for each unstyled components left to build?

Yup, it makes sense. We can discuss the API design and implementation details in these issues. I'll create them.

[michaldudak]

Here's the whole list: https://github.com/mui/material-ui/issues?q=is%3Aopen+is%3Aissue+label%3A%22package%3A+base-ui%22+label%3A%22new+feature%22+hook+in%3Atitle

[oliviertassinari]

@michaldudak Awesome, this is inline with https://ark-ui.canny.io/feature-requests/p/date-picker-react or ariakit/ariakit#955.

Once Danilo comes back from holiday, we can get #38025 live.