Change Details

== Background Currently, in Codex, the less type mixins for sans-serif font families is set to `@font-family-base`, which references a `sans-serif` font stack. This matches what is used in Vector, even though in Vector the token referenced is `@font-family-sans--fallback`. The Codex docs site uses `@font-family-system-sans`. The `system-sans` font stack is the most optimized for readability across all platforms and operating systems. Ideally, everywhere would use that font stack. === Questions # Should the font stack referenced in Codex, OOUI, Vector, and Minerva be consistent? === Acceptance criteria [] Determine what font stacks and therefore font family tokens should be used in the various places [] Make any necessary updates

== Background In Codex, where font-family tokens intended to be used in MediaWiki are defined, there are 3 sans-serif option tokens defined: - `sans-10` which includes a comment for it to be used as a fallback. - `sans-50` which is deprecated. - `sans-100` which includes a font stack that is tailored to provide better operating system-specific readability. `sans-100` is the font stack that is intended to be used. It is optimized to work best for various systems. However, at the application token level, `font-family-base` is set to `sans-10` and not `sans-100`, whereas `font-family-serif`, the intended serif font stack to be used is set to `serif-100`, the serif equivalent to `sans-100`, optimized for various systems. Codex primarily sets font-family to `inherit`. === Acceptance criteria [] Remove whatever [[ https://phabricator.wikimedia.org/T247166#9315066 | barriers ]] we have to using the stack from `@font-family-system-sans` [] Update `@font-family-base` to point to `@font-family-system-sans` [] Have Codex docs and Vector use `@font-family-base` [] Update the Codex typography mixins which reference a sans-serif typeface to use `inherit` instead, following the rest of how Codex components set a font-family. [] Remove the custom `@font-family-base` token in Minerva as it is no longer needed. [] `@font-family-sans--fallback`  is there as a fallback option if anyone really wants to use just sans-serif for something [] Add comments to each of these tokens explaining their use case to guide people

== Background Currently, in Codex, the less type mixins for sans-serif font families is set to `@font-family-base`, which references a `sans-serif` font stack. This matches what is used in Vector, even though in Vector the token referenced is `@font-family-sans--fallback`.In Codex, The Codex docs sitwhere font-family tokens intended to be uses `@font-family-system-sans`.d in MediaWiki are defined, The `system-sans` font stack is the mostthere are 3 sans-serif optimized for readability across all platforms and operating systems. Ideally,ion tokens defined: everywhere would use tha- `sans-10` which includes a comment font stack. === Questionsr it to be used as a fallback. # Should the font stack referenced in Codex- `sans-50` which is deprecated. - `sans-100` which includes a font stack that is tailored to provide better operating system-specific readability. `sans-100` is the font stack that is intended to be used. It is optimized to work best for various systems. However, at the application token level, `font-family-base` is set to `sans-10` and not `sans-100`, whereas `font-family-serif`, OOUIthe intended serif font stack to be used is set to `serif-100`, Vectorthe serif equivalent to `sans-100`, and Minerva be consistent?optimized for various systems. Codex primarily sets font-family to `inherit`. === Acceptance criteria [] Determine what font stacks and therefore font family tokens should be used in the various placesRemove whatever [[ https://phabricator.wikimedia.org/T247166#9315066 | barriers ]] we have to using the stack from `@font-family-system-sans` [] Update `@font-family-base` to point to `@font-family-system-sans` [] Have Codex docs and Vector use `@font-family-base` [] Update the Codex typography mixins which reference a sans-serif typeface to use `inherit` instead, following the rest of how Codex components set a font-family. [] Remove the custom `@font-family-base` token in Minerva as it is no longer needed. [] `@font-family-sans--fallback`  is there as a fallback option if anyone really wants to use just sans-serif for something [] Make any necessary updatesAdd comments to each of these tokens explaining their use case to guide people