All notifications should go in the notification center AND you can show them in the dashboard notifications related to dashboard only.
You might do the same for each page, especially if the notification is about an error.
When the user clicks in the notification center on a notification related to a page, they would expect to see the error with all ...
Interesting Question and Flow.
I am assuming I have understood your question correctly.
Let us check the flow in this case.
1 : User Does a change(on CMS in this example)
2 : The change is validated from server side on some conditions you need to have a check with.
3 : User should be given the +ve or -ve feedback based on validation.
It is a 3 step process ...
The best option would be to go with the single password field, but ONLY if these are both applicable:
Your "forgot password" functionality is a smooth process. It should be a quick and easy process that makes resetting the password can happen effortlessly.
You give the user the option, with a checkbox or something, to make the password entry ...
From a dictionary definition of dashboard:
the panel facing the driver of a vehicle or the pilot of an aircraft, containing instruments and controls.
Using this as a jumping-off point, it would be perfectly safe to assume that controls to perform actions could happily be presented alongside data in a dashboard. In fact, if you remove the controls, you ...
Yes, the menu-like dropdown would the right location to place the logout button.
You don't have to go far to see an example implementation. Just click the top right button on this website and you'll find an option to logout right below it.
Don't make the user input this data, in most cases.
Having users remember, calculate, and enter their mileage is a fairly labor-intensive pattern. When a task becomes a lot of effort, users are less likely to perform it
daily. A carbon-tracking app is something that you want them to develop a habit around using, so it needs to be very easy.
Know what apps ...
What is the standard convention for whether the icon itself should be clickable and the only clickable item next to the text?
I cannot recall any strict convention for that case – whether the icon should be the only clickable item next to the text depends on the context.
There are some examples when it happens:
tooltips (question mark icon is clickable)
The reason is that the text is something he wants to copy and paste to add to a filter while others want to see the destination of that text in a new window.
As long as the text is easily selectable, I see no problem in having the text being part of the link as well. An example is your UX Stack Exchange user card: I can start selecting a centimeter or so ...