"Sidebar" inside dashboards makes sense

[laupalombi]

Problem statement

We added a sidebar in Overview and its also available in custom dashboards. However, this has some fine tunning to do that is important before we can call this a done product.

1. In mobile navigation, right now we pile every module on top, which is problematic to the amount of tiles we pile up there. We need to find a better solutions that doesn't challenge discoverability.
2. We do have a statement of components that can live here, but there needs to be some way to handle visibility and limitation, and makes sense with the previous point. Either Summaries go somewhere else, and sidebar is only for alerts, or we do something else. It can't be a graveyard of things we want more attention on.

Scope & Boundaries

In scope

-UX changes within dashboards

Not in scope

-Global navigation

Foreseen solution

We rethink current distribution of cards and components in Overview considering both problems, and define strict logics for the sidebar and what can fit in there.

Community signals

Every now and then we have a discussion about something that should be in sidebar, or something relating access or customization of such elements. We need a structure that allows for this growth.

Risks & open questions

• How much growth is reasonable for Overview sidebar?
  -Can we avoid creating a "hide" feature to the risk of people not seeing what is hidden? Should it be only for summaries?
• Can we make reasonable rules for custom dashboards too so they are functional, or is it a rabbit hole?

Appetite

Medium - 1 cycle of frontend and design together

Execution issues

No response

Decision log

Date	Decision	Outcome
18/03	Scope	Let's keep custom dashboards outside of this bet, for avoiding a bigger scope. That can be done later in another bet.

[anakinsbrna]

about the risk for "Can we avoid creating a "hide" feature to the risk of people not seeing what is hidden? Should it be only for summaries?" I have an idea: can we add a signifier that tells people that sth is hidden? This would allow hiding things, while still being transparent - this signifier could be very subtle

[laupalombi]

OH very good point @anakinsbrna -it is a good potential solution

[jlpouffier]

I think the bet should be purely scoped to the home page and not go into allowing users to use the sidebar in custom dashboards.

And you should have a scedon one, simpler to bring the sidebar to custom dashboards. This one would be simpler, I feel. As it is already possible today with a lot of YAML fidling. We basically need to present it and handle drag and drop (Today you can't d&d if you add the sidebar on a custom dashbaord)

[laupalombi]

@jlpouffier I think I agree. Seeing the full picture of bets this can become a scope creep easily. Let me update it (keeping the original content for context)