Fix layout for inner documentation cards

[AnXh3L0]

This PR fixes extra spacing/layouting for the cards inside individual documentation pages.

Before

After

[AnXh3L0]

The second commit adds an initial version of the code that pulls the latest release number, and the latest changelog. The layout of this is only a draft and it can be improved upon. Additionally, more data can be pulled automatically so we can make a big part of the site "dynamic". I would like to hear your thoughts @ByteHamster @keunes and anyone else :)
https://user-images.githubusercontent.com/25004151/177218804-8fe28dca-dc74-4bce-8002-15ea93982749.mp4

[ByteHamster]

This PR fixes extra spacing/layouting for the cards inside individual documentation pages.

Thanks, looks good. Next time, please create a new PR for each feature, so that the features can be merged+reviewed individually. I would already merge that first commit but have some comments about the second one.

The second commit adds an initial version of the code that pulls the latest release number

I think I would move it below the download button. Having it above the main website text is a bit too prominent. I have two style ideas:

• I would try adding a light gray background below the expanded changelog
• I would remove the padding between the blue and the gray box, so that there is a single box with two colors instead of two boxes within each other

[keunes]

Hi @AnXh3L0,

Welcome back! :) I would love merge already the documentation cards improvement, while allowing some more time for tweaks to the 'latest release' feature (which looks quite cool already!).

Could we somehow still split the two?

Cheers

[AnXh3L0]

Hey @keunes,

Thanks :D Sure, I believe we can split the two, and then make another PR for the latest release feature.

[keunes]

@AnXh3L0 Would you mind doing the split? I don't know how to do it properly (via git). I could take & apply your changes in another PR, but then you wouldn't be the git author :)

[AnXh3L0]

@keunes sure, I'll try to deal with it this evening.

[AnXh3L0]

@keunes @ByteHamster you can merge this PR and squash the commits. I will then work on the GitHub-related changes on a new branch and open another PR.

[keunes]

Thanks @AnXh3L0!