I've added a handful of potential components to the "Components to include" section. Some could be very low priority or not useful to us at all, but attempting to make the list comprehensive.

I propose adding the following too:

• Spacing and layouting : Towards a grid system where all components have consistant layouting and spacing.
• Script support: The idea of scripts having stacked conjuncts, need for vertical space considerations, script directionality.
• Responsive design: All the components and their behavior in various screensizes

This is a good list. An additional items could be the Language selector/picker. Some ideas for improving and standardizing the component in this document.

Probably low priority, but would like to propose:

• Panels / Fieldsets
• Dialog - Hover cards / Page previews
• Success / Warning / Error / Info notices

The list looks good. Proposing a couple of low priority items.

• Footer
• Overflow menu

+1 to this list, particularly the components that are editor-focused.

• For Visual Editor : mobile and desktop specs for edit cards, toolbars, loading, transitions,

I'd also be keen to see a relational diagram of how to use the different navigations - I know that @alexhollender and I both have versions of something that looks like:

In T260239#6477685, @Prtksxna wrote:

• Success / Warning / Error / Info notices

Would you expand on that under light of https://design.wikimedia.org/style-guide/components/messages.html

In T260239#6479677, @iamjessklein wrote:

I'd also be keen to see a relational diagram of how to use the different navigations - I know that @alexhollender and I both have versions of something that looks like:

Relational diagram seems to be better off in a separate task and, from a current planning perspective probably more leaning into yet to be defined “Patterns” section. Happy if you like to drive that @iamjessklein…

In T260239#6483578, @Volker_E wrote:

In T260239#6477685, @Prtksxna wrote:

• Success / Warning / Error / Info notices

Would you expand on that under light of https://design.wikimedia.org/style-guide/components/messages.html

Sorry, forgot about that. Nothing to expand :)

In the last Design Style Guide meeting we've (designers of Wikimedia Design team and one of Wikimedia Deutschland) have prioritized components by importance and current product team needs with every designer having votes.
The 5 highest rated components were:

• Overlays/Modals
• Progress indicators
• Language selector
• Lists advanced and
• Dialogs

We've also had meta topic Spacing and grid top-voted, but I've raised concern that this might be far out given our complex in-production mix and non-connected rules. We've then agreed to break it down and consider starting with smaller steps like our base size spacing variables.

We need to limit the number of components to achieve our set goal for this quarter given the designer's prioritized team specific goals and the current situation.