I love that they are doing this, BUT the big header "503: Service Unavailable" is what is first read and in my experience, most users will just stop in their tracks and return later (assuming the site is having technical issues) without reading the rest.
We made some deliberate decisions to try to make it look as little as possible like a real error code. I think most people will realize that it's not an actual technical issue, nothing else on our site looks like this and we've given them plenty of warning through posts.
Comments
I love that they are doing this, BUT the big header "503: Service Unavailable" is what is first read and in my experience, most users will just stop in their tracks and return later (assuming the site is having technical issues) without reading the rest.
I would not want to be manning the tech support phones today.
We made some deliberate decisions to try to make it look as little as possible like a real error code. I think most people will realize that it's not an actual technical issue, nothing else on our site looks like this and we've given them plenty of warning through posts.
Right. I wanted it to be pure apache error message except for the text. El Hamstero Mustardo here talked me down.