Error pages

[tylerhunt]

trafficstars

If you've ever run into an "unexpected exit" error with Puma-dev, you know how frustrating it can be to have to start digging into logs to try to figure out where the error occurred so you even know where to start looking to fix the issue. Coming from Pow, this was a huge disappointment, as Pow has really nice error pages. They're both helpful and nicely designed, so while I appreciate other things about Puma-dev, the error experience is one of its weakest areas right now.

Example error page from Pow

I'd like to propose doing some work on this as an open source project at work, where I may also be able to get some assistance from a designer/front-end dev, but I'd like to know up front:

1. if this is something the maintainers are willing to add to Puma-dev, and
2. what the technical challenges in pursuing this will be.

I don't have any experience writing Go, but I'm willing to dig into it, because I think this would have a hugely positive impact on everyone using Puma-dev.

Could you weigh in on this, @evanphx?

[javan]

I may also be able to get some assistance from a designer/front-end dev

Feel free to use Pow's templates: https://github.com/basecamp/pow/tree/master/src/templates/http_server

[evanphx]

This is a good idea, we should do it.