Design Systems page probably could use updates

[bkardell]

It's been kind of a while since this project was started and a lot has happened since then. Some of the links we have sort of no longer point to what is advertised. Auth0 Styleguide link, for example, doesn't. Microsoft's things here are currently particularly confusing (@chrisdholt will provide more). However, there have been plenty of additional developments since. Tabs research also considered some additional ones like shoelace, for example. If we can get a decent crack at a list here, I'm happy to send a PR or three.

Note - there is a tricky aspect to this with two sides to it: First, the components grid that was created initially is also kind of stuck in time in both respects. We could remove and add whole systems - but I think that is also not complete because there are abstract design systems and sometimes N concrete implementations, and they don't often agree. We say design systems but many implementations don't even refer to or share their design systems too. I think we really have to look at all of them because, for example, we show some things as not having accordions, but some of their actual implementations do.

[css-meeting-bot]

The Open UI Community Group just discussed Design Systems page probably could use updates, and agreed to the following:

• RESOLVED: there should be an annual review of design systems page.

The full IRC log of that discussion

<jarhar> bkardell: i dont know that we have addressed this, but the first components grid was created a long time ago, and design system we refer to shifts in time
<jarhar> bkardell: we have been around long enough that some have come around, others have come defunct. microsofts ones are confusing because there was ones that were supplanting each other
<jarhar> bkardell: i think it could use some help, there are links there to stardust ui and fabric
<Luke> q+
<jarhar> gregw: what is our goal for this issue? to your point its ever evolving, i just dont know what to do with this issue. do we want to update the charter that every 6 months we will clean? what is the...
<jarhar> masonf: +1 to the resolution that we should not let things linger until they are stale
<jarhar> bkardell: even annually, there should be some plan going forward
<jarhar> gregw: can we resolve on an annual review? i just want to go land these PRs, i appreciate them taking this time to open and fix them
<masonf> Proposed resolution: there should be an annual review of design systems page.
<jarhar> gregw: ill ping ??? and see if they have time to automate them
<jarhar> gregw: for github avatars, i throw a calendar in and say go update them
<jarhar> gregw: if we could automate that would be good
<gregwhitworth> I'll ping @andrico
<jarhar> bkardell: when you do a research, its nice if theres a list like heres a bunch of them. for tabs we did more than are in here, i dont know if thats ok or encouraged
<jarhar> gregw: i encourage if its not in the table dont assume it doesnt exist
<jarhar> gregw: that design table is a launching point and we should keep it up
<masonf> RESOLVED: there should be an annual review of design systems page.
<bkardell_> +1
<jarhar> gregw: there should be an annual review of the design systems page. i will open a calendar item on myself once these 3 land
<Luke> +1
<jarhar> gregw: i will also ping andrico and see if we can automate so it can be monthly
<bkardell_> I think there might be another one that "went private" and you can't get to their system anymore - tho that might have just been a tabs one
<bkardell_> +1
<bkardell_> +2 even
<bkardell_> I will be out the following week too probaly as I will be on holiday

[gregwhitworth]

I'll be setting up a meeting but it would also be great if there was a way in which to automate knowing the diff of the systems that need to be updated. cc: @andrico1234 just in case he has any ideas.

[github-actions]

There hasn't been any discussion on this issue for a while, so we're marking it as stale. If you choose to kick off the discussion again, we'll remove the 'stale' label.

[gregwhitworth]

This is a generic issue as noted in the attached issues but I'm going to close this one and have us tackle them one at a time on the other issues.