[docs-infra] Scoped notification per product about material-ui

[danilo-leal]

Can I take a step back and raise whether this notification system within the docs is even a good pattern to support?

Most of our direct and indirect competitors don't have it (not a reason to drop it per se; just a quick benchmark), and I’m just unsure if users get value from an additional notification system that can just clutter stuff more as well as bother them (yet another red dot). If the notifications were scoped, that'd help, for sure. Still, if there's really a relevant thing to share, like, for example, MUI X's v7 release blog post, I'm sure it'd be way more impactful to use the banner approach rather than burying it in a notification. The banner could also be scoped (or not, we can deliberate). As the banner is just one, it'd be a great way to force us to figure out the most important thing to share at any given time (like the survey vs. a major product release).

[oliviertassinari]

this notification system within the docs is even a good pattern to support?

@danilo-leal It's common to find a banner system:

• https://developer.hashicorp.com/terraform/cli

• https://tailwindcss.com/docs/installation

• https://nuxt.com/docs/getting-started/assets

For a notifications system, I'm only aware of:

• https://vuetifyjs.com/en/getting-started/installation/

We used to have a banner like system (2018 with a snackbar), then moved to a notification system. I don't know, I don't see really an issue as long as the content is relevant. The use case we have in mind for Toolpad (creating awareness of RFCs) makes using banners impractical.

[danilo-leal]

Yup, the banner is way more common. I think one of my main motivators here is just reducing the amount of extra noise our documentation design has. Whenever we need to communicate about something important that will remove users from the docs (to a blog post or whatever), we should likely have one approach only.