T249051 is wrapping up but signs point to starting Vue.js search component development in a new, shareable NPM repo. This task builds on that work by evaluating the different technologies chosen by the WMDE Vue.js experts for their library and in what ways that can be leveraged to help build fine components fast for the Vue.js search project.

Specifically, this task is to explore building a single component in a copy of the WMDE component library. There is no expectation that the component will be committed afterwards but it could be a head start on future work regardless of the baseline used. For example, what does a Button look done WMDE fashion and what made development in/efficient?

Leveraging the choices WMDE has already pioneered has a number of possible benefits that are worth exploring:

• WMDE's approaches are proven. WMDE is on their third year with Vue.js and is using it in production in a number of places including: Wikidata mobile termbox, Wikidata bridge (beta), Wikidata Tainted References.
• The scaffolding phase of the Vue.js search work can be diminished.
• There is interest by WMDE in providing component review as able. Writing components like they do may improve the ability of their engineering talent to contribute their expertise to the project.

Like the rest of the Vue.js search project, this task is not a replacement for a proper long term, WMF or WMDE-wide decision which has many stakeholders across orgs, departments, and roles but it may help inform that discussion. The scope is for Vue.js search development only which should be efficient and informative.

Acceptance criteria

• A decision is made as to what parts are wanted to be copied or forked and tasks are created or updated.
• WMDE is consulted as needed and informed (primary contacts are @WMDE-leszek, @darthmon_wmde).