opened up to any image url

- support for non wiki(m|p)edia hosted images
- enhanced questionnaire with input fields for missing values
Do you really need to remove the API object being passed to the constructor? The API is more like a subject of configuration - imagining a flexible and extensible platform using multiple APIs, there probably should be something like an API manager which is passed to <code>Application</code> letting the front-page pick the appropriate API. For now, it should be enough to keep passing the Commons API and just replace that in FrontPage when not loading a Wiki(p|m)edia asset.