Add Baseline status for classes #2328
Description
Hello!
Developers are starting to pick up Baseline as a way of understanding feature availability in HTML, CSS and JS. We're starting to see popular frameworks like Vite and Angular adopting Baseline Widely available as their default build target, and popular docs sites like MDN and caniuse.com include Baseline status on features to make it easier for devs to know if something is interoperable and if it's been around long enough that it should be fairly safe to use.
Tailwind's docs pages don't currently have any indicator for how widely supported a particular class is or really any way for developers to know whether it will work well for their userbase. It would be great for class tables to have a column for Baseline status (Widely available, Newly available or Limited availability) and the year that it became Newly available. Optionally, you could display a popover or expanded row of information, indicating which minimum browser versions support the feature.
It should be fairly easy to get the data for this using web-features and/or compute-baseline, if you're able to map your class definitions to MDN compat keys. I'm happy to help work out what that should look like.
This wouldn't prevent Tailwind from adopting newer CSS features, but it would make it easier for developers to tell at a glance whether they need to be cautious about using a specific feature because it might only be fairly recently launched in one or more browsers.
CC @sdavids who has also advocated for Tailwind versions to indicate which Baseline feature set they fit into. I'll create a separate issue for that as I think I could help do this programmatically so you can publish a table.
Thanks!