[Documentation] Documentation needed for public release

[JonathanMace]

• (Vaastav) deciding on how all documentation, tutorials, API docs, blog posts, website stuff, etc. should be organizing; setting up the processes for all of this; and documenting those processes (and rules about where different kinds of docs should be kept) so that others can easily add documentation to the appropriate places.
• Code comments: [Documentation] Documentation of applications and plugins (Vaastav) #117
• Code comments: [Documentation] Documentation of applications and plugins (Jonathan) #118
• Website: initial blog post(s) e.g. introducing blueprint
• Website, Repo Docs: tutorials / getting started / 'dive in' type documentation for (a) running an existing application+wiring; (b) changing the existing application's wiring; (c) writing a new application
• a central page, probably on the website, that indexes all of the known applications
• a central page, probably in the repo docs, that lists all available plugins
• repo doc explaining basic expository documentation for (a) writing a plugin; (b) how the wiring spec stuff works; (c) how the IR and code generation works -- this doesn't need to be too good because we can direct people to just talk to us if they want to do these things
• metadata in github repos and mailing list (e.g. filling out display names, descriptions, links to websites/mailing lists, etc.)

[vaastav]

Application Index Page: https://blueprint-uservices.github.io/apps/

[vaastav]

Plugins Index Page: https://blueprint-uservices.github.io/plugins/