You Should Never See A Blank Page

One of the things I really like about working with the Rust programming language is that it has great error messages. It takes some practice to decipher them. Once you do, they are incredibly valuable. They'll usually walk you through what you need to do to fix your issue.

In fact, one of the Rust maintainers goes off the philosophy that it's a bug if you can't figure out what to do. I'd like to get to that level for Neopoligen. But, first things first. To start with my goal is that you should never see a blank page if something goes wrong while you're working on your site. Neopoligen will do the best it can to output whatever it can. If it's completely lost, it'll put up an error page with as much info as possible.

This is a difference between working on a project for myself and working on something that other folks will use. I know enough about the system that if a blank page shows up I know where to look. No one else would have the same chance.

Make the error messages better over time is one of my explicit goals. In the mean time, we'll make sure that at least something shows up when things go sideways.