Benefits of Vue only are that we won't need to change PageTriage's visual appearance, which means we can skip community consultation and a designer. Also, a volunteer has already started the rewrite.
Current thinking is that no matter what, PageTriage front end needs updating to more modern frameworks. Backbone.js and Underscore.js are used in PageTriage, but not anywhere else in the mediawiki ecosystem. This is a big source of technical debt, making the PageTriage extension hard to work on.
If key stakeholders are able to coalesce around the "Vue only" rewrite strategy, here are some steps we could follow to implement it:
- Install Vue scaffolding in PageTriage repo, get it working
- Get a Special:VuePagesFeed working. Thanks to T324914: Add [[User:DannyS712/VueNPP.js]] to PageTriage repo, this is already written, it just needs to be debugged and tweaked a bit.
- Once Special:VuePagesFeed is working well and is confirmed to be a good copy of Special:NewPagesFeed, deploy the VuePagesFeed to replace the old NewPagesFeed
- Page Curation toolbar
- Get the Page Curation toolbar working with Vue, with some way to keep it hidden from most patrollers, but with the ability to enable for select users for testing.
- Once the Vue Page Curation toolbar is working well and is confirmed to be a good copy of the old Page Curation toolbar, deploy the Vue Page Curation toolbar to replace the old Page Curation toolbar