Redesign palindrom-error-catcher for user friendlyness #7
Description
This element is used by default in the layouts provided by Blending app suite.
In case the error appears at the navigation attempt (HTTP GET with Accept: application/json-patch+json) due to the user being offline, we should try to do the full window reload of the HTTP GET URI (that's that Turbolinks does).
For other kinds of errors, i.e. after a patch from the client, we should make changes to it to appear user friendly. Let's recap. It has two kinds of users:
- the end user, who simply needs to know that something terrible happened on the server while he was using the app and this is not his fault. He needs to be assisted to recover. Block further user input, big button to reload the page and try again.
- the app author, who needs to know that an error occured on the server which might be his fault actually. He needs to be pointed out where to search for more clues (browser console, Starcounter database log).
The error message needs to be designed with the industry best standards: https://www.nngroup.com/articles/error-message-guidelines/, https://medium.com/design-ideas-thoughts/designing-error-pages-8d82e16e3472
Some examples that I like:
