Change Details

## Background - **Description:** Create a CSS/LESS only implementation of Codex components (maybe just a subset of them) - **History:** This is an approach that has been followed by many other design systems; it will help Codex to cover use-cases where using Vue (or JS at all) would not be appropriate - **Known use case(s):** Allow teams who have performance or security constraints to achieve visual consistency with the design system without using JS/Vue - **Considerations:** Can we avoid duplication by having the CSS "components" share styles with the Vue components? Would it make sense to publish a `codex-styles` package that contains LESS mixing, which then gets used in the Codex Vue components? ### User stories - As a developer of a feature that cannot use JS for performance or security reasons, I'd like my UI to have visual consistency with the wider design system. I'd also like to be able to simply re-use pre-defined styles that look and behave correctly instead of having to write them myself. ### Previous implementations These artifacts are listed for historical context. The figma spec, linked below, is the source of truth for the new component. - **OOUI:** The OOUI PHP work is relevant here

## Background - **Description:** Create a CSS/LESS only implementation of Codex components (maybe just a subset of them) - **History:** This is an approach that has been followed by many other design systems; it will help Codex to cover use-cases where using Vue (or JS at all) would not be appropriate - **Known use case(s):** Allow teams who have performance or security constraints to achieve visual consistency with the design system without using JS/Vue - **Considerations:** Can we avoid duplication by having the CSS "components" share styles with the Vue components? Would it make sense to publish a `codex-styles` package that contains LESS mixing, which then gets used in the Codex Vue components? ### User stories - As a developer of a feature that cannot use JS for performance or security reasons, I'd like my UI to have visual consistency with the wider design system. I'd also like to be able to simply re-use pre-defined styles that look and behave correctly instead of having to write them myself. ### Previous implementations - **OOUI:** The OOUI PHP work is relevant here

## Background - **Description:** Create a CSS/LESS only implementation of Codex components (maybe just a subset of them) - **History:** This is an approach that has been followed by many other design systems; it will help Codex to cover use-cases where using Vue (or JS at all) would not be appropriate - **Known use case(s):** Allow teams who have performance or security constraints to achieve visual consistency with the design system without using JS/Vue - **Considerations:** Can we avoid duplication by having the CSS "components" share styles with the Vue components? Would it make sense to publish a `codex-styles` package that contains LESS mixing, which then gets used in the Codex Vue components? ### User stories - As a developer of a feature that cannot use JS for performance or security reasons, I'd like my UI to have visual consistency with the wider design system. I'd also like to be able to simply re-use pre-defined styles that look and behave correctly instead of having to write them myself. ### Previous implementations These artifacts are listed for historical context. The figma spec, linked below, is the source of truth for the new component. - **OOUI:** The OOUI PHP work is relevant here