Update changelog's design

[alrra]

Now that the rules (and soon formatters and parses) are no longer included in sonarwhal, and each of them will have it's own changelog, we should start a discussion about what should be display on the https://sonarwhal.com/about/changelog/ page.

[alrra]

Note: GitHub provides a feed for releases.

[molant]

We need to take into account that we point the user to that url when there's a new version:

[alrra]

Talking to @molant, we were thinking that maybe we should have some kind of aggregator of all the changelogs, similar to:

https://changelog.travis-ci.com/
https://blog.github.com/changelog/

[ststimac]

Those two are pretty different content & design-wise. The Travis one seems to just be summaries with links and the github one links out to individual update pages with summaries and links.

[molant]

The general idea is that instead of grouping by version we group by date and put all the updates of all the packages at that time.

Structure wise, something like the following:

[ststimac]

Got it. Ok.

[ststimac]

Are the changes for each package going to be grouped into bug fixes/improvements and new features still?

[molant]

The changelog comes with that information. I think it will be useful to have it but it could have a different visual. Up to you!

[ststimac]

Here are a couple different variations for an updated layout:

__

--

--

[molant]

I think I like the first option best. @webhintio/core what do you think?

[alrra]

No. 3 for me, then the first one.

[antross]

I like the first one best, but all are good.