Using Blueprints

I was doing some reading on Flask, especially the strategies of structuring the content, because I thought we would need to separate the API and graphing part of the site soon or it will get too messy. I think using Blueprints would really help with this. It's the native way of doing this and it seems very scaleable. It would also make it much easier to work simultaneously on different parts of the site without risking merge conflicts and the like.
There are several different strategies how to organize the files that Blueprints use - I chose to encapsulate all code related to a blueprint into one folder, because it seemed to fit best.

Since Es is currently working on the URLdecoder I think we can't really merge this, it's meant more as a discussion topic. :)