Geo: POC | Present Geo Replicables in a "single" view
Requirements
-
UI in a more generalized state: #208470 (closed) -
GraphQL API that supports blobs and repositories: &2525
What and Why
With the introduction of Geo Self-Service, we will begin to have too many data types to continue to create new "views" for each time they are introduced.
There has been a lot of talk and thought about how we can represent important replication information to the users, outside of our typical paginated listing of each data type.
Example of current Geo Replication listing:
In opening this issue, my goal is to get all our thoughts in one place to reference as we works towards this end goal.
From conversations I've had with different team members, I have a few key takeaways:
- This new view should call higher attention to "non-synced" items.
- Non-synced items should have actionable items on them to help resolve their issues.
- Forever expanding the side-nav is not feasible.
@sunjungp had an amazing sketching activity that helps showcase some of our teams ideas as to what this view may look like.
Proposal
- Continue gathering data from our key stakeholders around how they want to interact with Geo
- As we fledge out Geo Self Service, begin to think about how we can best represent all replicable data as well as what is the most important to know about the replicable data.
- When we are ready, start converting the existing views of Replicable Data (Designs, Projects, Uploads, etc...) into this new Generalized view of all replicable data.
What does success look like?
- Generalized view that supports existing (and new) functionality for all replicable data types.
- No longer need to do any additional frontend coding to expose a new replicable data type
- Users understand why something is failing to sync and what they need to do to fix it in the UI
cc: @geo-team
Edited by Zack Cuddy