You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 28, 2022. It is now read-only.
We have some internal facing services that need to let users perform actions at any time. We've seen this in JUI, PUI, fees and payments. We've also seen this in other x-government systems such as CJS:
We originally designed grey buttons to work inside the blue case bar (also known as entity or details bar) like this:
But this didn't work because users couldn't spot the buttons. So we iterated and came up with this design:
The problem with the above design is that the actions are at the page level and aren't signifying their intention correctly. Sometimes we may want page-specific actions in and around that area such as on a data table where the actions sit above (not below). And you may have a search in the top right.
Then we looked at other ways to incorporate these buttons above, below, next to the sub navigation. None of it worked well for various reasons.
So our latest iteration involves changing the colour/style of the case/details bar to grey instead of blue.
By making the details bar grey it's less dominant which helps:
the buttons stand out and live in the right place
to use the space more efficiently
a genuine in-page alert appear most prominently
The text was updated successfully, but these errors were encountered:
We have some internal facing services that need to let users perform actions at any time. We've seen this in JUI, PUI, fees and payments. We've also seen this in other x-government systems such as CJS:
We originally designed grey buttons to work inside the blue case bar (also known as entity or details bar) like this:
But this didn't work because users couldn't spot the buttons. So we iterated and came up with this design:
The problem with the above design is that the actions are at the page level and aren't signifying their intention correctly. Sometimes we may want page-specific actions in and around that area such as on a data table where the actions sit above (not below). And you may have a search in the top right.
Then we looked at other ways to incorporate these buttons above, below, next to the sub navigation. None of it worked well for various reasons.
So our latest iteration involves changing the colour/style of the case/details bar to grey instead of blue.
By making the details bar grey it's less dominant which helps:
The text was updated successfully, but these errors were encountered: