Change Details

Now that Codex has changed to use `rem` units for typography and relative sizing/spacing tokens, the "legacy" build that we have produced thus far has become redundant. It is now identical with the non-legacy build We may need to make some additional changes to the way that we handle tokens or styles relating to font-size based on the outcome of T358038. But regardless of what we decide to do there, we should no longer need to maintain a separate, slightly-different build of the Codex tokens and styles. However, we are in the process of introducing several new build artifacts relating to night mode support (the "experimental" build, mode-specific CSS variable overrides, etc). In the interest of simplicity we should remove the legacy artifacts as well as all code needed to generate these files. Otherwise, we risk dealing with a combinatorial explosion of different modes/themes/component-specific styles and it's going to put a drag on development work. ==== Acceptance Criteria - [ ] Update the tokens build script to remove the "legacy" build (currently treated as a platform) - [ ] Remove all references to these files in other parts of Codex (component files, `package.json`, etc) - [ ] Remove all references to the legacy files in MediaWiki itself (skins, CodexModule.php, etc).

Now that Codex has changed to use `rem` units for typography and relative sizing/spacing tokens, the "legacy" build that we have produced thus far has become redundant. It is now identical with the non-legacy build We may need to make some additional changes to the way that we handle tokens or styles relating to font-size based on the outcome of T358038. But regardless of what we decide to do there, we should no longer need to maintain a separate, slightly-different build of the Codex tokens and styles. However, we are in the process of introducing several new build artifacts relating to night mode support (the "experimental" build, mode-specific CSS variable overrides, etc). In the interest of simplicity we should remove the legacy artifacts as well as all code needed to generate these files. Otherwise, we risk dealing with a combinatorial explosion of different modes/themes/component-specific styles and it's going to put a drag on development work. ==== Acceptance Criteria - [x] Update the tokens build script to remove the "legacy" build (currently treated as a platform) - [x] Remove all references to these files in other parts of Codex (component files, `package.json`, etc) - [ ] Remove all references to the legacy files in MediaWiki itself (skins, CodexModule.php, etc).

Now that Codex has changed to use `rem` units for typography and relative sizing/spacing tokens, the "legacy" build that we have produced thus far has become redundant. It is now identical with the non-legacy build We may need to make some additional changes to the way that we handle tokens or styles relating to font-size based on the outcome of T358038. But regardless of what we decide to do there, we should no longer need to maintain a separate, slightly-different build of the Codex tokens and styles. However, we are in the process of introducing several new build artifacts relating to night mode support (the "experimental" build, mode-specific CSS variable overrides, etc). In the interest of simplicity we should remove the legacy artifacts as well as all code needed to generate these files. Otherwise, we risk dealing with a combinatorial explosion of different modes/themes/component-specific styles and it's going to put a drag on development work. ==== Acceptance Criteria - [ - [x] Update the tokens build script to remove the "legacy" build (currently treated as a platform) - [ - [x] Remove all references to these files in other parts of Codex (component files, `package.json`, etc) - [ ] Remove all references to the legacy files in MediaWiki itself (skins, CodexModule.php, etc).