[Quick spike] As a UX designer/Engineer, I want to investigate if we can hide details behind hover-based interactions so that users can choose whether to see additional information.
Scope:
- information that is already there
- extra information that we have to get e.g. from wikidata
- photos
- links, e.g. to places in wikidata or diffs (note that the wikidata black hover over doesn't have links currently)
- actions e.g. clicking on a settings button
Priorities:
- info to inform UX interviews
- increase understanding for engineers
**Acceptance Criteria:**
- Research potential performance impact.
- What if there is no javascript (if we use the hovers extension)
- Comparison of the engineering effort/size of the different options for implementation - e.g. part of wikibase, or using hovers extension
**Checklist**
[x] Research UI context for hover-based tooltips in Wikipedia
[] Would it cause an issue for loading times
[] Check if it's enabled for recent changes and for watchlist
[] See the existing research on this from the web team:
- Extensive documentation [[ https://www.mediawiki.org/wiki/Page_Previews | here ]]
- “Why it took a long time to build that tiny link preview on Wikipedia” - [[ https://medium.com/freely-sharing-the-sum-of-all-knowledge/why-it-took-a-long-time-to-build-that-tiny-link-preview-on-wikipedia-d5bd734df8fe | blog post from Jon Robson ]]
- https://diff.wikimedia.org/2018/05/09/page-previews-documentation/
[] //add task//
[] //add task//