Next.js: Improve error template

[leo]

We've internally workout a slight improvement to the error template:

BEFORE:

AFTER:

It's now slightly better looking, responsive and has no . anymore.

Please take the styling AND markup from here. The code should be as similar as possible to what you can find in this file, so that it's in sync with all of the other parts/errors of the ZEIT ecosystem.

Ignore the CSS selectors that aren't used in the markup, please!

VERY IMPORTANT: Don't adjust the existing error page style trying to match the style of the new one. Copy the style over from the new gist instead!

[jaydenseric]

IMO these error messages are sentences (not sentence "fragments" or titles) and should have sentence-correct end punctuation. Almost all UI guidelines recommend end punctuation for alert messages:

• https://ux.stackexchange.com/questions/18671/periods-at-the-end-of-a-sentence-in-alert-message
• https://developer.apple.com/tvos/human-interface-guidelines/interface-elements/alerts#alert-titles-and-messages
• https://msdn.microsoft.com/en-us/library/windows/desktop/dn742471.aspx
• https://docs.microsoft.com/en-us/dotnet/standard/exceptions/best-practices-for-exceptions#use-grammatically-correct-error-messages

One practical benefit is that it allows you to build out a particular message with commas, semicolons, multiple sentences etc. without breaking consistency.

See Safari and Chrome HTTP error messages:

[dav-is]

I'd like to hear the rational of why this issue is "Priority: OMG Maximum". Completely ridiculous...