{"id":18739,"date":"2013-11-02T11:33:08","date_gmt":"2013-11-02T09:33:08","guid":{"rendered":"https:\/\/mamchenkov.net\/wordpress\/?p=18739"},"modified":"2013-11-02T11:33:08","modified_gmt":"2013-11-02T09:33:08","slug":"github-error-pages","status":"publish","type":"post","link":"https:\/\/mamchenkov.net\/wordpress\/2013\/11\/02\/github-error-pages\/","title":{"rendered":"GitHub error pages"},"content":{"rendered":"\n

I’ve praised GitHub many a time in posts on this blog and in numerous conversations over a pint. \u00a0Today, I found yet another reason to do so – GitHub error pages. \u00a0We’ve all seen a parallax 404<\/a> by now, right?<\/p>\n

\"github<\/a><\/p>\n

Today was the first time I looked into the source code of the page. \u00a0It greets one with the following words right under the HTML 5 Doctype definition:<\/p>\n

Hello future GitHubber! I bet you’re here to remove those nasty inline styles,
\nDRY up these templates and make ’em nice and re-usable, right?<\/p>\n

Please, don’t. https:\/\/github.com\/styleguide\/templates\/2.0<\/a><\/p><\/blockquote>\n

The link provides even more goodness. \u00a0The list of other (all?) GitHub error templates is provided with explanation of which one fires when, as well as an insightful list of rules that GitHub uses for building error pages. \u00a0Have a look:<\/p>\n

If you’re visiting from the internet, feel free to learn from our style. This is a guide we use for our own apps internally at GitHub. We encourage you to set up one that works for your own team.<\/p>\n

Error pages should be built such that they require zero scripting, zero javascript, and zero dependency on anything whatsoever. That means static HTML with inline CSS and base64-encoded images.<\/p>\n

The following are banned from every error page:<\/p>\n