nAdoni is a library that provides a way to check for updates to one or more binaries via an update manifest, and then to download an archive containing the updated binaries.
Through #1 it is now possible to automatically generate the website content. We should set up an automated build for the website so that any changes automatically get deployed.
It would be nice if we could write the documentation in one location and then have that published both in the github project wiki and on the website. If possible also pull in the API documentation, links to downloads, blog posts, and other reference materials
The website automatically includes the wiki pages but not the API documentation. If we can generate Markdown files for the API documentation then we could include those in the web site generation process.
Before we do that we'll have to sort out some questions:
How are we going to deal with different versions of the API. Preferably we'd like to include all versions but that might be tricky to provide
Where are we going to get the assemblies and XML documentation files from. It would probably be best to get these from the releases.