Add CHANGELOG to website about less-docs HOT 6 CLOSED

@ChrisCinelli can you clarify what you meant with the "BONUS" point? At first it sounds like you're referring to tags on the Less.js repo, then it sounds like you're referring to tags on the lesscss.org repo...?

from less-docs.

Example: I have some products that use bootstrap v1. For maintenance I had to find a link to the documentation provided by somebody else.
I think it would be great to have always on the homepage the doc regarding last released version.
But at the end of the page in the Changelog session it would be nice to have the version numbers (ex: 1.0, 1.1, 1.3.3, 1.4.2 etc) that link the old versions of the documentation.
In this way the latest version of the documentation can be clean instead of having: "in v 1.4 this behave like this, but in v 1.3.3 it behave like that". The changelog and the older documentation should be enough to get all the necessary info.
I would add that in the changelog you could have also a migration/incompatibility link.

Ex:

    <h1>Changelog</h1>
    <h2><a href="/doc-v142/index.html">v.1.4.2</a></h2>
    <span class="migration">Migration guide from v 1.3.3</span><br/>
    <ul> ... </ul>

If the version numbers are x.y.z (like in 1.3.3) and the z are just bug fixes (that is probably a good idea), we just need a migration guide only between different x.y versions.

I called it "bonus" because in the list at less/less.js#1050 (comment) this was the point that was probably taking the longest while the others seemed more important, deliver immediate value and doable in less than 2 hours with the current lesscss.org code.

from less-docs.

I was just trying to clarify which repo you were referring to when you mentioned the tags. A while ago I ported the CHANGELOG to yaml and have templates setup to be able to do what you're suggesting (both lodash and handlebars). I just wanted to clarify because I can easily have the links dynamically generated as well, and I wanted to make sure that it would be done in a way that made sense based on your suggestion.

thanks for clarifying, this is helpful

from less-docs.

Django has a good example of versioned documentation. It even warns you if you're looking at docs for a "work in progress" development build.

https://docs.djangoproject.com/en/1.5/

Notice the version number in the docs url as well as the version changing widget at the bottom right.

from less-docs.

I love the idea. I think we can easily work this in. I'm working hard to get everything consolidated so I can start pushing stuff up.

from less-docs.

Closing this since change log is kept now .

from less-docs.