Refactor CSS modules

[Kaptard]

I'm submitting a...

• Bug report
• Feature request
• Documentation issue or request

Current behavior

Most styles are defined individually inside components, but we could probably abstract some of these and make them more easily available, either through scss mixins or global css classes.

Expected behavior

Manual styling should be reduced to a minimum.

Minimal reproduction of the problem

Environment

Browser:

• Chrome (desktop) version:
• Chrome (Android) version:
• Chrome (iOS) version:
• Firefox version:
• Safari (desktop) version:
• Safari (iOS) version:
• IE version:
• Edge version:

For development issues:

• Node version:
• Operating System:

Additional Description

I'm sure someone already figured out how to do this systematically, so we should probably start by researching other's methods.

[Kaptard]

refactor: Refactor CSS modules into a more structured structure :^)

[Bitti09]

what about a switch to tailwindcss ? manual css styling won't be necessary after that

[Kaptard]

The idea was to make our own library of classes like that to fit our own style guides. But it's certainly a good point of reference.