Design System Team/Design Systems Team Vue.js Migration
 | This page is obsolete. It is being retained for archival purposes. It may document extensions or features that are obsolete and/or no longer supported. Do not rely on the information here being up-to-date. |
Staying informed about the migration
[edit]- Email lists: wikitech-l@wikimedia.org, design@wikimedia.org and design-systems-team@wikimedia.org (internal only)
- Current tasks: Design System team kanban board
- Slack channels: #design, #front-end and #vue-developer-designer-summit-2021
*slack channels are generally for WMF staff only with exceptions for WMDE colleagues and contractors
Associated Events
[edit]Frequently Asked Questions
[edit]Should I be developing stuff in Vue.js now/before migrations happen?
Currently, probably not. Anything you do will be experimental, and will need to be migrated. But if you are interested in trying it out without a lot of institutional support, as an experiment, please give us a heads up; you can find us on slack at #vue-developer-designer-summit-2021. We are working on standing up Vue.js component library and supporting infrastructure in place to assist product teams in developing new features in Vue.js. We will also begin assisting with the migration of our frontend features to utilize the new framework.
Internal Resources
[edit]Wikimedia & MediaWiki Documentation
[edit]- Vue.js page on MediaWiki
- Vue.js/Testing
- Wikimedia Design Style Guide
- WVUI component library on GitHub (this is the current, transitional library; we intend to start work on a new shared project with input from multiple teams very soon)
- WVUI storybook demo
External Resources
[edit]About Vue
[edit]- Vue.js News (weekly newsletter)
- Mozilla Developer Network (MDN) Vue.js documentation
About Vue.js Testing
[edit]Build Tool
[edit]- Vite build tool (currently being explored)