In order to position Codex for success on a wider scale, it would be useful to release it as an "alpha" version and test it against a low-risk use case in production. Doing this will create space for a valuable prototype phase where we can collect insights and respond to an initial round of user feedback before opening Codex to the public. Because the goal is to go through a feedback loop first, an alpha release would not come with a formal call-to-action for contributors outside of the the Design Systems Team and the partnering launch team.
**Background:**
The original "alpha" project for Codex was WVUI deprecation and we are continuing to work towards this milestone inAs we work towards our original Codex launch milestone (WVUI deprecation, T300081.), If a smaller-scale alphwe are also seeking opportunities to test Codex as a project should launch in advance,ototype in a low-risk production environment. it will have the goal of improving outcomes for WVUI deprecationThis "alpha" release would allow us to collect and respond to user feedback and position Codex for success before a wider release. Selection of a project will involve weighing factors such as the impact on timelines and the overall risk involved in launch.It would not come with a formal call-to-action for contributors outside of the the Design Systems Team and the partnering test team.
**Requirements:**
The requirementschecklist below are project-agnostic and apply to whichever projecties to any Codex is launched withh.
- {T299136}
- Decide on a pilot project (exploration phase to wrap mid Feb 2022)
- Formalize the process for Codex work intake, assignments, and feedback between design/engineering/x-team (product task)
- I- For new projects, identify areas in the pilotproduct design where Codex should be used and ensure general design system compliancee is needed
- Complete component design and development for any new components
- Test Codex installation and component implementation
- Solicit feedback from pilotpartner 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 -use, not public yet.
- Prepare onboarding resources for collaborating teams, including structure for feedback loops (product task)
- Document design terminology for different types of components (base components, patterns, etc.)
- Make sure design Figma files match Codex documentation site