Change Details

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)

We would like to release Codex as an "alpha", or 1.0 version, in partnership with a volunteer team that can help us collect and address feedback in a real use-case scenario. The alpha release will not come with a formal announcement or call-to-action for contributors because the goal of this release is to position Codex for success as much as possible before opening it up to the public. **Background:** The original release goal for Codex was WVUI deprecation and we are continuing to work towards this as a key milestone in T300081. The following requirements for Codex launch are project-agnostic. **Requirements:** - {T299136} - Decide on a pilot project (exploration phase) - Identify areas in the pilot design where Codex should be used and ensure general design system compliance - Complete component design and development for any new components - Test Codex installation and component implementation - Solicit feedback from pilot team (feedback cycle) - Perform final design review before release (feedback cycle) **Deploy Steps:** - Complete QA/regression testing - Deploy Codex to NPM (library deploy only, no integration) - Deploy Codex to MediaWiki (library deploy only, no integration) - Coordinate deploy schedule between teams - Integrate Codex with pilot project (following library deploy - could be ResourceLoader, NPM, or both) **Documentation:** Should be the last step, light and for internal use. Will revisit to finalize documentation after feedback is received and we're ready to launch the design system to the public. - Document design terminology for different types of components (base components, patterns, etc.) - Complete design Figma files - Write developer documentation for installation steps and new components

We would like to release Codex inas an "alpha" version with a volunteer pilot project that can help us collect and address feedback for a wider, more stableor 1.0 version, public-facing releasein partnership with a volunteer team that can help us collect and address feedback in a real use-case scenario. Our original goal for a "Codex 0.5" release was WVUI deprecation,The alpha release will not come with a formal announcement or call-to-action for contributors because the goal of this release is to position Codex for success as much as possible before opening it up to the public. **Background:** The original release goal for Codex 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, in T300081. but they are alsoThe following requirements for Codex launch are project-agnostic. **Requirements:** - Define design terminology for different types of components (base components, patterns, etc.)- {T299136} - Decide on a pilot project (exploration phase) - Identify areas in the pilot design where Codex should be used and ensure general design system compliance - Complete design Figma files (alpha version; nocomponent design and development for external contributions)any new components - Complete developer document- Test Codex installation ofand component behaviors (alpha version; not for external contributionsimplementation - Solicit feedback from pilot team (feedback cycle) - Formaliz- Perform final design review before release version for Codexe (feedback cycle) **Deploy Steps:** - Complete QA/regression testing - Deploy Codex to NPM (library deploy only, no integration) - Deploy Codex to MediaWiki (library deploy only, no integration) - QA/regression testing - Coordinate deploy schedulee between teams - Integrate Codex with pilot project (following library deploy - could be ResourceLoader, NPM, or both) **Documentation:** Should be the last step, light and for internal use. Will revisit to finalize documentation after feedback is received and we're ready to launch the design system to the public. - Document design terminology for different types of components (base components, patterns, etc.) - Complete design Figma files - Write developer documentation for installation steps and new components