| • Prtksxna | |
| Jan 6 2017, 5:31 AM |
| F5241297: search-annotations.png | |
| Jan 6 2017, 11:15 AM |
| F5241175: reference-ltr.png | |
| Jan 6 2017, 11:15 AM |
Some text options-
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | MarkTraceur | T144302 Release FileAnnotations on the Beta Cluster | |||
| Open | None | T151327 Explore designs for FileAnnotations | |||
| Declined | dchen | T153296 Moderated usability testing for FileAnnotations prototypes | |||
| Declined | None | T154747 FileAnnotations prototype: Search: Guide user during empty state |
Do we want to take this space to explain the full spectrum of what is possible with annotations or just help the user type something in the search box? I think the latter, with a 'Learn more' link.
The goal of my proposal was to provide a minimal piece of information that helps to understand why to annotate and the benefits of doing so. Not about instructions about how to do so since the single search field already suggests which is the next step (although the placeholder could help here too).
The kind of message should respond to questions like "why should I add annotations?" or "which kind of related content is welcome?"
I created a mockup (based on VE education illustration: F5241175) to illustrated the idea:
The text copy can be different, and it is possible to add a link to learn more if we think it is needed (e.g., turning the "and more" part into a link ).
Since the 2016/2017 FileAnnotations prototype work is now quite outdated and both Wikidata and Commons have new features and design plans (like moving new features to Vue.js on Commons), and the extension is not actively under development, the best thing to do is close these tasks and create new ones when/if there's a team available to pick up development on this feature.