You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As the number of metrics is growing, we need a way to clarify the UI and only show the important one first and have a way to show all metrics separately.
The text was updated successfully, but these errors were encountered:
When I'm looking at front-end metrics, I ignore the editor metrics and vice versa. It feels these are two different sets that I don't need to see together. Are they different "projects"? Can they be grouped (shown/hidden) using tabs?
For front-end metrics, there are different "scenarios". At the moment, we are tracking the times for the homepage of a site, but we could add new metrics for the single post template. Unlike the comment before (front-end vs editor), for these "scenarios", it'd be valuable to look at them all together. Like a table, where rows are the metrics and columns the scenario, so to speak.
When I'm looking at front-end metrics, I ignore the editor metrics and vice versa. It feels these are two different sets that I don't need to see together. Are they different "projects"? Can they be grouped (shown/hidden) using tabs?
Want to spin up an issue about this, I think we need both.
For instance, If I want a big picture about Gutenberg, I'd like to see: "type", "first block" and "LCP" personally.
Another idea: the cards can be hidden and rearranged by the user. That way, I can construct my own dashboard. However, this doesn't solve the fact that front-end metrics for different views (homepage vs single post) would be the same.
As the number of metrics is growing, we need a way to clarify the UI and only show the important one first and have a way to show all metrics separately.
The text was updated successfully, but these errors were encountered: