Regardless of the UI design we eventually settle on, the Image Browsing prototype will need to be able to show "relevant images" to the user when it gets triggered.
"Relevant" images could include:
- All images from the current article page
- excluding small things like icons, flags, etc (what's the cut-off size?)
- Images from equivalent pages on other-language wikis
- Images from other related articles on the same wiki
- Images from Commons (or Wikidata) that meet certain criteria (this may be out of scope for the MVP)
The MVP prototype will likely not exhaust the possibilities here.
Another high-level goal (aside from relevance) is that we want to prioritize community curation. If the community has already spent time and effort selecting images for a given article, we want to prioritize that content. If we do explore pulling images from places like Commons, what kinds of "signals" can we rely on for relevance?
Finally, while it is probably out of scope for the MVP, we may need to consider what an editorial workflow would look like for this feature – if we decided to scale out an image browsing prototype, we'd probably want to give editors a way to directly include/exclude content here (overriding whatever is automatically provided if desired).
Acceptance Criteria
- RG engineers should discuss what kind of a procedure we want to rely on here at a high level before we build it in code.
- Document the decisions made in terms of how to do this in an appropriate venue (wiki page, markdown ADR file in codebase, etc)
Actual implementation work should take place in a follow-up task; the goal here is to come up with a plan.
