Hardcoded values about co-design HOT 5 CLOSED

I'll review this later/tomorrow and fix some of these things.

However, at least the last point is not a problem:

1. If the modal body exceeds that height, scroll bars appear.
2. On mobile, the modal body spans the whole height, due to this rule:

   co-design/src/_modals.scss

   Line 115 in c969990

   flex-grow: 1;

from co-design.

I don't think, the hard-coded values will lead to a problem with responsiveness. CD is fully responsive AFAIK and AFAICT.

I'll review the decision to use pixels rather than ems, however that might take some time and is rather low priority (at least for me - feel free to open a PR) unless one can demonstrate actual problems with it (with screenshots).

from co-design.

Hardcoded values might pose issues regarding code quality.

I should've probably opened a separate issue; it's about the pixels. Pixels and other absolute units are per definition non-responsive. Which means a user on a 4k display will have the same button shadow as somebody on his 640p Raspi display. And that's non-responsive.

As the W3 schools article I quoted states:

The absolute length units are fixed and a length expressed in any of these will appear as exactly that size. Absolute length units are not recommended for use on screen, because screen sizes vary so much. However, they can be used if the output medium is known, such as for print layout.

Wth an exception, however:

Pixels (px) are relative to the viewing device. For low-dpi devices, 1px is one device pixel (dot) of the display. For printers and high resolution screens 1px implies multiple device pixels.

from co-design.

This is being worked on.

from co-design.

All values are now set in the _config.scss, except for those, that cannot be changed while maintaining the basic design idea.

from co-design.