Takes a package name and a dest path. This way we can more eassily change the
layout and it will error out on package name typos or missing packages.

as is the case with font packages

They were hardcoded in more places

The rollup json plugin allows accessing keyss with named exports,
so we can read the package name at build time.

Add a scope to all package names and set to version to 0.1.0

See merge request !8

Add a scope so we don't have to care about naming conflicts
and set the verison to 0.1.0 since we don't have a stable API yet.

Chromium sometimes hangs when multiple karma runs happen
at the same time :(

Now that we have clearer separated sections in responsive mode the different
spacing stand out so unify them a bit.

Also in case the menu is in sticky mode it's kinda small and hard to hit via touch
so add some padding there and remove some margin from the headline instead to keep
the overall height the same.

tests: use tdd mode, unify karma config, don't depend on puppeteer

See merge request !7

While it's nice to have a fixed chrome version it slows down the yarn install,
downloads a lot of things, and the chrome version depends on various
system packages so one needss to have chromium installed anyway.

This means developers that want to work on tests need firefox and chdomium installed.

Sadly I couldn't find a way to make browsers optional in case the developer
only has one installed.

Use tdd in all cases to be more consisstend.
Also since last year we can use chai with rollup directly, so
do that everywhere instead of relying on karma-chai injecting
it in to the global scope.

not supported in firefox 68

auth-keycloak: make sure the token is always valid for at least 20 seconds

See merge request !6

More in line with native button elements

The keycloak library currently only sends us an event in case the token
is about to expire, which is problematic because there is a time window
where we don't have a new token yet and on mobile the timers used
might be suspended and come too late.

To avoid this we check every 10 seconds that the token is valid for 30
and to work around suspended timers we also check on "visibilitychange"
which should trigger then the website gets visible again after the browser
sleeps.

we use ayarn workspaces now