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 ...
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 ...
Assuming you need a UX solution rather than a technical one, if the character count can't be accurate then don't use one. Try an alternative pattern, such as a completion 'progress bar' that fills up as the user types.
Once they get over the maximum limit then let them know so they can amend 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 ...
A second layer would be problematic because modal windows are closed by clicking outside of them. If the user clicks outside of the second layer, does that close the first modal window, too?
Some alternatives for showing "additional assets" in a modal window could be:
"Show more" link that opens a panel to reveal the ...