Together with UX we need to investigate handling of different possible failure scenarios for the discovery page feature that we can already anticipate.
| Scenario | Priority | Figma link |
| API is not reachable | ||
| API data is stale (UI can see last time updated) | ||
| Pagecount unavailable (available in the next 24h) | ||
ACs:
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Evelien_WMDE | T339334 🟩 Introduce the Discovery feature to the new page on Wikibase Cloud | |||
| Resolved | Evelien_WMDE | T344581 🟢 API: expose wiki data in public endpoint | |||
| Resolved | Evelien_WMDE | T344436 🟢 Implement the Discover feature layout | |||
| Declined | None | T344585 🟢 Hook up Discovery feature frontend to API | |||
| Open | None | T344588 Implement failure modes for Discovery page |
Hey @Deniz_WMDE , thanks for setting up this ticket! I was just talking with @Tarrow about it the other day. For me it would be best if you could compile as many possible errors and edge cases in a list so that I can then go through them in one swoop.
I already discussed the scenario of an unavailavle page count with @Andrew-WMDE last week. That could also be something added to the list.
I edited the ticket to make a table out of the bullet points so we can then use the same ticket to discuss the priority with @Evelien_WMDE and link it to the mocks. Hope that's alright!