chore(docs): add button to link to stable docs

[petebacondarwin]

No description provided.

[mary-poppins]

Thanks for the PR! Please check the items below to help us merge this faster. See the contributing docs for more information.

• Uses the issue template (#7727)

If you need to make changes to your pull request, you can update the commit with git commit --amend.
Then, update the pull request with git push -f.

Thanks again for your help!

[btford]

Related: I recently implemented this for karma's docs: karma-runner/karma-runner.github.com#21

I'm wondering if we couldn't make this more obvious in the Angular docs. The problem is that our docs generator doesn't work particularly well if you want to re-generate the site with old content but a new template.

[petebacondarwin]

@btford - good idea. I think the best plan is to move to a "container" docs web site, which hosts the docs for the different versions. If necessary, we could regenerate docs for previous versions.

There are complexities that would need to be handled with this approach but it is going to need to be the way forward, since our new development strategy of multiple, individually versioned, small modules for Angular 2 will need a more flexible documentation site.

[btford]

@petebacondarwin: I started a novel static site generator a while ago that regenerates content on a per-sha basis. – https://github.com/btford/quinoa

[EmperorEarth]

This is still a minor annoyance that I, like many others, bump into a dozen times a day.
Can we get a timeline on a fix?

Caitp's hack was more than sufficient to provide a quick, temporary fix as you all work on Angular 2.0. #7513 (comment)

[petebacondarwin]

I guess you are referring to this PR? :-) I want to get it in but it just doesn't look nice. If you want to help with the layout then please do.

[petebacondarwin]

This is too messy. I have created a simple fix for now - moving the latest version of each of the main development branches to the top of the version drop-down. See aa7dbf0