Document and REST-ify API

[loleg]

While a basic API description is in the README and we already use the API for interesting things like chatbots, the support is currently very basic. Integration with tools like Flask API and Swagger (via Flask RESTplus or Flask Restless) would help make the platform more interesting for other developers. Ideally we would also make the API bi-directional (fully RESTful) through this effort.

[loleg]

What also always helps are bootstraps and samples. Here is, for one, a Vue.js-based app made for a hackathon in November:

https://codesandbox.io/s/cool-cloud-ozl5k

[loleg]

As mentioned in #176, setting up rich event content is cumbersome for users not familiar with HTML or Markdown. Making improvements to the API documentation and doing some integration work would help to make dribdat a better 'headless' provider of hackathon event information for any website.

[loleg]

Not that Flask-REST has been superceded by Flask-RESTX and there are compelling alternatives like Flask-smorest out there which make me rethink some of the base patterns of the project, I think this should be the foundation of a wholesome rewrite of dribdat.