Aspects to support:
- Common UI widgets - Buttons, Icons, Grid, ButtonGroup with i18n and following the mediawiki design guidelines.
- Common Content translation specific UI widgets - Translation work item with thumbnail, title, languages, description, Basic chrome of the page
- Language selection controls
- Unit testing each UI components - Jest
- Data store possibly using vuex
- Mediawiki api backend
- Dialog navigation
Along with developing these widgets, to demonstrate and prove that it fits the purpose, they will be used to construct the minimal CX dashboard optimized to mobile interface. This will have the chrome(Page header), translator's translations(to test api integration) and its listing(to test UI widgets)
This will also take the advantage of the proof of concept done as part of T242006
The latest version(master branch) will be always available at sx.wmflabs.org
Applying to one usecase
Once the general infrastructure is available, it will be applied to one usecase.
From product perspective the proposed step to start with would be "picking a section" (T241587) to maximize delivered value and minimize blockers. Support for this initial step allows to enable a basic version of the core process when connected with Content Translation's one-section mode (T234323). In this way, a basic experience that actually allows to translate a section can be demoed, tested, shared with early adopters, used for user research, and validate our analytics (i.e., how we visualize the initial "sectiontranslation" edits ). That is, making it useful while the team works on additional pieces that complete the experience, without having to wait for those to complete.