In order to position Codex for success on a wider scale, it would be useful to release it inas an "alpha" version and test it against a low-risk, use case in production. real use-case in productionDoing 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. Doing this will allow our teamBecause the goal is to collect and respond togo through a feedback before opening Codex up to a wider audience.loop first, 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. the 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 release goal"alpha" project for Codex was WVUI deprecation and we are continuing to work towards this key milestone in T300081. If a smaller-scale alpha project should launch in advance, The requirements in this task are project-agnostic and should be applied to any launch,it will have the goal of improving outcomes for WVUI deprecation. whether we starSelection of a project with an alpha release or go straight into WVUI deprecationll involve weighing factors such as impact timelines and the overall risk involved in launch.
**Requirements:**
The requirements below are project-agnostic and apply to whichever project Codex is launched with.
- {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)
- 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 - not public yet)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