-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
warning users about Expert and Advanced settings #673
Comments
When I'm right, the warning symbols (now red triangle with exclamation mark) should warn the user/administrator that this tabs should be handled carefully? What do you think about yellow triangles and not red? |
To me, yellow will also make me think something is wrong (a warning level problem, rather than an error level problem) Is there some "standard" icon for "expert settings" that is different to the "gear" icon that is usually used for "settings"? |
I think the naming is enough. If I am a careful user / admin I will treat expert settings with caution. If I am a careless user / admin I won't read anything, so I won't care what the tab of the settings is called or the symbol of it, I just click through it and set what I want. We already have our documentation. We already have admin trainings. I don't see why we have to change anything, additionally with the constraint from Product Management that the changes have to be minimal, so anything significant that would help is off limits anyway. |
I'd suggest to remove the red triangle and instead put a warning hint on each of the pages. Something like: "Please be careful and only change these values if you know what you are doing. Changes in production environments can cause severe issues." |
Ping! Ref. #672 |
I like it |
Currently this is the interface.
I think it may cause confusion. When I look and see these symbols I think something is wrong in the configuration, so do some others.
Maybe we should talk about this, and come to a solution.
Feel free to invite or assign or ping others in here
The text was updated successfully, but these errors were encountered: