Change Details

The initial goal for 0.5 release was WVUI deprecation and we will continue working towards this as a key milestone. However, we are also exploring opportunities for a release that is smaller in scope and could help us make iterative improvements to the product in a lower-risk environment, so another pilot may release first. Ideally, the 0.5 release of Codex will be an "alpha" version that lives within a single project, likely on MediaWiki. The first release should help us collect and address feedback in order to position Codex for a wider, stable 1.0 release. **Requirements:** [ ] {T299136} [ ] {T295185} [ ] Decide on pilot use-case(s) for 0.5 launch of Codex (in progress) [ ] Design tokens and theming requirements (needs discussion)

We would like to release Codex in an "alpha" version with a volunteer pilot project that can help us collect and address feedback for a wider, more stable, public-facing release. Our original goal for a "Codex 0.5" release was WVUI deprecation, and we are continuing to work towards this as a key milestone. The following requirements should also be applied to the WVUI work, but they are also project-agnostic. **Requirements:** - Define design terminology for different types of components (base components, patterns, etc.) - Complete design Figma files (alpha version; not for external contributions) - Complete developer documentation of component behaviors (alpha version; not for external contributions) - Formalize release version for Codex - Deploy Codex to NPM (library deploy only, no integration) - Deploy Codex to MediaWiki (library deploy only, no integration) - QA/regression testing - Coordinate deploy schedule - Integrate Codex with pilot project (following library deploy - could be ResourceLoader, NPM, or both)

The initial goal for 0.5 release was WVUI deprecation and we will continue working towards this as a key milestone.We would like to release Codex in an "alpha" version with a volunteer pilot project that can help us collect and address feedback for a wider, Howevermore stable, we are also exploring opportunities for a release that is smaller in scope and could help us make iterative improvements to the product in a lower-risk environment,public-facing release. so another pilot mayOur original goal for a "Codex 0.5" release first. Ideallywas WVUI deprecation, the 0.5 release of Codex will be an "alpha" version that lives within a single project,and we are continuing to work towards this as a key milestone. likely on MediaWiki.The following requirements should also be applied to the WVUI work, The first release should help us collect and address feedback in order to position Codex for a wider,but they are also project-agnostic. stable 1.0 release. **Requirements:** [ ] {T299136} - Define design terminology for different types of components (base components, patterns, etc.) [ ] {T295185} - Complete design Figma files (alpha version; not for external contributions) [ ] Decide on pilot use-case(s) for 0.5 launch of Codex (in progress - Complete developer documentation of component behaviors (alpha version; not for external contributions) [ ] Design tokens and theming requirements (needs discussion - Formalize release version for Codex - Deploy Codex to NPM (library deploy only, no integration) - Deploy Codex to MediaWiki (library deploy only, no integration) - QA/regression testing - Coordinate deploy schedule - Integrate Codex with pilot project (following library deploy - could be ResourceLoader, NPM, or both)