See issue #33

See issue #33

Instead of handling the visibility checks at render time we keep around a list
of visible routes and emit an event when they change. This way the welcome activity
can mirror what the menu shows and update at the same time.

This field specifies a list of roles that the logged-in user needs to
have to interact with this activity.

In the case of the app-shell this means the activity is hidden until
the user information is loaded after login.

This reverts commit bcfc8d65.

This seems to only work on the body

In the non-mobile mode add a padding to the left if there is a scrollbar.

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.

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.

Neuber, Eugen Ramon authored 4 years ago and Bekerle, Patrizio committed 4 years ago

Activate Matomo logging only after user logged in successfully. Deactivate if user logs out.