Add settings view

[joaquimrocha]

There should be a settings view to allow the user to configre several aspects of the dashboard / clusters.

Acceptance Criteria:

• [ ] There is a settings button and view available
• [ ] At first, the settings should allow to see the details of all the clusters configured and change their accent color (#15)

Design:

TBD

[ashu8912]

@joaquimrocha is there a design ready for this

[joaquimrocha]

Not yet.

[joaquimrocha]

The design is close to finish.

[joaquimrocha]

I had added a mockup here but turns out it needs some final touch.

[illume]

With github settings, I like how each section has it's own URL. So when you click on the sides or link to the settings from documentation or another part of the app it works.

What I don't like about github settings is you can't easily link to a section. Often there are many sections on a page, so you need to scroll down a lot. For example, if you click on the "Appearance" sidebar menu, and scroll down you see "Emoji skin tone preference". Would be better if there was an anchor on that section so people could link to it.

Search box? Settings like Edge (and firefox, etc) have a settings view that allows you to search within the different settings options.

[yolossn]

I think we can take "inspiration" from vscode for the way it handles settings for plugins, it allows plugins to have their own settings in a separate subsection.

[joaquimrocha]

Here is the latest design we have from @tsompura:

Also, about the search, I think it makes sense when we have more than a few options, i.e. more than one "page" of settings. This will likely happen in the future, but as an MVP for settings, I don't think search is needed.

[illume]

I think we can take "inspiration" from vscode for the way it handles settings for plugins, it allows plugins to have their own settings in a separate subsection.

I really like the idea of having plugins being able to add their own settings if they want. But I wonder if anyone needs that already?

For bundled plugins, they should probably not be listed under a plugins section? Because they are part of the app, and not plugins from the perspective of the users and the developers of those apps.

[ashu8912]

[yolossn]

Adding the points from our discussion.

1. In In-cluster mode it is import to make the message correct that the settings are specific to the user and not something a admin can set for the whole application. Like setting the language to french for example and expecting it to be the default for all users.
2. In In-cluster mode if the user sets the settings in a browser and accesses headlamp from another device or browser the settings will be completely different.