Noah Klayman

@safu9 since this isn't getting any attention, why don't you make a separate package (`electron-builder-icon-maker`) so that we don't have to install from your git repo. Thanks!

What about [vuepress](https://vuepress.vuejs.org)? It supports markdown -> HTML, is open source, has a zero-config build step, and can be deployed anywhere.

If you want, I'd be happy to convert the docs into separate pages for each h2 using vuepress and submit a PR.

I converted docs to [vuepress](https://v0.vuepress.vuejs.org/) in [my fork](https://github.com/nklayman/ava). just run `npm run docs:dev` to start dev server (w/ hot reload). I still need to configure the deploy command to handle...

What about publishing under a different url every time, ie docs.ava.io/v1/, docs.ava.io/v2? You could then create a custom drop-down that would redirect to the correct page. Each url would be...

Does anyone know how to get just the release tag? [https://api.github.com/repos/avajs/ava/releases](https://api.github.com/repos/avajs/ava/releases) gives you a lot of unnecessary info.

How should I authenticate with the API?

Since the graphql api forces use of an authentication token, maybe we should just host a json file with the release data ourselves, as part of the docs site.

Then your access key would be publicly available on the site. I can use a [postversion](https://docs.npmjs.com/misc/scripts) script to automate updating the json file, so it won't be an issue.

Updated my fork to support versioning. It requests the `releases.json`, located in the public folder. It creates a dropdown called "versions" and links each version. The link redirects to `/${version}`....