Goal: Capture basic info about what other teams are thinking in terms of Vue and Codex so we can plan ahead and shift priorities to ensure these teams can adopt Codex.
Questions:
- How familiar are you and your team with Vue.js? What about Codex? (If needed, give a brief overview of Codex)
- Have you built anything with Vue/Codex? If so, what?
- Have you thought about building a new project with Vue/Codex, or migrating an old one? If so, what project(s), and when?
- What is blocking you from adopting Codex? (For teams already using it, we could get more info about what's difficult or blocking them from using it in more places) Some common things might be:
- Need Vue training
- Need SSR (or CSS-only components)
- Need more components or design tokens
- Want to, but can’t find the time
- Worried about performance, security, browser compatibility, etc
App specific
- Use of Codex design tokens a possible path forward? T327200
Acceptance criteria:
- Responses are logged in this google doc (viewable by DST)
Checklist:
- Abstract Wikipedia - @Catrope
- Anti-Harassment Tools - @ldelench_wmf
- Campaigns - @ldelench_wmf
- Community Tech - @ldelench_wmf
- Editing - @Catrope
- Growth - @AnneT
- Fundraising Tech - @Catrope
- Inuka - @egardner
- Language - @Catrope
- Moderator Tools - @egardner
- Structured Data - @egardner
- Trust and Safety Tools - @AnneT
- Web - @AnneT
- Wikidata (WMDE) - @AnneT
- Technical Wishes (WMDE) - @AnneT
- API platform - @AnneT
- Data Engineering - @egardner
- Technical Engagement (toolhub) - @Catrope
- Android – @Volker_E
- iOS – @Volker_E