Here is a technical question that came up while thinking about how we should handle a "Link" component (T313507):

Should Codex include a stylesheet for these global visual rules (typographic styles, grid system, breakpoints, etc) that could be used independently of the Vue components?

I personally would defer from this approach and rather offer Codex tokens (via the Codex library in MediaWiki for example) being able to be consumed independently from technical framework.
A stylesheet makes already a number of assumptions, like selectors used, that would be more problematic to implement, to maintain and hinders adoption.

Codex tokens have a number of advantages:

• They can be applied anywhere including non-stylesheet based environments like apps, or more easily in different stylesheet flavors (CSS, pre-processors)
• They are simpler centrally maintainable
• In pre-processors, they're only output when used, which is a huge performance advantage

In T314086#8120027, @Volker_E wrote:

I personally would defer from this approach and rather offer Codex tokens (via the Codex library in MediaWiki for example) being able to be consumed independently from technical framework.
A stylesheet makes already a number of assumptions, like selectors used, that would be more problematic to implement, to maintain and hinders adoption.

My concern is that there may be cases where multiple tokens need to be used together to achieve the correct visual style – for example links need multiple colors for all the various states, etc. If end-users must track down all the correct tokens one-by-one to create the correct style on their end, it creates opportunities for inconsistencies to creep in.

Maybe distributing LESS mixins (something @Catrope had suggested originally) would be a good solution here – then we can still avoid making assumptions in terms of selector rules, but we can package a group of tokens together to make things easier on the consumer. Need a button? Just drop in the "button" mixin. Same goes for basic text styles, links, and (eventually) responsive layout rules.

I'd be interested to get @bmartinezcalvo and @Sarai-WMDE response on “Users can find a publicly available list of "global" styles supported by the design system”
From my point of view this is aimed to be (and already for all available groups) covered by tokens demo.

In T314086#8120773, @Volker_E wrote:

I'd be interested to get @bmartinezcalvo and @Sarai-WMDE response on “Users can find a publicly available list of "global" styles supported by the design system”
From my point of view this is aimed to be (and already for all available groups) covered by tokens demo.

I agree that's covered by the demo, yes. Also since the second point refers to Figma. I assume that the checkbox is there to reflect completion of said critical global styles if marked.

In T314086#8120773, @Volker_E wrote:

I'd be interested to get @bmartinezcalvo and @Sarai-WMDE response on “Users can find a publicly available list of "global" styles supported by the design system”
From my point of view this is aimed to be (and already for all available groups) covered by tokens demo.

In T314086#8140935, @Sarai-WMDE wrote:

I agree that's covered by the demo, yes. Also since the second point refers to Figma. I assume that the checkbox is there to reflect completion of said critical global styles if marked.

Updated task description to specify that our global styles will be available in both the code demo and the design specs.