preliminar re-organization of dust page.

basic docs for dust integration page
So, we do publish a tag every time we release. I always use `npm version patch` or whatever which updates the `package.json` and creates the `v` tag.

Updating the site's deps every time we publish an update to one of our packages seems normal and fine to me. Ideally we'd alway be testing out the updated package on the site before we publish a new version to npm.