First and foremost I need to say: The skin documentation on mediawiki.org is, similar to the skin architecture itself, an *ahem* inferior collection. Why do I feel I need to state this? Because satisfying to me documentation looks differently and I won't expand the scope to make it good, I will solely focus on the skin variables pieces!

The additional info added to Vue.js guidelines on mediawiki.org is helpful! Do you think it's worth mentioning in "style limitations" section that when using design tokens and mixins, the design tokens must be imported before the mixins.

This snippet is from our code examples on Codex component demo pages:

// Note: you must import the design tokens before importing the css-icon mixin
@import (reference) "@wikimedia/codex-design-tokens/theme-wikimedia-ui.less";
@import (reference) "@wikimedia/codex/mixins/css-icon.less";

And the section "Write Vue3-compatible code" can be updated to share the history and current status of the Vue 2 to Vue 3 migration

In T349359#9469262, @lwatson wrote:

The additional info added to Vue.js guidelines on mediawiki.org is helpful! Do you think it's worth mentioning in "style limitations" section that when using design tokens and mixins, the design tokens must be imported before the mixins.

This snippet is from our code examples on Codex component demo pages:

// Note: you must import the design tokens before importing the css-icon mixin
@import (reference) "@wikimedia/codex-design-tokens/theme-wikimedia-ui.less";
@import (reference) "@wikimedia/codex/mixins/css-icon.less";

This is not an issue when using Codex in MediaWiki, because importing mediawiki.skin.variables.less imports both the tokens and the mixins (and internally ensures they're imported in the right order). The documentation kind of says this:

To access Codex design tokens and mixins inside Vue files, import MediaWiki skin variables @import 'mediawiki.skin.variables.less'; at the beginning of your style section.

but that doesn't totally make clear that the warning from the Codex docs doesn't apply in MW.

And the section "Write Vue3-compatible code" can be updated to share the history and current status of the Vue 2 to Vue 3 migration

I agree, I think we should probably remove that entire section at this point.

Was this actually in progress this sprint? Moving it back to Up Next to review what else is needed here.