Open paulsonder opened 1 month ago
@paulsonder I had one question that I commented on the design about being able to expand the Summary (or if we should put expanded features in a new sort of page or component), such as viewing the list of Map Types in the repo.
If we can answer that question, then otherwise this design is ready to go to Dev!
Thanks @jamlung-ri
The designs have been updated to include a link to 'View all'. My proposal is that we decide how many summaries to display in this list by default, then expand to see all once a user clicks the link.
If further work is required to improve the UX of this based on real insights, I would suggest that's something we can look at later? For example, using a modal...
@snyaggarwal Moving to 'Ready for dev' - let me know if you would like to schedule some time to discuss.
@jamlung-ri @paulsonder I have added this on QA. Need to understand more on "View All". Right now almost everything is listed without view all.
Thanks @snyaggarwal! Agreed that we need to be clear about View All. Putting feedback below:
@jamlung-ri @paulsonder
@snyaggarwal
Re: We can give recalculate button next to Summary, @paulsonder What do you think?
If the user needed to reload, should we show an error state rather than an incorrect summary, is that technically possible?
@paulsonder Its not always possible. There are two types of issues in this:
2nd situation is what happens 95%+ times and that's easy to identify but not the other one. I would suggest we somehow give an option to retrigger it (its there in v2) and also show some specific state that it failed to calculate.
I've updated the Repo designs to include a link to re-run the summary.
Let me know what you think.
@jamlung-ri This is deployed on QA/STaging
This is looking good. I don't see any problems, but the Canonical Registry thing is still needed for discussion, it looks like.
User interface can be found here.
The Summary sits in the right of the Repo template.
Please record any feedback that needs to be actioned before moving the Dev here.
For future requirements, let's capture in a separate ticket and prioritise accordingly.