From e7fd26528d08d43cbd072bd9e7e47b43d8c55742 Mon Sep 17 00:00:00 2001
From: ludoholic <ludoholic@users.noreply.github.com>
Date: Tue, 20 Aug 2024 11:10:26 +0000
Subject: [PATCH] deploy: 722a4995722caf869e02d61d8749277bf59cdeec

---
 docs/afm/client-afm.html                      | 12 +++---
 docs/afm/core.html                            | 38 +++++++++---------
 docs/afm/plugin-address-search.html           | 40 +++++++++----------
 docs/afm/plugin-attributions.html             | 10 ++---
 docs/afm/plugin-draw.html                     | 26 ++++++------
 docs/afm/plugin-export.html                   | 12 +++---
 docs/afm/plugin-gfi.html                      | 20 +++++-----
 docs/afm/plugin-icon-menu.html                |  8 ++--
 docs/afm/plugin-layer-chooser.html            | 10 ++---
 docs/afm/plugin-legend.html                   |  4 +-
 docs/afm/plugin-loading-indicator.html        | 12 +++---
 docs/afm/plugin-pins.html                     | 18 ++++-----
 docs/afm/plugin-scale.html                    |  8 ++--
 docs/afm/plugin-toast.html                    | 18 ++++-----
 docs/afm/plugin-zoom.html                     | 14 +++----
 docs/generic/client-generic.html              |  6 +--
 docs/generic/core.html                        | 38 +++++++++---------
 docs/generic/lib-custom-types.html            |  2 +-
 docs/generic/plugin-address-search.html       | 40 +++++++++----------
 docs/generic/plugin-attributions.html         | 10 ++---
 docs/generic/plugin-draw.html                 | 26 ++++++------
 docs/generic/plugin-export.html               | 12 +++---
 docs/generic/plugin-filter.html               | 20 +++++-----
 docs/generic/plugin-fullscreen.html           | 12 +++---
 docs/generic/plugin-geo-location.html         | 14 +++----
 docs/generic/plugin-gfi.html                  | 20 +++++-----
 docs/generic/plugin-icon-menu.html            |  8 ++--
 docs/generic/plugin-layer-chooser.html        | 10 ++---
 docs/generic/plugin-legend.html               |  4 +-
 docs/generic/plugin-loading-indicator.html    | 12 +++---
 docs/generic/plugin-pins.html                 | 18 ++++-----
 docs/generic/plugin-reverse-geocoder.html     | 12 +++---
 docs/generic/plugin-scale.html                |  8 ++--
 docs/generic/plugin-toast.html                | 18 ++++-----
 docs/generic/plugin-zoom.html                 | 14 +++----
 docs/meldemichel/client-meldemichel.html      | 10 ++---
 docs/meldemichel/core.html                    | 38 +++++++++---------
 docs/meldemichel/lib-custom-types.html        |  2 +-
 docs/meldemichel/lib-invisible-style.html     |  2 +-
 docs/meldemichel/plugin-address-search.html   | 40 +++++++++----------
 docs/meldemichel/plugin-attributions.html     | 10 ++---
 docs/meldemichel/plugin-filter.html           | 20 +++++-----
 docs/meldemichel/plugin-fullscreen.html       | 12 +++---
 docs/meldemichel/plugin-geo-location.html     | 14 +++----
 docs/meldemichel/plugin-gfi.html              | 20 +++++-----
 docs/meldemichel/plugin-icon-menu.html        |  8 ++--
 docs/meldemichel/plugin-layer-chooser.html    | 10 ++---
 .../meldemichel/plugin-loading-indicator.html | 12 +++---
 docs/meldemichel/plugin-pins.html             | 18 ++++-----
 docs/meldemichel/plugin-reverse-geocoder.html | 12 +++---
 docs/meldemichel/plugin-scale.html            |  8 ++--
 docs/meldemichel/plugin-toast.html            | 18 ++++-----
 docs/meldemichel/plugin-zoom.html             | 14 +++----
 docs/snowbox/client-snowbox.html              |  2 +-
 docs/snowbox/core.html                        | 38 +++++++++---------
 docs/snowbox/lib-custom-types.html            |  2 +-
 docs/snowbox/plugin-address-search.html       | 40 +++++++++----------
 docs/snowbox/plugin-attributions.html         | 10 ++---
 docs/snowbox/plugin-draw.html                 | 26 ++++++------
 docs/snowbox/plugin-export.html               | 12 +++---
 docs/snowbox/plugin-fullscreen.html           | 12 +++---
 docs/snowbox/plugin-geo-location.html         | 14 +++----
 docs/snowbox/plugin-gfi.html                  | 20 +++++-----
 docs/snowbox/plugin-icon-menu.html            |  8 ++--
 docs/snowbox/plugin-layer-chooser.html        | 10 ++---
 docs/snowbox/plugin-legend.html               |  4 +-
 docs/snowbox/plugin-loading-indicator.html    | 12 +++---
 docs/snowbox/plugin-pins.html                 | 18 ++++-----
 docs/snowbox/plugin-reverse-geocoder.html     | 12 +++---
 docs/snowbox/plugin-scale.html                |  8 ++--
 docs/snowbox/plugin-toast.html                | 18 ++++-----
 docs/snowbox/plugin-zoom.html                 | 14 +++----
 docs/textLocator/client-textLocator.html      |  2 +-
 docs/textLocator/core.html                    | 38 +++++++++---------
 docs/textLocator/lib-custom-types.html        |  2 +-
 docs/textLocator/lib-tooltip.html             |  2 +-
 docs/textLocator/plugin-address-search.html   | 40 +++++++++----------
 docs/textLocator/plugin-attributions.html     | 10 ++---
 docs/textLocator/plugin-draw.html             | 26 ++++++------
 docs/textLocator/plugin-icon-menu.html        |  8 ++--
 docs/textLocator/plugin-layer-chooser.html    | 10 ++---
 docs/textLocator/plugin-legend.html           |  4 +-
 .../textLocator/plugin-loading-indicator.html | 12 +++---
 docs/textLocator/plugin-scale.html            |  8 ++--
 docs/textLocator/plugin-toast.html            | 18 ++++-----
 docs/textLocator/plugin-zoom.html             | 14 +++----
 .../node_modules/@polar/core/README.md        |  2 +-
 87 files changed, 649 insertions(+), 649 deletions(-)

diff --git a/docs/afm/client-afm.html b/docs/afm/client-afm.html
index 7213f453d..da95ac833 100644
--- a/docs/afm/client-afm.html
+++ b/docs/afm/client-afm.html
@@ -22,21 +22,21 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>POLAR AfM map client</h1>
+    <h1 id="polar-afm-map-client" tabindex="-1">POLAR AfM map client</h1>
 <p>This is a default compilation of POLAR feature packages for online services. This document and its child documents describe the setup.</p>
 
-<h2>Requirements</h2>
+<h2 id="requirements" tabindex="-1">Requirements</h2>
 <p>To understand this document, programming knowledge (preferably in JavaScript) are required. This is a technical document describing how to integrate the map client with its programmatic API.</p>
-<h2>Versioning</h2>
+<h2 id="versioning" tabindex="-1">Versioning</h2>
 <p>The map client honors <a href="https://semver.org/lang/de/">SemVer</a> versioning. Breaking Changes without a change in leading version number are bugs.</p>
-<h2>Library integration</h2>
+<h2 id="library-integration" tabindex="-1">Library integration</h2>
 <p>You may either use the AfM client with import syntax or via HTML tags. In the following, the integration via HTML is shown.</p>
 <pre><code class="language-html">&lt;script src=&quot;&lt;Path&gt;/dist/polar-client.js&quot;&gt;&lt;/script&gt;
 </code></pre>
 <p>The global variable <code>MapClient</code> is now available. All other files in the dist folder are pulled on demand by relative pathing.</p>
-<h2>Configuration and creation</h2>
+<h2 id="configuration-and-creation" tabindex="-1">Configuration and creation</h2>
 <p>The map client can be controlled with a configuration object. An example file is supplied in the folder <code>example</code>. This file can be used as base for your own configuration.</p>
-<h3>Programmatic integration</h3>
+<h3 id="programmatic-integration" tabindex="-1">Programmatic integration</h3>
 <p>The following is an abstract example.</p>
 <p>In your HTML, a div with unique ID is required that holds the following style properties. Width and height can be changed as you need, but are required to be defined.</p>
 <pre><code class="language-html">&lt;div
diff --git a/docs/afm/core.html b/docs/afm/core.html
index 30ed9bbdf..aa70cc755 100644
--- a/docs/afm/core.html
+++ b/docs/afm/core.html
@@ -22,8 +22,8 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Core</h1>
-<h2>Scope</h2>
+    <h1 id="core" tabindex="-1">Core</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The client's core is the base package to create clients in the POLAR environment.</p>
 <p>It offers this functionality:</p>
 <ul>
@@ -31,15 +31,15 @@ <h2>Scope</h2>
 <li>@masterportal/masterportalapi functionality</li>
 <li>Localization mechanism</li>
 </ul>
-<h2>Interaction</h2>
+<h2 id="interaction" tabindex="-1">Interaction</h2>
 <p>If a client is rendered as part of another page, the zoom and drag-pan behaviour is different to if the client is rendered as complete page.<br>
 If it's part of another page, drag-panning on mobile devices is only usable if at least two fingers are being used while on desktop clients the user can only zoom if using the respective platform modifier key (e.g. CTRL).</p>
 <p>It is important to note that the behaviour will be desktop-like on larger touchscreen devices (e.g. tablets).</p>
-<h2>Initialization / Configuration</h2>
+<h2 id="initialization-%2F-configuration" tabindex="-1">Initialization / Configuration</h2>
 <p>It depends on the client how exactly the initialization will take place for the embedding programmer. However, the core mechanism remains the same.</p>
 <p>The exported default object is an extended masterportalAPI, adding the <code>addPlugins</code> and extending the <code>createMap</code> functions. For masterportalAPI details, <a href="https://bitbucket.org/geowerkstatt-hamburg/masterportalapi/src/master/">see their repository</a>.</p>
 <p>To be able to see the map in production mode, the imported stylesheet has to have the property <code>data-polar</code>. The value can be chosen arbitrarily. ⚠️ Deprecated. The new field 'stylePath' should be used instead.</p>
-<h3>addPlugins</h3>
+<h3 id="addplugins" tabindex="-1">addPlugins</h3>
 <p>Before instantiating the map, all required plugins have to be added. Depending on how you use POLAR, this may already have been done. Ready-made clients (that is, packages prefixed <code>@polar/client-</code>) come with plugins prepared. You may add further plugins or proceed with <code>createMap</code>.</p>
 <p>In case you're integrating new plugins, call <code>addPlugins</code> with an array of instances.</p>
 <pre><code class="language-js">client.addPlugins([Plugin({ pluginConfig })])
@@ -55,7 +55,7 @@ <h3>addPlugins</h3>
   })
 </code></pre>
 <p>If the storeModule features a <code>setupModule</code> action, it will be executed automatically after initialization.</p>
-<h3>createMap</h3>
+<h3 id="createmap" tabindex="-1">createMap</h3>
 <p>The map is created by calling the <code>createMap</code> method. Depending on how you use POLAR, this may already have been done, as some clients come as ready-made standalone HTML pages that do this for you.</p>
 <pre><code class="language-js">MapClient.createMap({
   // arbitrary id, must point to a div
@@ -66,7 +66,7 @@ <h3>createMap</h3>
   /* Your Code, e.g. for setting up callbacks. */
 })
 </code></pre>
-<h4>mapConfiguration</h4>
+<h4 id="mapconfiguration" tabindex="-1">mapConfiguration</h4>
 <p>The mapConfiguration allows controlling many client instance details.</p>
 <table>
 <thead>
@@ -124,7 +124,7 @@ <h4>mapConfiguration</h4>
 </tr>
 </tbody>
 </table>
-<h5>mapConfiguration.LanguageOption</h5>
+<h5 id="mapconfiguration.languageoption" tabindex="-1">mapConfiguration.LanguageOption</h5>
 <p>A language option is an object consisting of a type (its language key) and the i18next resource definition. You may e.g. decide that the texts offered in the LayerChooser do not fit the style of your client, or that they could be more precise in your situation since you're only using <em>very specific</em> overlays.</p>
 <p>An example for a LanguageOption array usable in <code>createMap</code> is this array:</p>
 <pre><code class="language-ts">const languageOptions: LanguageOption[] = [
@@ -151,7 +151,7 @@ <h5>mapConfiguration.LanguageOption</h5>
 ]
 </code></pre>
 <p>To figure out the name of the locales to override, inspect the matching plugin in GitHub's file browser. In <code>packages/plugins</code>, open the plugin you desire to override. Each plugin's <code>src</code> folder contains a <code>language.ts</code> listing all used locale keys with appropriate nesting.</p>
-<h5>mapConfiguration.extendedMasterportalapiMarkers</h5>
+<h5 id="mapconfiguration.extendedmasterportalapimarkers" tabindex="-1">mapConfiguration.extendedMasterportalapiMarkers</h5>
 <table>
 <thead>
 <tr>
@@ -193,7 +193,7 @@ <h5>mapConfiguration.extendedMasterportalapiMarkers</h5>
 </tr>
 </tbody>
 </table>
-<h6>mapConfiguration.extendedMasterportalapiMarkers.MarkerStyle</h6>
+<h6 id="mapconfiguration.extendedmasterportalapimarkers.markerstyle" tabindex="-1">mapConfiguration.extendedMasterportalapiMarkers.MarkerStyle</h6>
 <table>
 <thead>
 <tr>
@@ -281,7 +281,7 @@ <h6>mapConfiguration.extendedMasterportalapiMarkers.MarkerStyle</h6>
 </tbody>
 </table>
 </blockquote>
-<h5>mapConfiguration.LayerConf</h5>
+<h5 id="mapconfiguration.layerconf" tabindex="-1">mapConfiguration.LayerConf</h5>
 <p>The layer configuration (or: service register) is read by the masterportalAPI. The full definition can be read <a href="https://bitbucket.org/geowerkstatt-hamburg/masterportal/src/dev/doc/services.json.md">here</a>.</p>
 <p>However, not all listed services have been implemented in the masterportalAPI yet, and no documentation regarding implemented properties exists there yet.</p>
 <p>Whitelisted and confirmed parameters include:</p>
@@ -289,7 +289,7 @@ <h5>mapConfiguration.LayerConf</h5>
 <li>WMS: id, name, url, typ, format, version, transparent, layers, STYLES</li>
 <li>WFS: id, name, url, typ, outputFormat, version, featureType</li>
 </ul>
-<h6>Example services register</h6>
+<h6 id="example-services-register" tabindex="-1">Example services register</h6>
 <pre><code class="language-json">[
   {
     &quot;id&quot;: &quot;my-wfs-id&quot;,
@@ -313,7 +313,7 @@ <h6>Example services register</h6>
 ]
 </code></pre>
 <p>Since this is the base for many functions, the service ID set in this is used to reference map material in many places of the map client.</p>
-<h5>&lt;...masterportalAPI.fields&gt;</h5>
+<h5 id="%3C...masterportalapi.fields%3E" tabindex="-1">&lt;...masterportalAPI.fields&gt;</h5>
 <p>The <code>&lt;...masterportalAPI.fields&gt;</code> means that any masterportalAPI field may also be used here <em>directly</em>. The most common fields are the following ones; for more, see masterportalAPI.</p>
 <table>
 <thead>
@@ -356,10 +356,10 @@ <h5>&lt;...masterportalAPI.fields&gt;</h5>
 </tr>
 </tbody>
 </table>
-<h5>&lt;plugin.fields&gt;</h5>
-<p>Plugins in POLAR are modular components that extend the functionality of the map client. They can be added using the <a href="#addPlugins">addPlugins</a> method and configured through the <code>mapConfiguration</code> object. Each plugin has its own set of fields and options that can be customized.</p>
+<h5 id="%3Cplugin.fields%3E" tabindex="-1">&lt;plugin.fields&gt;</h5>
+<p>Plugins in POLAR are modular components that extend the functionality of the map client. They can be added using the <a href="#addplugins">addPlugins</a> method and configured through the <code>mapConfiguration</code> object. Each plugin has its own set of fields and options that can be customized.</p>
 <p>On how to configure a plugin, see the respective plugin. The configuration is given in the <code>mapConfiguration</code> object by the plugin's name as specified in its respective documentation.</p>
-<h6>Global Plugin Parameters</h6>
+<h6 id="global-plugin-parameters" tabindex="-1">Global Plugin Parameters</h6>
 <p>Most plugins honor this additional field.</p>
 <table>
 <thead>
@@ -377,7 +377,7 @@ <h6>Global Plugin Parameters</h6>
 </tr>
 </tbody>
 </table>
-<h6>Example Configuration</h6>
+<h6 id="example-configuration" tabindex="-1">Example Configuration</h6>
 <p>For example, a <code>@polar/plugin-address-search</code> plugin can be configured like this:</p>
 <pre><code class="language-js">{
   addressSearch: {
@@ -387,7 +387,7 @@ <h6>Example Configuration</h6>
   }
 }
 </code></pre>
-<h5>mapConfiguration.vuetify</h5>
+<h5 id="mapconfiguration.vuetify" tabindex="-1">mapConfiguration.vuetify</h5>
 <p>These fields let you e.g. specify a <a href="https://vuetifyjs.com/en/features/theme/">Vuetify-Theme</a>. For more options, refer to the official vuetify documentation.</p>
 <p>Additionally to the regular fields, <code>primaryContrast</code> and <code>secondaryContrast</code> are interpreted. They serve as contrast colors to their respective fields and are used for e.g. button icons.</p>
 <pre><code class="language-js">{
@@ -403,7 +403,7 @@ <h5>mapConfiguration.vuetify</h5>
   }
 }
 </code></pre>
-<h2>Store</h2>
+<h2 id="store" tabindex="-1">Store</h2>
 <p>The core module features a vuex root store that all plugin vuex modules are plugged into. However, the root contents are only relevant to plugins. It is accessible with <code>map.$store</code>, and can be used as a starting point for plugin access.</p>
 <p>To ease use, the map instance also features a <code>subscribe</code> method that will register a watcher to any state field. Please mind that only documented paths should be used, and all others are subject to change without notice.</p>
 <pre><code class="language-js">// state subscription – listening to data held by the map client
diff --git a/docs/afm/plugin-address-search.html b/docs/afm/plugin-address-search.html
index 0a0b045fd..c247a447a 100644
--- a/docs/afm/plugin-address-search.html
+++ b/docs/afm/plugin-address-search.html
@@ -22,8 +22,8 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>AddressSearch</h1>
-<h2>Scope</h2>
+    <h1 id="addresssearch" tabindex="-1">AddressSearch</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The AddressSearch plugin allows users to search for an address. If multiple addresses are returned by services, the user is prompted to select a result.</p>
 <p>The plugin saves the chosen information as GeoJSON to the store so that following procedures may grab it or so that other plugins may use it.</p>
 <p>Currently supported services:</p>
@@ -32,8 +32,8 @@ <h2>Scope</h2>
 <li>WFS</li>
 <li>Some gazetteers/WFS-G (please request a check or try yourself, not 100% done)</li>
 </ul>
-<h2>Configuration</h2>
-<h3>addressSearch</h3>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
+<h3 id="addresssearch-1" tabindex="-1">addressSearch</h3>
 <p>The configuration allows defining and grouping services. Grouped services can be requested in a search at the same time, and one group of searches can be active at a time. When multiple searches are in a group, they may be extended with category information to make the results easier to browse.</p>
 <p>It is advised to either use one-search-per-group <em>or</em> all services in a singular group to avoid an overly complex UI. Mixed configurations may be required for more complex search requirements.</p>
 <p>In <code>categoryProperties</code> and <code>groupProperties</code>, id strings called <code>groupId</code> and <code>categoryId</code> are used. These are arbitrary strings you can introduce and reuse to group or categorize elements together. Regarding what groups and categories are, see further below.</p>
@@ -104,7 +104,7 @@ <h3>addressSearch</h3>
 </tbody>
 </table>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/afm/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
-<h4>addressSearch.searchMethodsObject</h4>
+<h4 id="addresssearch.searchmethodsobject" tabindex="-1">addressSearch.searchMethodsObject</h4>
 <table>
 <thead>
 <tr>
@@ -156,7 +156,7 @@ <h4>addressSearch.searchMethodsObject</h4>
 </tr>
 </tbody>
 </table>
-<h4>addressSearch.customSearchMethod</h4>
+<h4 id="addresssearch.customsearchmethod" tabindex="-1">addressSearch.customSearchMethod</h4>
 <p>This is a function with the following signature:</p>
 <pre><code>(
   // should be used to actually abort request
@@ -170,7 +170,7 @@ <h4>addressSearch.customSearchMethod</h4>
 ) =&gt; Promise&lt;FeatureCollection&gt; | never
 </code></pre>
 <p>With this, arbitrary services can be supported.</p>
-<h4>addressSearch.customSelectFunction</h4>
+<h4 id="addresssearch.customselectfunction" tabindex="-1">addressSearch.customSelectFunction</h4>
 <p>This is a function with the following signature:</p>
 <pre><code>({
   // VueX context object
@@ -182,7 +182,7 @@ <h4>addressSearch.customSelectFunction</h4>
 }) =&gt; void
 </code></pre>
 <p>With this, arbitrary click results can be supported. Please mind that undocumented mutations and actions fired in such a function are subject to change without further notice.</p>
-<h4>addressSearch.groupProperties</h4>
+<h4 id="addresssearch.groupproperties" tabindex="-1">addressSearch.groupProperties</h4>
 <table>
 <thead>
 <tr>
@@ -219,7 +219,7 @@ <h4>addressSearch.groupProperties</h4>
 </tr>
 </tbody>
 </table>
-<h4>addressSearch.categoryProperties</h4>
+<h4 id="addresssearch.categoryproperties" tabindex="-1">addressSearch.categoryProperties</h4>
 <table>
 <thead>
 <tr>
@@ -236,7 +236,7 @@ <h4>addressSearch.categoryProperties</h4>
 </tr>
 </tbody>
 </table>
-<h5>addressSearch.searchMethodsObject.queryParameters (type:common)</h5>
+<h5 id="addresssearch.searchmethodsobject.queryparameters-(type%3Acommon)" tabindex="-1">addressSearch.searchMethodsObject.queryParameters (type:common)</h5>
 <p>These fields are interpreted by all implemented services.</p>
 <table>
 <thead>
@@ -254,7 +254,7 @@ <h5>addressSearch.searchMethodsObject.queryParameters (type:common)</h5>
 </tr>
 </tbody>
 </table>
-<h5>addressSearch.searchMethodsObject.queryParameters (type:wfs)</h5>
+<h5 id="addresssearch.searchmethodsobject.queryparameters-(type%3Awfs)" tabindex="-1">addressSearch.searchMethodsObject.queryParameters (type:wfs)</h5>
 <table>
 <thead>
 <tr>
@@ -317,7 +317,7 @@ <h5>addressSearch.searchMethodsObject.queryParameters (type:wfs)</h5>
 <li>WFS 2.0.0 <code>{wildCard: &quot;%&quot;, singleChar: &quot;*&quot;, escapeChar: &quot;\&quot;}</code></li>
 <li>WFS 1.0.0 <code>{wildCard: &quot;*&quot;, singleChar: &quot;*&quot;, escape: &quot;\&quot;}</code></li>
 </ul>
-<h5>addressSearch.searchMethodsObject.queryParameters (type:gazetteer)</h5>
+<h5 id="addresssearch.searchmethodsobject.queryparameters-(type%3Agazetteer)" tabindex="-1">addressSearch.searchMethodsObject.queryParameters (type:gazetteer)</h5>
 <blockquote>
 <p>⚠️ &quot;gazetteer&quot; is deprecated. Please use &quot;mpapi&quot; instead.</p>
 </blockquote>
@@ -362,7 +362,7 @@ <h5>addressSearch.searchMethodsObject.queryParameters (type:gazetteer)</h5>
 </tr>
 </tbody>
 </table>
-<h5>addressSearch.searchMethodsObject.queryParameters (type:mpapi)</h5>
+<h5 id="addresssearch.searchmethodsobject.queryparameters-(type%3Ampapi)" tabindex="-1">addressSearch.searchMethodsObject.queryParameters (type:mpapi)</h5>
 <blockquote>
 <p><strong>Please mind that this requires a configured backend. A WFS's Stored Query is requested with predefined parameters using the <a href="https://bitbucket.org/geowerkstatt-hamburg/masterportalapi/src/master/">masterportalApi</a>. This implementation is meant for e.g. https://geodienste.hamburg.de/HH_WFS_GAGES, but works with other WFS configured in the same manner.</strong></p>
 </blockquote>
@@ -408,14 +408,14 @@ <h5>addressSearch.searchMethodsObject.queryParameters (type:mpapi)</h5>
 </tbody>
 </table>
 <p>While all fields are optional, configuring none of them will yield undefined behaviour. At least one search instruction should be set to <code>true</code>.</p>
-<h5>addressSearch.searchMethodsObject.queryParameters (type:bkg)</h5>
+<h5 id="addresssearch.searchmethodsobject.queryparameters-(type%3Abkg)" tabindex="-1">addressSearch.searchMethodsObject.queryParameters (type:bkg)</h5>
 <p>In <em>BKG</em> mode, queryParameter's key-value pairs are used in the service query. E.g. <code>{filter: { bundesland: 'Bremen' }}</code> results in the GET request URL having <code>&amp;filter=bundesland:Bremen</code> as suffix.</p>
 <p>For more options, please check the <a href="https://sg.geodatenzentrum.de/web_public/gdz/dokumentation/deu/geokodierungsdienst.pdf">official documentation</a> regarding what query parameters are interpreted.</p>
 <p>Additionally, it is possible to configure the parameters <code>accesstoken</code> (<code>Authorization</code>) or <code>apiKey</code> (custom header <code>X-Api-Key</code>) to send the described headers to the search service for authentication purposes.
 Note that this changes the request to be non-simple. To be able to use the parameters, the request has to be sent in <a href="https://developer.mozilla.org/en-US/docs/Web/API/Request/mode"><code>cors</code> mode</a> and has to support preflight request <code>OPTIONS</code>.</p>
-<h2>Store</h2>
-<h3>Mutations</h3>
-<h4>setSelectedGroupName</h4>
+<h2 id="store" tabindex="-1">Store</h2>
+<h3 id="mutations" tabindex="-1">Mutations</h3>
+<h4 id="setselectedgroupname" tabindex="-1">setSelectedGroupName</h4>
 <p>This can be used to change the selected search group by name.</p>
 <pre><code class="language-js">map.$store.commit(
   'plugin/addressSearch/setSelectedGroupName',
@@ -423,8 +423,8 @@ <h4>setSelectedGroupName</h4>
 )
 </code></pre>
 <p>Please mind that programmatically changing the search group will <em>not</em> trigger a search, unlike a search group change by the user. If you need a search after change, consider the <code>search</code> action.</p>
-<h3>Actions</h3>
-<h4>search</h4>
+<h3 id="actions" tabindex="-1">Actions</h3>
+<h4 id="search" tabindex="-1">search</h4>
 <p>This is a purely programmatical search method. It is not used by user input.</p>
 <pre><code class="language-js">map.$store.dispatch('plugin/addressSearch/search', {
   input: 'Bahnhofsstraße 12',
@@ -453,7 +453,7 @@ <h4>search</h4>
 </tr>
 </tbody>
 </table>
-<h3>State</h3>
+<h3 id="state" tabindex="-1">State</h3>
 <pre><code class="language-js">map.subscribe('plugin/addressSearch/chosenAddress', (chosenAddress) =&gt; {
   /* Your code. */
 })
diff --git a/docs/afm/plugin-attributions.html b/docs/afm/plugin-attributions.html
index 3e1b41457..6490147ee 100644
--- a/docs/afm/plugin-attributions.html
+++ b/docs/afm/plugin-attributions.html
@@ -22,11 +22,11 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Attributions</h1>
-<h2>Scope</h2>
+    <h1 id="attributions" tabindex="-1">Attributions</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>This plugin shows attributions (that is, legal information) regarding copyrights and sources of the currently visible layers.</p>
-<h2>Configuration</h2>
-<h3>attributions</h3>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
+<h3 id="attributions-1" tabindex="-1">attributions</h3>
 <p>All parameters are optional. However, setting neither <code>layerAttributions</code> nor <code>staticAttributions</code> results in an empty window.</p>
 <table>
 <thead>
@@ -70,7 +70,7 @@ <h3>attributions</h3>
 </tbody>
 </table>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/afm/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
-<h4>attributions.layerAttribution</h4>
+<h4 id="attributions.layerattribution" tabindex="-1">attributions.layerAttribution</h4>
 <table>
 <thead>
 <tr>
diff --git a/docs/afm/plugin-draw.html b/docs/afm/plugin-draw.html
index 7772b9ae3..8fc489d78 100644
--- a/docs/afm/plugin-draw.html
+++ b/docs/afm/plugin-draw.html
@@ -22,8 +22,8 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Draw</h1>
-<h2>Scope</h2>
+    <h1 id="draw" tabindex="-1">Draw</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The draw plugin allows users to draw features on the map. Drawn features may be edited and deleted.</p>
 <p>Currently supported OpenLayers geometry types:</p>
 <ul>
@@ -33,15 +33,15 @@ <h2>Scope</h2>
 <li><code>'Polygon'</code></li>
 </ul>
 <p>Also, <code>'Text'</code> is supported which is modeled as an OpenLayers <code>'Point'</code>. This is no default feature, so it must be specified in the configuration to use it.</p>
-<h2>User instructions for Text Mode</h2>
+<h2 id="user-instructions-for-text-mode" tabindex="-1">User instructions for Text Mode</h2>
 <p>The interaction with text features is not intuitive, which is why the text feature should come with instructions for the users:</p>
-<h3>Edit</h3>
+<h3 id="edit" tabindex="-1">Edit</h3>
 <p>To edit the text or the placement of the text feature, the user must click on the center of the text to select the point geometry below it. After selecting it, the user can move the point by keeping the left mouse button pressed, or edit the text in the input field that opens with selecting the feature. If more than one text size is specified in the configuration, the user can change the text size with a slider.</p>
-<h3>Delete</h3>
+<h3 id="delete" tabindex="-1">Delete</h3>
 <p>To delete the text, the user must either click on the point at the center of the text or use CTRL + left mouse button to open a box over all features that he or she wants to delete.</p>
-<h2>Configuration</h2>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
 <p>The styling of the drawn features can be configured to overwrite the default ol-style. Configuration is oriented around the <a href="https://openlayers.org/en/latest/apidoc/module-ol_style_Style.html#~StyleLike">OpenLayers styles</a>.</p>
-<h3>draw</h3>
+<h3 id="draw-1" tabindex="-1">draw</h3>
 <table>
 <thead>
 <tr>
@@ -69,7 +69,7 @@ <h3>draw</h3>
 </tbody>
 </table>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/afm/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
-<h5>draw.textStyle</h5>
+<h5 id="draw.textstyle" tabindex="-1">draw.textStyle</h5>
 <table>
 <thead>
 <tr>
@@ -91,7 +91,7 @@ <h5>draw.textStyle</h5>
 </tr>
 </tbody>
 </table>
-<h5>draw.textStyle.font</h5>
+<h5 id="draw.textstyle.font" tabindex="-1">draw.textStyle.font</h5>
 <table>
 <thead>
 <tr>
@@ -113,7 +113,7 @@ <h5>draw.textStyle.font</h5>
 </tr>
 </tbody>
 </table>
-<h4>draw.style (by example)</h4>
+<h4 id="draw.style-(by-example)" tabindex="-1">draw.style (by example)</h4>
 <p>The <code>@masterportal/masterportalapi</code> has vectorStyles in development. As soon as that's done, we shall use its styling syntax and methods.</p>
 <p>For the time being, please use this example as a rough reference as to what can currently be done.</p>
 <pre><code class="language-json">{
@@ -141,14 +141,14 @@ <h4>draw.style (by example)</h4>
   }
 }
 </code></pre>
-<h2>Store</h2>
-<h3>State</h3>
+<h2 id="store" tabindex="-1">Store</h2>
+<h3 id="state" tabindex="-1">State</h3>
 <pre><code class="language-js">map.subscribe('plugin/draw/featureCollection', (featureCollection) =&gt; {
   /* Your code. */
 })
 </code></pre>
 <p>The returned featureCollection is a <a href="https://geojson.org/">GeoJSON</a> FeatureCollection. It includes all drawn features and updates on changes.</p>
-<h2>Actions</h2>
+<h2 id="actions" tabindex="-1">Actions</h2>
 <pre><code class="language-js">map.$store.dispatch('plugin/draw/addFeatures', {
   geoJSON: {
     type: 'FeatureCollection',
diff --git a/docs/afm/plugin-export.html b/docs/afm/plugin-export.html
index ed22888a4..8bb458cf0 100644
--- a/docs/afm/plugin-export.html
+++ b/docs/afm/plugin-export.html
@@ -22,11 +22,11 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Export</h1>
-<h2>Scope</h2>
+    <h1 id="export" tabindex="-1">Export</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The Export plugin offers users to download the currently visible map canvas in a variety of file formats and by a variety of methods.</p>
-<h2>Configuration</h2>
-<h3>export</h3>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
+<h3 id="export-1" tabindex="-1">export</h3>
 <table>
 <thead>
 <tr>
@@ -60,12 +60,12 @@ <h3>export</h3>
 </table>
 <p>To remove user control, add <code>displayComponent: false</code> to the configuration and use the following interactions.</p>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/afm/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
-<h3>Actions</h3>
+<h3 id="actions" tabindex="-1">Actions</h3>
 <p>To programmatically trigger a &quot;screenshot&quot;, use this action.</p>
 <pre><code class="language-js">// type is 'Png', 'Jpg', or 'Pdf'
 map.$store.dispatch('plugin/export/exportAs', type)
 </code></pre>
-<h3>State</h3>
+<h3 id="state" tabindex="-1">State</h3>
 <p>This shows how a callback can be used to show the exported data in a suitable html element. The value of the <code>screenshot</code> variable is a base64-encoded string.</p>
 <pre><code class="language-js">const someElement = // ... however you retrieve your html element
   map.subscribe('plugin/export/exportedMap', (screenshot) =&gt;
diff --git a/docs/afm/plugin-gfi.html b/docs/afm/plugin-gfi.html
index e86380765..79b334df8 100644
--- a/docs/afm/plugin-gfi.html
+++ b/docs/afm/plugin-gfi.html
@@ -22,14 +22,14 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>GFI</h1>
-<h2>Scope</h2>
+    <h1 id="gfi" tabindex="-1">GFI</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The GFI plugin can be used to fetch and optionally display GFI (GetFeatureInfo) from WMS and WFS services as well as layers based on GeoJSON files. In a first step, the information is stored in the VueX store to allow for easy access. Display is optional and quite obstructive within the map client.</p>
 <blockquote>
 <p>⚠️ The display feature is currently not meant for production. Please use data bindings for display to avoid obstructing the map client.</p>
 </blockquote>
-<h3>Configuration</h3>
-<h4>gfi</h4>
+<h3 id="configuration" tabindex="-1">Configuration</h3>
+<h4 id="gfi-1" tabindex="-1">gfi</h4>
 <table>
 <thead>
 <tr>
@@ -92,7 +92,7 @@ <h4>gfi</h4>
 </tbody>
 </table>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/afm/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
-<h5>gfi.gfiLayerConfiguration</h5>
+<h5 id="gfi.gfilayerconfiguration" tabindex="-1">gfi.gfiLayerConfiguration</h5>
 <table>
 <thead>
 <tr>
@@ -156,7 +156,7 @@ <h5>gfi.gfiLayerConfiguration</h5>
 </tr>
 </tbody>
 </table>
-<h5>gfi.customHighlightStyle</h5>
+<h5 id="gfi.customhighlightstyle" tabindex="-1">gfi.customHighlightStyle</h5>
 <table>
 <thead>
 <tr>
@@ -178,7 +178,7 @@ <h5>gfi.customHighlightStyle</h5>
 </tr>
 </tbody>
 </table>
-<h5>gfi.featureList</h5>
+<h5 id="gfi.featurelist" tabindex="-1">gfi.featureList</h5>
 <table>
 <thead>
 <tr>
@@ -210,7 +210,7 @@ <h5>gfi.featureList</h5>
 </tr>
 </tbody>
 </table>
-<h4>Example configuration</h4>
+<h4 id="example-configuration" tabindex="-1">Example configuration</h4>
 <pre><code class="language-js">layers: {
   [serviceId]: {
     geometry: true,
@@ -235,8 +235,8 @@ <h4>Example configuration</h4>
   },
 },
 </code></pre>
-<h2>Store</h2>
-<h3>State</h3>
+<h2 id="store" tabindex="-1">Store</h2>
+<h3 id="state" tabindex="-1">State</h3>
 <p>If a successful query has been sent and a response has been received, the result will be saved in the store and can be subscribed through the path <code>'plugin/gfi/featureInformation'</code>. If, however, a query for a layer fails, a <code>Symbol</code> containing the error will be saved in the store instead to indicate the error.</p>
 <p>The exact value of <code>featureInformation</code> may vary wildly depending on the service used, but is always given as json representation here.</p>
 <pre><code class="language-js">map.subscribe('plugin/gfi/featureInformation', (featureInformation) =&gt; {
diff --git a/docs/afm/plugin-icon-menu.html b/docs/afm/plugin-icon-menu.html
index 81eabdbd4..7e69484f9 100644
--- a/docs/afm/plugin-icon-menu.html
+++ b/docs/afm/plugin-icon-menu.html
@@ -22,13 +22,13 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>IconMenu</h1>
+    <h1 id="iconmenu" tabindex="-1">IconMenu</h1>
 <p>The IconMenu offers an icon-button based menu to open various functionality as cards. This way, obstructive UI can be hidden until the user desires to open it. Please use carefully – users may have issues finding process-relevant buttons/interactions if you hide them here.<br>
 Currently, the IconMenu should only be rendered with <code>layoutTag</code> set to <code>NineLayoutTag.TOP_RIGHT</code>.</p>
-<h2>Scope</h2>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>It is meant for additional information/functionality (legend, other layers) or power users in non-public clients.</p>
 <p><em>Please note that the average user has never seen the client before and just wants to get done with it, not learn a map client.</em></p>
-<h2>Configuration</h2>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
 <blockquote>
 <p>⚠️ This plugin can't be configured with the <code>mapConfiguration</code>, but is configured during client construction. Currently, no way exists to add plugins to it after the build took place.</p>
 </blockquote>
@@ -60,7 +60,7 @@ <h2>Configuration</h2>
   ],
 }
 </code></pre>
-<h3>menus</h3>
+<h3 id="menus" tabindex="-1">menus</h3>
 <p>When landscape mode is active the IconMenu is oriented horizontally. Currently, the IconMenu works fine only if there is not more than one row of Icons in landscape mode.</p>
 
     
diff --git a/docs/afm/plugin-layer-chooser.html b/docs/afm/plugin-layer-chooser.html
index 9aa84a2d3..3709de5e4 100644
--- a/docs/afm/plugin-layer-chooser.html
+++ b/docs/afm/plugin-layer-chooser.html
@@ -22,12 +22,12 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>LayerChooser</h1>
+    <h1 id="layerchooser" tabindex="-1">LayerChooser</h1>
 <p>The tool offers layer selection to the user.</p>
-<h2>Scope</h2>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The LayerChooser offers an additive (usually Overlays, technically named with <code>type: 'mask'</code>) and an exclusive (usually background maps, <code>type: 'background'</code>) selection of layers to the users.</p>
 <p>Order of layers within a layer is currently always as initially configured.</p>
-<h2>Configuration</h2>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
 <p>The tool does not require any configuration for itself, but is based on the <code>mapConfiguration.layers</code> array. It will infer its options from there, and change layer visibility and availability depending on <code>minZoom</code> and <code>maxZoom</code>.</p>
 <p>Each object in <code>mapConfiguration.layers</code> array fits this definition:</p>
 <table>
@@ -82,7 +82,7 @@ <h2>Configuration</h2>
 </tbody>
 </table>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/afm/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
-<h3>mapConfiguration.layers.options</h3>
+<h3 id="mapconfiguration.layers.options" tabindex="-1">mapConfiguration.layers.options</h3>
 <p>An option wheel will appear in the layer chooser that allows opening a sub-menu with configured configuration options for the end user.</p>
 <table>
 <thead>
@@ -100,7 +100,7 @@ <h3>mapConfiguration.layers.options</h3>
 </tr>
 </tbody>
 </table>
-<h4>mapConfiguration.layers.options.layers</h4>
+<h4 id="mapconfiguration.layers.options.layers" tabindex="-1">mapConfiguration.layers.options.layers</h4>
 <p>This field is named like this to match the OGC specification for their name; that is, layers have layers that may have layers that may have layers, and so on. However, only the first level (a layer's layers) is currently implemented.</p>
 <table>
 <thead>
diff --git a/docs/afm/plugin-legend.html b/docs/afm/plugin-legend.html
index f21114f33..3789318d3 100644
--- a/docs/afm/plugin-legend.html
+++ b/docs/afm/plugin-legend.html
@@ -22,9 +22,9 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Legend</h1>
+    <h1 id="legend" tabindex="-1">Legend</h1>
 <p>The Legend module offers legend images as supplied by OGC services.</p>
-<h2>Configuration</h2>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/afm/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
 
     
diff --git a/docs/afm/plugin-loading-indicator.html b/docs/afm/plugin-loading-indicator.html
index 7d51f3256..f86342668 100644
--- a/docs/afm/plugin-loading-indicator.html
+++ b/docs/afm/plugin-loading-indicator.html
@@ -22,13 +22,13 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>LoadingIndicator</h1>
-<h2>Scope</h2>
+    <h1 id="loadingindicator" tabindex="-1">LoadingIndicator</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>A generic loading indicator that may be used by any plugin or outside procedure to indicate loading.</p>
-<h2>Configuration</h2>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/afm/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
-<h2>Store</h2>
-<h3>Mutations</h3>
+<h2 id="store" tabindex="-1">Store</h2>
+<h3 id="mutations" tabindex="-1">Mutations</h3>
 <pre><code class="language-js">// show loading indicator
 map.$store.commit('plugin/loadingIndicator/addLoadingKey', key)
 // hide loading indicator
@@ -37,7 +37,7 @@ <h3>Mutations</h3>
 <p><img src="./readme_loadingIndicator_example.png" alt="Loading indicator example"></p>
 <p>The key must be unique and is kept track of via a Set. It can't be added multiple times, and removing it once always removes it altogether. It is advised to use a key like <code>{my-plugin-or-application-name}-{procedure-name}</code> to avoid name conflicts. The LoadingIndicator will usually be used for asynchronous code.</p>
 <p>As such, <strong>always call <code>removeLoadingKey</code> in the <code>finally</code> section of your code</strong> to prevent hanging loading indicators.</p>
-<h3>Getters</h3>
+<h3 id="getters" tabindex="-1">Getters</h3>
 <p>You may desire to listen to whether the loader is currently being shown.</p>
 <table>
 <thead>
diff --git a/docs/afm/plugin-pins.html b/docs/afm/plugin-pins.html
index 1985b16de..2c36045af 100644
--- a/docs/afm/plugin-pins.html
+++ b/docs/afm/plugin-pins.html
@@ -22,12 +22,12 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Pins</h1>
-<h2>Scope</h2>
+    <h1 id="pins" tabindex="-1">Pins</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The pins plugin handles marking locations. Embedding processes can then use that coordinate for further steps. The plugin may react to other plugins, especially address searches.</p>
-<h2>Configuration</h2>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
 <p>The usage of <code>displayComponent</code> has no influence on the creation of Pins on the Map if this plugin is being used.</p>
-<h3>pins</h3>
+<h3 id="pins-1" tabindex="-1">pins</h3>
 <table>
 <thead>
 <tr>
@@ -84,7 +84,7 @@ <h3>pins</h3>
 </tr>
 </tbody>
 </table>
-<h4>pins.appearOnClick</h4>
+<h4 id="pins.appearonclick" tabindex="-1">pins.appearOnClick</h4>
 <table>
 <thead>
 <tr>
@@ -106,7 +106,7 @@ <h4>pins.appearOnClick</h4>
 </tr>
 </tbody>
 </table>
-<h4>pins.initial</h4>
+<h4 id="pins.initial" tabindex="-1">pins.initial</h4>
 <table>
 <thead>
 <tr>
@@ -133,7 +133,7 @@ <h4>pins.initial</h4>
 </tr>
 </tbody>
 </table>
-<h4>pins.style</h4>
+<h4 id="pins.style" tabindex="-1">pins.style</h4>
 <table>
 <thead>
 <tr>
@@ -155,8 +155,8 @@ <h4>pins.style</h4>
 </tr>
 </tbody>
 </table>
-<h2>Store</h2>
-<h3>State</h3>
+<h2 id="store" tabindex="-1">Store</h2>
+<h3 id="state" tabindex="-1">State</h3>
 <pre><code class="language-js">map.subscribe('plugin/pins/transformedCoordinate', (pinCoordinate) =&gt; {
   /* Your Code. */
 })
diff --git a/docs/afm/plugin-scale.html b/docs/afm/plugin-scale.html
index a0ce3dad2..28eaeeea7 100644
--- a/docs/afm/plugin-scale.html
+++ b/docs/afm/plugin-scale.html
@@ -22,14 +22,14 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Scale</h1>
+    <h1 id="scale" tabindex="-1">Scale</h1>
 <blockquote>
 <p>⚠ The Scale plugin is currently meant for passive usage only. It's API has not yet been finally defined, and is subject to change without further notice.</p>
 </blockquote>
-<h2>Scope</h2>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The scale plugin shows the current map resolution as relative scale (1:x) and/or absolute scale (a drawn line has length x units).</p>
-<h2>Configuration</h2>
-<h3>scale</h3>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
+<h3 id="scale-1" tabindex="-1">scale</h3>
 <table>
 <thead>
 <tr>
diff --git a/docs/afm/plugin-toast.html b/docs/afm/plugin-toast.html
index b552a70c4..05b3dfff4 100644
--- a/docs/afm/plugin-toast.html
+++ b/docs/afm/plugin-toast.html
@@ -22,12 +22,12 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Toast</h1>
-<h2>Scope</h2>
+    <h1 id="toast" tabindex="-1">Toast</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The toast plugin offers global functionality to display text messages to the user. These are the classic success, warning, info, and error messages, helping to understand what's going on or why something happened.</p>
-<h2>Configuration</h2>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
 <p>Please check the vuetify documentation to override the success, warning, info, or errors colors in general. To affect only this plugin, the following configuration parameters can be added to either the plugin instantiation or the mapConfiguration:</p>
-<h3>toast</h3>
+<h3 id="toast-1" tabindex="-1">toast</h3>
 <table>
 <thead>
 <tr>
@@ -60,7 +60,7 @@ <h3>toast</h3>
 </tbody>
 </table>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/afm/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
-<h4>toast.toastStyle</h4>
+<h4 id="toast.toaststyle" tabindex="-1">toast.toastStyle</h4>
 <table>
 <thead>
 <tr>
@@ -82,12 +82,12 @@ <h4>toast.toastStyle</h4>
 </tr>
 </tbody>
 </table>
-<h2>Store</h2>
-<h3>Actions</h3>
+<h2 id="store" tabindex="-1">Store</h2>
+<h3 id="actions" tabindex="-1">Actions</h3>
 <p>New entries are made via action. They are either dismissed after a timeout or by user interaction.</p>
 <pre><code class="language-js">map.$store.dispatch('plugin/toast/addToast', payload)
 </code></pre>
-<h4>Payload structure</h4>
+<h4 id="payload-structure" tabindex="-1">Payload structure</h4>
 <table>
 <thead>
 <tr>
@@ -124,7 +124,7 @@ <h4>Payload structure</h4>
 </tr>
 </tbody>
 </table>
-<h4>Usage example</h4>
+<h4 id="usage-example" tabindex="-1">Usage example</h4>
 <pre><code class="language-js">map.$store.dispatch('plugin/toast/addToast', {
   type: 'warning',
   text: 'Wrong hammer for screw.',
diff --git a/docs/afm/plugin-zoom.html b/docs/afm/plugin-zoom.html
index 7c39c3d72..e8bc270a5 100644
--- a/docs/afm/plugin-zoom.html
+++ b/docs/afm/plugin-zoom.html
@@ -22,10 +22,10 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Zoom</h1>
-<h2>Scope</h2>
+    <h1 id="zoom" tabindex="-1">Zoom</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The Zoom plugin offers functionality regarding map zooming.</p>
-<h2>Configuration</h2>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
 <p>The Zoom plugin offers a plus/minus button, and will adjust itself to the map's zoom settings on initialization.<br>
 It can be configured as followed.</p>
 <table>
@@ -55,8 +55,8 @@ <h2>Configuration</h2>
 </tbody>
 </table>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/afm/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
-<h2>Store</h2>
-<h3>State</h3>
+<h2 id="store" tabindex="-1">Store</h2>
+<h3 id="state" tabindex="-1">State</h3>
 <p>The map's zoom level can be listened to.</p>
 <table>
 <thead>
@@ -88,7 +88,7 @@ <h3>State</h3>
   /* This code is called on any zoomLevel update. */
 })
 </code></pre>
-<h3>Getters</h3>
+<h3 id="getters" tabindex="-1">Getters</h3>
 <table>
 <thead>
 <tr>
@@ -117,7 +117,7 @@ <h3>Getters</h3>
   }
 )
 </code></pre>
-<h3>Actions</h3>
+<h3 id="actions" tabindex="-1">Actions</h3>
 <p>The zoomLevel can be set programmatically.</p>
 <pre><code class="language-js">map.$store.dispatch('plugin/zoom/setZoomLevel', zoomLevelNumber)
 map.$store.dispatch('plugin/zoom/increaseZoomLevel')
diff --git a/docs/generic/client-generic.html b/docs/generic/client-generic.html
index dd3d17656..29285defd 100644
--- a/docs/generic/client-generic.html
+++ b/docs/generic/client-generic.html
@@ -22,12 +22,12 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Generic MapClient API 🗺️ <code>@polar/client-generic</code></h1>
+    <h1 id="generic-mapclient-api-%F0%9F%97%BA%EF%B8%8F-%40polar%2Fclient-generic" tabindex="-1">Generic MapClient API 🗺️ <code>@polar/client-generic</code></h1>
 <p>This client is based on <a href="https://github.com/Dataport/polar">POLAR</a> and subsequently the <a href="https://bitbucket.org/geowerkstatt-hamburg/masterportalapi/src/master/">masterportalAPI</a>. The following documentation only contains how this specific client can be used, and the minimal information required to get it running.</p>
 
 <p>For the development test deployments and example configurations, <a href="https://dataport.github.io/polar#plugin-gallery">see here</a>.</p>
 <p>For a minimum working example, <a href="https://github.com/dopenguin/polar-fossgis-2024">see here</a>.</p>
-<h2>Basic usage</h2>
+<h2 id="basic-usage" tabindex="-1">Basic usage</h2>
 <p>The NPM package <code>@polar/client-generic</code> can be installed via NPM or downloaded from the <a href="https://github.com/Dataport/polar/releases">release page</a>. When using <code>import mapClient from '@polar/client-generic'</code>, the object <code>mapClient</code> contains a method <code>createMap</code>. This is the main method required to get the client up and running. Should you use another import method, check the package's <code>dist</code> folder for available files.</p>
 <p>The method expects a single object with the following parameters.</p>
 <table>
@@ -87,7 +87,7 @@ <h2>Basic usage</h2>
 }
 </code></pre>
 <p>The value to <code>stylePath</code> is the same as as a <code>link</code> tag would have in its <code>href</code>.</p>
-<h3>Destroy instance</h3>
+<h3 id="destroy-instance" tabindex="-1">Destroy instance</h3>
 <p>The <code>mapInstance</code> returned by the <code>createMap</code> call can be destroyed by calling <code>mapInstance.$destroy</code>. This will not remove the rendered HTML, but unlink all internal creations and effects. This should be called before re-navigating, usual lifecycle hooks are <code>beforeDestroy</code> or <code>beforeUnmount</code>, depending on the framework in use.</p>
 <p>After this, <code>createMap</code> can be used again when the DOM is restored. That is, the original <code>div</code> with its <code>id</code> must be recreated, since POLAR changes the DOM in the <code>div</code>. Normally, an SPA will take care of this by itself since it will render the outlying component anew.</p>
 <p>Should this not be the case in your framework, the following snippet restores the DOM:</p>
diff --git a/docs/generic/core.html b/docs/generic/core.html
index 30ed9bbdf..aa70cc755 100644
--- a/docs/generic/core.html
+++ b/docs/generic/core.html
@@ -22,8 +22,8 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Core</h1>
-<h2>Scope</h2>
+    <h1 id="core" tabindex="-1">Core</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The client's core is the base package to create clients in the POLAR environment.</p>
 <p>It offers this functionality:</p>
 <ul>
@@ -31,15 +31,15 @@ <h2>Scope</h2>
 <li>@masterportal/masterportalapi functionality</li>
 <li>Localization mechanism</li>
 </ul>
-<h2>Interaction</h2>
+<h2 id="interaction" tabindex="-1">Interaction</h2>
 <p>If a client is rendered as part of another page, the zoom and drag-pan behaviour is different to if the client is rendered as complete page.<br>
 If it's part of another page, drag-panning on mobile devices is only usable if at least two fingers are being used while on desktop clients the user can only zoom if using the respective platform modifier key (e.g. CTRL).</p>
 <p>It is important to note that the behaviour will be desktop-like on larger touchscreen devices (e.g. tablets).</p>
-<h2>Initialization / Configuration</h2>
+<h2 id="initialization-%2F-configuration" tabindex="-1">Initialization / Configuration</h2>
 <p>It depends on the client how exactly the initialization will take place for the embedding programmer. However, the core mechanism remains the same.</p>
 <p>The exported default object is an extended masterportalAPI, adding the <code>addPlugins</code> and extending the <code>createMap</code> functions. For masterportalAPI details, <a href="https://bitbucket.org/geowerkstatt-hamburg/masterportalapi/src/master/">see their repository</a>.</p>
 <p>To be able to see the map in production mode, the imported stylesheet has to have the property <code>data-polar</code>. The value can be chosen arbitrarily. ⚠️ Deprecated. The new field 'stylePath' should be used instead.</p>
-<h3>addPlugins</h3>
+<h3 id="addplugins" tabindex="-1">addPlugins</h3>
 <p>Before instantiating the map, all required plugins have to be added. Depending on how you use POLAR, this may already have been done. Ready-made clients (that is, packages prefixed <code>@polar/client-</code>) come with plugins prepared. You may add further plugins or proceed with <code>createMap</code>.</p>
 <p>In case you're integrating new plugins, call <code>addPlugins</code> with an array of instances.</p>
 <pre><code class="language-js">client.addPlugins([Plugin({ pluginConfig })])
@@ -55,7 +55,7 @@ <h3>addPlugins</h3>
   })
 </code></pre>
 <p>If the storeModule features a <code>setupModule</code> action, it will be executed automatically after initialization.</p>
-<h3>createMap</h3>
+<h3 id="createmap" tabindex="-1">createMap</h3>
 <p>The map is created by calling the <code>createMap</code> method. Depending on how you use POLAR, this may already have been done, as some clients come as ready-made standalone HTML pages that do this for you.</p>
 <pre><code class="language-js">MapClient.createMap({
   // arbitrary id, must point to a div
@@ -66,7 +66,7 @@ <h3>createMap</h3>
   /* Your Code, e.g. for setting up callbacks. */
 })
 </code></pre>
-<h4>mapConfiguration</h4>
+<h4 id="mapconfiguration" tabindex="-1">mapConfiguration</h4>
 <p>The mapConfiguration allows controlling many client instance details.</p>
 <table>
 <thead>
@@ -124,7 +124,7 @@ <h4>mapConfiguration</h4>
 </tr>
 </tbody>
 </table>
-<h5>mapConfiguration.LanguageOption</h5>
+<h5 id="mapconfiguration.languageoption" tabindex="-1">mapConfiguration.LanguageOption</h5>
 <p>A language option is an object consisting of a type (its language key) and the i18next resource definition. You may e.g. decide that the texts offered in the LayerChooser do not fit the style of your client, or that they could be more precise in your situation since you're only using <em>very specific</em> overlays.</p>
 <p>An example for a LanguageOption array usable in <code>createMap</code> is this array:</p>
 <pre><code class="language-ts">const languageOptions: LanguageOption[] = [
@@ -151,7 +151,7 @@ <h5>mapConfiguration.LanguageOption</h5>
 ]
 </code></pre>
 <p>To figure out the name of the locales to override, inspect the matching plugin in GitHub's file browser. In <code>packages/plugins</code>, open the plugin you desire to override. Each plugin's <code>src</code> folder contains a <code>language.ts</code> listing all used locale keys with appropriate nesting.</p>
-<h5>mapConfiguration.extendedMasterportalapiMarkers</h5>
+<h5 id="mapconfiguration.extendedmasterportalapimarkers" tabindex="-1">mapConfiguration.extendedMasterportalapiMarkers</h5>
 <table>
 <thead>
 <tr>
@@ -193,7 +193,7 @@ <h5>mapConfiguration.extendedMasterportalapiMarkers</h5>
 </tr>
 </tbody>
 </table>
-<h6>mapConfiguration.extendedMasterportalapiMarkers.MarkerStyle</h6>
+<h6 id="mapconfiguration.extendedmasterportalapimarkers.markerstyle" tabindex="-1">mapConfiguration.extendedMasterportalapiMarkers.MarkerStyle</h6>
 <table>
 <thead>
 <tr>
@@ -281,7 +281,7 @@ <h6>mapConfiguration.extendedMasterportalapiMarkers.MarkerStyle</h6>
 </tbody>
 </table>
 </blockquote>
-<h5>mapConfiguration.LayerConf</h5>
+<h5 id="mapconfiguration.layerconf" tabindex="-1">mapConfiguration.LayerConf</h5>
 <p>The layer configuration (or: service register) is read by the masterportalAPI. The full definition can be read <a href="https://bitbucket.org/geowerkstatt-hamburg/masterportal/src/dev/doc/services.json.md">here</a>.</p>
 <p>However, not all listed services have been implemented in the masterportalAPI yet, and no documentation regarding implemented properties exists there yet.</p>
 <p>Whitelisted and confirmed parameters include:</p>
@@ -289,7 +289,7 @@ <h5>mapConfiguration.LayerConf</h5>
 <li>WMS: id, name, url, typ, format, version, transparent, layers, STYLES</li>
 <li>WFS: id, name, url, typ, outputFormat, version, featureType</li>
 </ul>
-<h6>Example services register</h6>
+<h6 id="example-services-register" tabindex="-1">Example services register</h6>
 <pre><code class="language-json">[
   {
     &quot;id&quot;: &quot;my-wfs-id&quot;,
@@ -313,7 +313,7 @@ <h6>Example services register</h6>
 ]
 </code></pre>
 <p>Since this is the base for many functions, the service ID set in this is used to reference map material in many places of the map client.</p>
-<h5>&lt;...masterportalAPI.fields&gt;</h5>
+<h5 id="%3C...masterportalapi.fields%3E" tabindex="-1">&lt;...masterportalAPI.fields&gt;</h5>
 <p>The <code>&lt;...masterportalAPI.fields&gt;</code> means that any masterportalAPI field may also be used here <em>directly</em>. The most common fields are the following ones; for more, see masterportalAPI.</p>
 <table>
 <thead>
@@ -356,10 +356,10 @@ <h5>&lt;...masterportalAPI.fields&gt;</h5>
 </tr>
 </tbody>
 </table>
-<h5>&lt;plugin.fields&gt;</h5>
-<p>Plugins in POLAR are modular components that extend the functionality of the map client. They can be added using the <a href="#addPlugins">addPlugins</a> method and configured through the <code>mapConfiguration</code> object. Each plugin has its own set of fields and options that can be customized.</p>
+<h5 id="%3Cplugin.fields%3E" tabindex="-1">&lt;plugin.fields&gt;</h5>
+<p>Plugins in POLAR are modular components that extend the functionality of the map client. They can be added using the <a href="#addplugins">addPlugins</a> method and configured through the <code>mapConfiguration</code> object. Each plugin has its own set of fields and options that can be customized.</p>
 <p>On how to configure a plugin, see the respective plugin. The configuration is given in the <code>mapConfiguration</code> object by the plugin's name as specified in its respective documentation.</p>
-<h6>Global Plugin Parameters</h6>
+<h6 id="global-plugin-parameters" tabindex="-1">Global Plugin Parameters</h6>
 <p>Most plugins honor this additional field.</p>
 <table>
 <thead>
@@ -377,7 +377,7 @@ <h6>Global Plugin Parameters</h6>
 </tr>
 </tbody>
 </table>
-<h6>Example Configuration</h6>
+<h6 id="example-configuration" tabindex="-1">Example Configuration</h6>
 <p>For example, a <code>@polar/plugin-address-search</code> plugin can be configured like this:</p>
 <pre><code class="language-js">{
   addressSearch: {
@@ -387,7 +387,7 @@ <h6>Example Configuration</h6>
   }
 }
 </code></pre>
-<h5>mapConfiguration.vuetify</h5>
+<h5 id="mapconfiguration.vuetify" tabindex="-1">mapConfiguration.vuetify</h5>
 <p>These fields let you e.g. specify a <a href="https://vuetifyjs.com/en/features/theme/">Vuetify-Theme</a>. For more options, refer to the official vuetify documentation.</p>
 <p>Additionally to the regular fields, <code>primaryContrast</code> and <code>secondaryContrast</code> are interpreted. They serve as contrast colors to their respective fields and are used for e.g. button icons.</p>
 <pre><code class="language-js">{
@@ -403,7 +403,7 @@ <h5>mapConfiguration.vuetify</h5>
   }
 }
 </code></pre>
-<h2>Store</h2>
+<h2 id="store" tabindex="-1">Store</h2>
 <p>The core module features a vuex root store that all plugin vuex modules are plugged into. However, the root contents are only relevant to plugins. It is accessible with <code>map.$store</code>, and can be used as a starting point for plugin access.</p>
 <p>To ease use, the map instance also features a <code>subscribe</code> method that will register a watcher to any state field. Please mind that only documented paths should be used, and all others are subject to change without notice.</p>
 <pre><code class="language-js">// state subscription – listening to data held by the map client
diff --git a/docs/generic/lib-custom-types.html b/docs/generic/lib-custom-types.html
index fc8188e5f..775c6e0a3 100644
--- a/docs/generic/lib-custom-types.html
+++ b/docs/generic/lib-custom-types.html
@@ -22,7 +22,7 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Custom Types</h1>
+    <h1 id="custom-types" tabindex="-1">Custom Types</h1>
 <p>This is a custom type library for overarching types. They can be used both in core, plugin, and lib packages to develop a common custom package-global type system.</p>
 <p>Keep it as small as possible and sort types where they belong, whenever possible.</p>
 
diff --git a/docs/generic/plugin-address-search.html b/docs/generic/plugin-address-search.html
index e665cdef6..99d9a0da0 100644
--- a/docs/generic/plugin-address-search.html
+++ b/docs/generic/plugin-address-search.html
@@ -22,8 +22,8 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>AddressSearch</h1>
-<h2>Scope</h2>
+    <h1 id="addresssearch" tabindex="-1">AddressSearch</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The AddressSearch plugin allows users to search for an address. If multiple addresses are returned by services, the user is prompted to select a result.</p>
 <p>The plugin saves the chosen information as GeoJSON to the store so that following procedures may grab it or so that other plugins may use it.</p>
 <p>Currently supported services:</p>
@@ -32,8 +32,8 @@ <h2>Scope</h2>
 <li>WFS</li>
 <li>Some gazetteers/WFS-G (please request a check or try yourself, not 100% done)</li>
 </ul>
-<h2>Configuration</h2>
-<h3>addressSearch</h3>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
+<h3 id="addresssearch-1" tabindex="-1">addressSearch</h3>
 <p>The configuration allows defining and grouping services. Grouped services can be requested in a search at the same time, and one group of searches can be active at a time. When multiple searches are in a group, they may be extended with category information to make the results easier to browse.</p>
 <p>It is advised to either use one-search-per-group <em>or</em> all services in a singular group to avoid an overly complex UI. Mixed configurations may be required for more complex search requirements.</p>
 <p>In <code>categoryProperties</code> and <code>groupProperties</code>, id strings called <code>groupId</code> and <code>categoryId</code> are used. These are arbitrary strings you can introduce and reuse to group or categorize elements together. Regarding what groups and categories are, see further below.</p>
@@ -104,7 +104,7 @@ <h3>addressSearch</h3>
 </tbody>
 </table>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/generic/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
-<h4>addressSearch.searchMethodsObject</h4>
+<h4 id="addresssearch.searchmethodsobject" tabindex="-1">addressSearch.searchMethodsObject</h4>
 <table>
 <thead>
 <tr>
@@ -156,7 +156,7 @@ <h4>addressSearch.searchMethodsObject</h4>
 </tr>
 </tbody>
 </table>
-<h4>addressSearch.customSearchMethod</h4>
+<h4 id="addresssearch.customsearchmethod" tabindex="-1">addressSearch.customSearchMethod</h4>
 <p>This is a function with the following signature:</p>
 <pre><code>(
   // should be used to actually abort request
@@ -170,7 +170,7 @@ <h4>addressSearch.customSearchMethod</h4>
 ) =&gt; Promise&lt;FeatureCollection&gt; | never
 </code></pre>
 <p>With this, arbitrary services can be supported.</p>
-<h4>addressSearch.customSelectFunction</h4>
+<h4 id="addresssearch.customselectfunction" tabindex="-1">addressSearch.customSelectFunction</h4>
 <p>This is a function with the following signature:</p>
 <pre><code>({
   // VueX context object
@@ -182,7 +182,7 @@ <h4>addressSearch.customSelectFunction</h4>
 }) =&gt; void
 </code></pre>
 <p>With this, arbitrary click results can be supported. Please mind that undocumented mutations and actions fired in such a function are subject to change without further notice.</p>
-<h4>addressSearch.groupProperties</h4>
+<h4 id="addresssearch.groupproperties" tabindex="-1">addressSearch.groupProperties</h4>
 <table>
 <thead>
 <tr>
@@ -219,7 +219,7 @@ <h4>addressSearch.groupProperties</h4>
 </tr>
 </tbody>
 </table>
-<h4>addressSearch.categoryProperties</h4>
+<h4 id="addresssearch.categoryproperties" tabindex="-1">addressSearch.categoryProperties</h4>
 <table>
 <thead>
 <tr>
@@ -236,7 +236,7 @@ <h4>addressSearch.categoryProperties</h4>
 </tr>
 </tbody>
 </table>
-<h5>addressSearch.searchMethodsObject.queryParameters (type:common)</h5>
+<h5 id="addresssearch.searchmethodsobject.queryparameters-(type%3Acommon)" tabindex="-1">addressSearch.searchMethodsObject.queryParameters (type:common)</h5>
 <p>These fields are interpreted by all implemented services.</p>
 <table>
 <thead>
@@ -254,7 +254,7 @@ <h5>addressSearch.searchMethodsObject.queryParameters (type:common)</h5>
 </tr>
 </tbody>
 </table>
-<h5>addressSearch.searchMethodsObject.queryParameters (type:wfs)</h5>
+<h5 id="addresssearch.searchmethodsobject.queryparameters-(type%3Awfs)" tabindex="-1">addressSearch.searchMethodsObject.queryParameters (type:wfs)</h5>
 <table>
 <thead>
 <tr>
@@ -317,7 +317,7 @@ <h5>addressSearch.searchMethodsObject.queryParameters (type:wfs)</h5>
 <li>WFS 2.0.0 <code>{wildCard: &quot;%&quot;, singleChar: &quot;*&quot;, escapeChar: &quot;\&quot;}</code></li>
 <li>WFS 1.0.0 <code>{wildCard: &quot;*&quot;, singleChar: &quot;*&quot;, escape: &quot;\&quot;}</code></li>
 </ul>
-<h5>addressSearch.searchMethodsObject.queryParameters (type:gazetteer)</h5>
+<h5 id="addresssearch.searchmethodsobject.queryparameters-(type%3Agazetteer)" tabindex="-1">addressSearch.searchMethodsObject.queryParameters (type:gazetteer)</h5>
 <blockquote>
 <p>⚠️ &quot;gazetteer&quot; is deprecated. Please use &quot;mpapi&quot; instead.</p>
 </blockquote>
@@ -362,7 +362,7 @@ <h5>addressSearch.searchMethodsObject.queryParameters (type:gazetteer)</h5>
 </tr>
 </tbody>
 </table>
-<h5>addressSearch.searchMethodsObject.queryParameters (type:mpapi)</h5>
+<h5 id="addresssearch.searchmethodsobject.queryparameters-(type%3Ampapi)" tabindex="-1">addressSearch.searchMethodsObject.queryParameters (type:mpapi)</h5>
 <blockquote>
 <p><strong>Please mind that this requires a configured backend. A WFS's Stored Query is requested with predefined parameters using the <a href="https://bitbucket.org/geowerkstatt-hamburg/masterportalapi/src/master/">masterportalApi</a>. This implementation is meant for e.g. https://geodienste.hamburg.de/HH_WFS_GAGES, but works with other WFS configured in the same manner.</strong></p>
 </blockquote>
@@ -408,14 +408,14 @@ <h5>addressSearch.searchMethodsObject.queryParameters (type:mpapi)</h5>
 </tbody>
 </table>
 <p>While all fields are optional, configuring none of them will yield undefined behaviour. At least one search instruction should be set to <code>true</code>.</p>
-<h5>addressSearch.searchMethodsObject.queryParameters (type:bkg)</h5>
+<h5 id="addresssearch.searchmethodsobject.queryparameters-(type%3Abkg)" tabindex="-1">addressSearch.searchMethodsObject.queryParameters (type:bkg)</h5>
 <p>In <em>BKG</em> mode, queryParameter's key-value pairs are used in the service query. E.g. <code>{filter: { bundesland: 'Bremen' }}</code> results in the GET request URL having <code>&amp;filter=bundesland:Bremen</code> as suffix.</p>
 <p>For more options, please check the <a href="https://sg.geodatenzentrum.de/web_public/gdz/dokumentation/deu/geokodierungsdienst.pdf">official documentation</a> regarding what query parameters are interpreted.</p>
 <p>Additionally, it is possible to configure the parameters <code>accesstoken</code> (<code>Authorization</code>) or <code>apiKey</code> (custom header <code>X-Api-Key</code>) to send the described headers to the search service for authentication purposes.
 Note that this changes the request to be non-simple. To be able to use the parameters, the request has to be sent in <a href="https://developer.mozilla.org/en-US/docs/Web/API/Request/mode"><code>cors</code> mode</a> and has to support preflight request <code>OPTIONS</code>.</p>
-<h2>Store</h2>
-<h3>Mutations</h3>
-<h4>setSelectedGroupName</h4>
+<h2 id="store" tabindex="-1">Store</h2>
+<h3 id="mutations" tabindex="-1">Mutations</h3>
+<h4 id="setselectedgroupname" tabindex="-1">setSelectedGroupName</h4>
 <p>This can be used to change the selected search group by name.</p>
 <pre><code class="language-js">map.$store.commit(
   'plugin/addressSearch/setSelectedGroupName',
@@ -423,8 +423,8 @@ <h4>setSelectedGroupName</h4>
 )
 </code></pre>
 <p>Please mind that programmatically changing the search group will <em>not</em> trigger a search, unlike a search group change by the user. If you need a search after change, consider the <code>search</code> action.</p>
-<h3>Actions</h3>
-<h4>search</h4>
+<h3 id="actions" tabindex="-1">Actions</h3>
+<h4 id="search" tabindex="-1">search</h4>
 <p>This is a purely programmatical search method. It is not used by user input.</p>
 <pre><code class="language-js">map.$store.dispatch('plugin/addressSearch/search', {
   input: 'Bahnhofsstraße 12',
@@ -453,7 +453,7 @@ <h4>search</h4>
 </tr>
 </tbody>
 </table>
-<h3>State</h3>
+<h3 id="state" tabindex="-1">State</h3>
 <pre><code class="language-js">map.subscribe('plugin/addressSearch/chosenAddress', (chosenAddress) =&gt; {
   /* Your code. */
 })
diff --git a/docs/generic/plugin-attributions.html b/docs/generic/plugin-attributions.html
index 6070f2c20..3cad0ede3 100644
--- a/docs/generic/plugin-attributions.html
+++ b/docs/generic/plugin-attributions.html
@@ -22,11 +22,11 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Attributions</h1>
-<h2>Scope</h2>
+    <h1 id="attributions" tabindex="-1">Attributions</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>This plugin shows attributions (that is, legal information) regarding copyrights and sources of the currently visible layers.</p>
-<h2>Configuration</h2>
-<h3>attributions</h3>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
+<h3 id="attributions-1" tabindex="-1">attributions</h3>
 <p>All parameters are optional. However, setting neither <code>layerAttributions</code> nor <code>staticAttributions</code> results in an empty window.</p>
 <table>
 <thead>
@@ -70,7 +70,7 @@ <h3>attributions</h3>
 </tbody>
 </table>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/generic/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
-<h4>attributions.layerAttribution</h4>
+<h4 id="attributions.layerattribution" tabindex="-1">attributions.layerAttribution</h4>
 <table>
 <thead>
 <tr>
diff --git a/docs/generic/plugin-draw.html b/docs/generic/plugin-draw.html
index 7ebe889ab..45454a98a 100644
--- a/docs/generic/plugin-draw.html
+++ b/docs/generic/plugin-draw.html
@@ -22,8 +22,8 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Draw</h1>
-<h2>Scope</h2>
+    <h1 id="draw" tabindex="-1">Draw</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The draw plugin allows users to draw features on the map. Drawn features may be edited and deleted.</p>
 <p>Currently supported OpenLayers geometry types:</p>
 <ul>
@@ -33,15 +33,15 @@ <h2>Scope</h2>
 <li><code>'Polygon'</code></li>
 </ul>
 <p>Also, <code>'Text'</code> is supported which is modeled as an OpenLayers <code>'Point'</code>. This is no default feature, so it must be specified in the configuration to use it.</p>
-<h2>User instructions for Text Mode</h2>
+<h2 id="user-instructions-for-text-mode" tabindex="-1">User instructions for Text Mode</h2>
 <p>The interaction with text features is not intuitive, which is why the text feature should come with instructions for the users:</p>
-<h3>Edit</h3>
+<h3 id="edit" tabindex="-1">Edit</h3>
 <p>To edit the text or the placement of the text feature, the user must click on the center of the text to select the point geometry below it. After selecting it, the user can move the point by keeping the left mouse button pressed, or edit the text in the input field that opens with selecting the feature. If more than one text size is specified in the configuration, the user can change the text size with a slider.</p>
-<h3>Delete</h3>
+<h3 id="delete" tabindex="-1">Delete</h3>
 <p>To delete the text, the user must either click on the point at the center of the text or use CTRL + left mouse button to open a box over all features that he or she wants to delete.</p>
-<h2>Configuration</h2>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
 <p>The styling of the drawn features can be configured to overwrite the default ol-style. Configuration is oriented around the <a href="https://openlayers.org/en/latest/apidoc/module-ol_style_Style.html#~StyleLike">OpenLayers styles</a>.</p>
-<h3>draw</h3>
+<h3 id="draw-1" tabindex="-1">draw</h3>
 <table>
 <thead>
 <tr>
@@ -69,7 +69,7 @@ <h3>draw</h3>
 </tbody>
 </table>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/generic/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
-<h5>draw.textStyle</h5>
+<h5 id="draw.textstyle" tabindex="-1">draw.textStyle</h5>
 <table>
 <thead>
 <tr>
@@ -91,7 +91,7 @@ <h5>draw.textStyle</h5>
 </tr>
 </tbody>
 </table>
-<h5>draw.textStyle.font</h5>
+<h5 id="draw.textstyle.font" tabindex="-1">draw.textStyle.font</h5>
 <table>
 <thead>
 <tr>
@@ -113,7 +113,7 @@ <h5>draw.textStyle.font</h5>
 </tr>
 </tbody>
 </table>
-<h4>draw.style (by example)</h4>
+<h4 id="draw.style-(by-example)" tabindex="-1">draw.style (by example)</h4>
 <p>The <code>@masterportal/masterportalapi</code> has vectorStyles in development. As soon as that's done, we shall use its styling syntax and methods.</p>
 <p>For the time being, please use this example as a rough reference as to what can currently be done.</p>
 <pre><code class="language-json">{
@@ -141,14 +141,14 @@ <h4>draw.style (by example)</h4>
   }
 }
 </code></pre>
-<h2>Store</h2>
-<h3>State</h3>
+<h2 id="store" tabindex="-1">Store</h2>
+<h3 id="state" tabindex="-1">State</h3>
 <pre><code class="language-js">map.subscribe('plugin/draw/featureCollection', (featureCollection) =&gt; {
   /* Your code. */
 })
 </code></pre>
 <p>The returned featureCollection is a <a href="https://geojson.org/">GeoJSON</a> FeatureCollection. It includes all drawn features and updates on changes.</p>
-<h2>Actions</h2>
+<h2 id="actions" tabindex="-1">Actions</h2>
 <pre><code class="language-js">map.$store.dispatch('plugin/draw/addFeatures', {
   geoJSON: {
     type: 'FeatureCollection',
diff --git a/docs/generic/plugin-export.html b/docs/generic/plugin-export.html
index 26d494526..f512fc051 100644
--- a/docs/generic/plugin-export.html
+++ b/docs/generic/plugin-export.html
@@ -22,11 +22,11 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Export</h1>
-<h2>Scope</h2>
+    <h1 id="export" tabindex="-1">Export</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The Export plugin offers users to download the currently visible map canvas in a variety of file formats and by a variety of methods.</p>
-<h2>Configuration</h2>
-<h3>export</h3>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
+<h3 id="export-1" tabindex="-1">export</h3>
 <table>
 <thead>
 <tr>
@@ -60,12 +60,12 @@ <h3>export</h3>
 </table>
 <p>To remove user control, add <code>displayComponent: false</code> to the configuration and use the following interactions.</p>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/generic/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
-<h3>Actions</h3>
+<h3 id="actions" tabindex="-1">Actions</h3>
 <p>To programmatically trigger a &quot;screenshot&quot;, use this action.</p>
 <pre><code class="language-js">// type is 'Png', 'Jpg', or 'Pdf'
 map.$store.dispatch('plugin/export/exportAs', type)
 </code></pre>
-<h3>State</h3>
+<h3 id="state" tabindex="-1">State</h3>
 <p>This shows how a callback can be used to show the exported data in a suitable html element. The value of the <code>screenshot</code> variable is a base64-encoded string.</p>
 <pre><code class="language-js">const someElement = // ... however you retrieve your html element
   map.subscribe('plugin/export/exportedMap', (screenshot) =&gt;
diff --git a/docs/generic/plugin-filter.html b/docs/generic/plugin-filter.html
index 9139955d1..377fbc359 100644
--- a/docs/generic/plugin-filter.html
+++ b/docs/generic/plugin-filter.html
@@ -22,11 +22,11 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Filter</h1>
-<h2>Scope</h2>
+    <h1 id="filter" tabindex="-1">Filter</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The Filter plugin can be used to filter arbitrary configurable vector layers by their properties.</p>
-<h3>Configuration</h3>
-<h4>filter</h4>
+<h3 id="configuration" tabindex="-1">Configuration</h3>
+<h4 id="filter-1" tabindex="-1">filter</h4>
 <table>
 <thead>
 <tr>
@@ -46,7 +46,7 @@ <h4>filter</h4>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/generic/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
 <pre><code>The following chapters contain drafts in this format. Please mind that they neither represent UI nor localisation, but are merely there to communicate the idea with an example.
 </code></pre>
-<h5>filter.filterConfiguration</h5>
+<h5 id="filter.filterconfiguration" tabindex="-1">filter.filterConfiguration</h5>
 <table>
 <thead>
 <tr>
@@ -68,7 +68,7 @@ <h5>filter.filterConfiguration</h5>
 </tr>
 </tbody>
 </table>
-<h6>filter.filterConfiguration.category</h6>
+<h6 id="filter.filterconfiguration.category" tabindex="-1">filter.filterConfiguration.category</h6>
 <table>
 <thead>
 <tr>
@@ -101,7 +101,7 @@ <h6>filter.filterConfiguration.category</h6>
 ▢ Vanilla
 ▢ Strawberry
 </code></pre>
-<h6>filter.filterConfiguration.time</h6>
+<h6 id="filter.filterconfiguration.time" tabindex="-1">filter.filterConfiguration.time</h6>
 <table>
 <thead>
 <tr>
@@ -139,7 +139,7 @@ <h6>filter.filterConfiguration.time</h6>
 </tbody>
 </table>
 <p>Of all time restrictions, at most one can be selected at any time. The produced options are selectable by radio buttons.</p>
-<h6>filter.filterConfiguration.time.options</h6>
+<h6 id="filter.filterconfiguration.time.options" tabindex="-1">filter.filterConfiguration.time.options</h6>
 <table>
 <thead>
 <tr>
@@ -166,7 +166,7 @@ <h6>filter.filterConfiguration.time.options</h6>
 ◯ Last 7 days
 </code></pre>
 <p>In <code>'days'</code> mode, the selections will always include full days, and additionally the current day. Due to this, the time frame of &quot;last 7 days&quot; is actually 8*24h long. This seems unexpected at first, but follows intuition – if it's Monday and a user filters to the &quot;last seven days&quot;, they would expect to fully see last week's Monday, but also features from that day's morning.</p>
-<h6>filter.filterConfiguration.time.freeSelection</h6>
+<h6 id="filter.filterconfiguration.time.freeselection" tabindex="-1">filter.filterConfiguration.time.freeSelection</h6>
 <table>
 <thead>
 <tr>
@@ -193,7 +193,7 @@ <h6>filter.filterConfiguration.time.freeSelection</h6>
    From ▒▒▒▒▒▒▒▒▒▒▒ // clicking input opens a selector restricted *until* today
    To   ▇▇▇▇▇▇▇▇▇▇▇ // clicking input opens a selector restricted *until* today
 </code></pre>
-<h4>Example configuration</h4>
+<h4 id="example-configuration" tabindex="-1">Example configuration</h4>
 <pre><code class="language-js">{
   filter: {
     layers: {
diff --git a/docs/generic/plugin-fullscreen.html b/docs/generic/plugin-fullscreen.html
index 85ee34a52..3b6942d11 100644
--- a/docs/generic/plugin-fullscreen.html
+++ b/docs/generic/plugin-fullscreen.html
@@ -22,11 +22,11 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Fullscreen</h1>
-<h2>Scope</h2>
+    <h1 id="fullscreen" tabindex="-1">Fullscreen</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The fullscreen plugin allows viewing the map in fullscreen mode. It relies solely on the <a href="https://developer.mozilla.org/en-US/docs/Web/API/Fullscreen_API">HTML Fullscreen API</a>, where you can also find more about browser support.</p>
-<h2>Configuration</h2>
-<h3>fullscreen</h3>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
+<h3 id="fullscreen-1" tabindex="-1">fullscreen</h3>
 <table>
 <thead>
 <tr>
@@ -49,8 +49,8 @@ <h3>fullscreen</h3>
 </tbody>
 </table>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/generic/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
-<h2>Store</h2>
-<h3>State</h3>
+<h2 id="store" tabindex="-1">Store</h2>
+<h3 id="state" tabindex="-1">State</h3>
 <pre><code class="language-js">map.subscribe('plugin/fullscreen/isInFullscreen', (isInFullscreen) =&gt; {
   /* Your code. */
 })
diff --git a/docs/generic/plugin-geo-location.html b/docs/generic/plugin-geo-location.html
index 2772a21c3..145f3e1b3 100644
--- a/docs/generic/plugin-geo-location.html
+++ b/docs/generic/plugin-geo-location.html
@@ -22,13 +22,13 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>GeoLocation</h1>
-<h2>Scope</h2>
+    <h1 id="geolocation" tabindex="-1">GeoLocation</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The GeoLocation plugin is responsible for collecting and displaying a user's GPS location. It is shown as a crosshair mark on the map.
 The tracking can be triggered initially on startup or via a button. This behavior can be controlled by setting <code>checkLocationInitially</code> to
 either <code>true</code> or <code>false</code>. When a users denies the location tracking, the button for this plugin gets disabled.</p>
-<h2>Configuration</h2>
-<h4>geoLocation</h4>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
+<h4 id="geolocation-1" tabindex="-1">geoLocation</h4>
 <table>
 <thead>
 <tr>
@@ -81,7 +81,7 @@ <h4>geoLocation</h4>
 </tbody>
 </table>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/generic/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
-<h4>Example configuration</h4>
+<h4 id="example-configuration" tabindex="-1">Example configuration</h4>
 <pre><code class="language-json">{
   &quot;geoLocation&quot;: {
     &quot;checkLocationInitially&quot;: true,
@@ -89,8 +89,8 @@ <h4>Example configuration</h4>
   }
 }
 </code></pre>
-<h2>Store</h2>
-<h3>State</h3>
+<h2 id="store" tabindex="-1">Store</h2>
+<h3 id="state" tabindex="-1">State</h3>
 <p>If the access to an users location has been granted, the coordinates get stored in the <code>position</code> state value. This value can be subscribed through the path <code>'plugin/geoLocation/position'</code>.</p>
 <pre><code class="language-js">map.subscribe('plugin/geoLocation/position', (position) =&gt; {
   /* Your code here */
diff --git a/docs/generic/plugin-gfi.html b/docs/generic/plugin-gfi.html
index 9af21eb24..279c9cba8 100644
--- a/docs/generic/plugin-gfi.html
+++ b/docs/generic/plugin-gfi.html
@@ -22,14 +22,14 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>GFI</h1>
-<h2>Scope</h2>
+    <h1 id="gfi" tabindex="-1">GFI</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The GFI plugin can be used to fetch and optionally display GFI (GetFeatureInfo) from WMS and WFS services as well as layers based on GeoJSON files. In a first step, the information is stored in the VueX store to allow for easy access. Display is optional and quite obstructive within the map client.</p>
 <blockquote>
 <p>⚠️ The display feature is currently not meant for production. Please use data bindings for display to avoid obstructing the map client.</p>
 </blockquote>
-<h3>Configuration</h3>
-<h4>gfi</h4>
+<h3 id="configuration" tabindex="-1">Configuration</h3>
+<h4 id="gfi-1" tabindex="-1">gfi</h4>
 <table>
 <thead>
 <tr>
@@ -92,7 +92,7 @@ <h4>gfi</h4>
 </tbody>
 </table>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/generic/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
-<h5>gfi.gfiLayerConfiguration</h5>
+<h5 id="gfi.gfilayerconfiguration" tabindex="-1">gfi.gfiLayerConfiguration</h5>
 <table>
 <thead>
 <tr>
@@ -156,7 +156,7 @@ <h5>gfi.gfiLayerConfiguration</h5>
 </tr>
 </tbody>
 </table>
-<h5>gfi.customHighlightStyle</h5>
+<h5 id="gfi.customhighlightstyle" tabindex="-1">gfi.customHighlightStyle</h5>
 <table>
 <thead>
 <tr>
@@ -178,7 +178,7 @@ <h5>gfi.customHighlightStyle</h5>
 </tr>
 </tbody>
 </table>
-<h5>gfi.featureList</h5>
+<h5 id="gfi.featurelist" tabindex="-1">gfi.featureList</h5>
 <table>
 <thead>
 <tr>
@@ -210,7 +210,7 @@ <h5>gfi.featureList</h5>
 </tr>
 </tbody>
 </table>
-<h4>Example configuration</h4>
+<h4 id="example-configuration" tabindex="-1">Example configuration</h4>
 <pre><code class="language-js">layers: {
   [serviceId]: {
     geometry: true,
@@ -235,8 +235,8 @@ <h4>Example configuration</h4>
   },
 },
 </code></pre>
-<h2>Store</h2>
-<h3>State</h3>
+<h2 id="store" tabindex="-1">Store</h2>
+<h3 id="state" tabindex="-1">State</h3>
 <p>If a successful query has been sent and a response has been received, the result will be saved in the store and can be subscribed through the path <code>'plugin/gfi/featureInformation'</code>. If, however, a query for a layer fails, a <code>Symbol</code> containing the error will be saved in the store instead to indicate the error.</p>
 <p>The exact value of <code>featureInformation</code> may vary wildly depending on the service used, but is always given as json representation here.</p>
 <pre><code class="language-js">map.subscribe('plugin/gfi/featureInformation', (featureInformation) =&gt; {
diff --git a/docs/generic/plugin-icon-menu.html b/docs/generic/plugin-icon-menu.html
index 48d26d425..70ddaa121 100644
--- a/docs/generic/plugin-icon-menu.html
+++ b/docs/generic/plugin-icon-menu.html
@@ -22,13 +22,13 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>IconMenu</h1>
+    <h1 id="iconmenu" tabindex="-1">IconMenu</h1>
 <p>The IconMenu offers an icon-button based menu to open various functionality as cards. This way, obstructive UI can be hidden until the user desires to open it. Please use carefully – users may have issues finding process-relevant buttons/interactions if you hide them here.<br>
 Currently, the IconMenu should only be rendered with <code>layoutTag</code> set to <code>NineLayoutTag.TOP_RIGHT</code>.</p>
-<h2>Scope</h2>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>It is meant for additional information/functionality (legend, other layers) or power users in non-public clients.</p>
 <p><em>Please note that the average user has never seen the client before and just wants to get done with it, not learn a map client.</em></p>
-<h2>Configuration</h2>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
 <blockquote>
 <p>⚠️ This plugin can't be configured with the <code>mapConfiguration</code>, but is configured during client construction. Currently, no way exists to add plugins to it after the build took place.</p>
 </blockquote>
@@ -60,7 +60,7 @@ <h2>Configuration</h2>
   ],
 }
 </code></pre>
-<h3>menus</h3>
+<h3 id="menus" tabindex="-1">menus</h3>
 <p>When landscape mode is active the IconMenu is oriented horizontally. Currently, the IconMenu works fine only if there is not more than one row of Icons in landscape mode.</p>
 
     
diff --git a/docs/generic/plugin-layer-chooser.html b/docs/generic/plugin-layer-chooser.html
index c4f4d3f85..b1ab07470 100644
--- a/docs/generic/plugin-layer-chooser.html
+++ b/docs/generic/plugin-layer-chooser.html
@@ -22,12 +22,12 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>LayerChooser</h1>
+    <h1 id="layerchooser" tabindex="-1">LayerChooser</h1>
 <p>The tool offers layer selection to the user.</p>
-<h2>Scope</h2>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The LayerChooser offers an additive (usually Overlays, technically named with <code>type: 'mask'</code>) and an exclusive (usually background maps, <code>type: 'background'</code>) selection of layers to the users.</p>
 <p>Order of layers within a layer is currently always as initially configured.</p>
-<h2>Configuration</h2>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
 <p>The tool does not require any configuration for itself, but is based on the <code>mapConfiguration.layers</code> array. It will infer its options from there, and change layer visibility and availability depending on <code>minZoom</code> and <code>maxZoom</code>.</p>
 <p>Each object in <code>mapConfiguration.layers</code> array fits this definition:</p>
 <table>
@@ -82,7 +82,7 @@ <h2>Configuration</h2>
 </tbody>
 </table>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/generic/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
-<h3>mapConfiguration.layers.options</h3>
+<h3 id="mapconfiguration.layers.options" tabindex="-1">mapConfiguration.layers.options</h3>
 <p>An option wheel will appear in the layer chooser that allows opening a sub-menu with configured configuration options for the end user.</p>
 <table>
 <thead>
@@ -100,7 +100,7 @@ <h3>mapConfiguration.layers.options</h3>
 </tr>
 </tbody>
 </table>
-<h4>mapConfiguration.layers.options.layers</h4>
+<h4 id="mapconfiguration.layers.options.layers" tabindex="-1">mapConfiguration.layers.options.layers</h4>
 <p>This field is named like this to match the OGC specification for their name; that is, layers have layers that may have layers that may have layers, and so on. However, only the first level (a layer's layers) is currently implemented.</p>
 <table>
 <thead>
diff --git a/docs/generic/plugin-legend.html b/docs/generic/plugin-legend.html
index f4511efae..9af96bdc1 100644
--- a/docs/generic/plugin-legend.html
+++ b/docs/generic/plugin-legend.html
@@ -22,9 +22,9 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Legend</h1>
+    <h1 id="legend" tabindex="-1">Legend</h1>
 <p>The Legend module offers legend images as supplied by OGC services.</p>
-<h2>Configuration</h2>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/generic/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
 
     
diff --git a/docs/generic/plugin-loading-indicator.html b/docs/generic/plugin-loading-indicator.html
index eb0396786..a0d432e67 100644
--- a/docs/generic/plugin-loading-indicator.html
+++ b/docs/generic/plugin-loading-indicator.html
@@ -22,13 +22,13 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>LoadingIndicator</h1>
-<h2>Scope</h2>
+    <h1 id="loadingindicator" tabindex="-1">LoadingIndicator</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>A generic loading indicator that may be used by any plugin or outside procedure to indicate loading.</p>
-<h2>Configuration</h2>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/generic/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
-<h2>Store</h2>
-<h3>Mutations</h3>
+<h2 id="store" tabindex="-1">Store</h2>
+<h3 id="mutations" tabindex="-1">Mutations</h3>
 <pre><code class="language-js">// show loading indicator
 map.$store.commit('plugin/loadingIndicator/addLoadingKey', key)
 // hide loading indicator
@@ -37,7 +37,7 @@ <h3>Mutations</h3>
 <p><img src="./readme_loadingIndicator_example.png" alt="Loading indicator example"></p>
 <p>The key must be unique and is kept track of via a Set. It can't be added multiple times, and removing it once always removes it altogether. It is advised to use a key like <code>{my-plugin-or-application-name}-{procedure-name}</code> to avoid name conflicts. The LoadingIndicator will usually be used for asynchronous code.</p>
 <p>As such, <strong>always call <code>removeLoadingKey</code> in the <code>finally</code> section of your code</strong> to prevent hanging loading indicators.</p>
-<h3>Getters</h3>
+<h3 id="getters" tabindex="-1">Getters</h3>
 <p>You may desire to listen to whether the loader is currently being shown.</p>
 <table>
 <thead>
diff --git a/docs/generic/plugin-pins.html b/docs/generic/plugin-pins.html
index 1985b16de..2c36045af 100644
--- a/docs/generic/plugin-pins.html
+++ b/docs/generic/plugin-pins.html
@@ -22,12 +22,12 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Pins</h1>
-<h2>Scope</h2>
+    <h1 id="pins" tabindex="-1">Pins</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The pins plugin handles marking locations. Embedding processes can then use that coordinate for further steps. The plugin may react to other plugins, especially address searches.</p>
-<h2>Configuration</h2>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
 <p>The usage of <code>displayComponent</code> has no influence on the creation of Pins on the Map if this plugin is being used.</p>
-<h3>pins</h3>
+<h3 id="pins-1" tabindex="-1">pins</h3>
 <table>
 <thead>
 <tr>
@@ -84,7 +84,7 @@ <h3>pins</h3>
 </tr>
 </tbody>
 </table>
-<h4>pins.appearOnClick</h4>
+<h4 id="pins.appearonclick" tabindex="-1">pins.appearOnClick</h4>
 <table>
 <thead>
 <tr>
@@ -106,7 +106,7 @@ <h4>pins.appearOnClick</h4>
 </tr>
 </tbody>
 </table>
-<h4>pins.initial</h4>
+<h4 id="pins.initial" tabindex="-1">pins.initial</h4>
 <table>
 <thead>
 <tr>
@@ -133,7 +133,7 @@ <h4>pins.initial</h4>
 </tr>
 </tbody>
 </table>
-<h4>pins.style</h4>
+<h4 id="pins.style" tabindex="-1">pins.style</h4>
 <table>
 <thead>
 <tr>
@@ -155,8 +155,8 @@ <h4>pins.style</h4>
 </tr>
 </tbody>
 </table>
-<h2>Store</h2>
-<h3>State</h3>
+<h2 id="store" tabindex="-1">Store</h2>
+<h3 id="state" tabindex="-1">State</h3>
 <pre><code class="language-js">map.subscribe('plugin/pins/transformedCoordinate', (pinCoordinate) =&gt; {
   /* Your Code. */
 })
diff --git a/docs/generic/plugin-reverse-geocoder.html b/docs/generic/plugin-reverse-geocoder.html
index ba1db2ce2..855c2e77a 100644
--- a/docs/generic/plugin-reverse-geocoder.html
+++ b/docs/generic/plugin-reverse-geocoder.html
@@ -22,12 +22,12 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Reverse Geocoder</h1>
-<h2>Scope</h2>
+    <h1 id="reverse-geocoder" tabindex="-1">Reverse Geocoder</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>Reverse Geocoder Plugin that turns coordinates into addresses via a WPS. It does not offer any UI by itself.</p>
 <p>This module has been written for the HH WPS service. The return format is custom and no other WPS are currently supported. Please mind this when trying to use this plugin with any other WPS. For usage with other WPS, those must either fit the HH WPS, or a generalization of this plugin is required.</p>
-<h2>Configuration</h2>
-<h3>reverseGeocoder</h3>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
+<h3 id="reversegeocoder" tabindex="-1">reverseGeocoder</h3>
 <table>
 <thead>
 <tr>
@@ -69,9 +69,9 @@ <h3>reverseGeocoder</h3>
 </tr>
 </tbody>
 </table>
-<h2>Store</h2>
+<h2 id="store" tabindex="-1">Store</h2>
 <p>The ReverseGeocoder plugin does not hold any state.</p>
-<h3>Actions</h3>
+<h3 id="actions" tabindex="-1">Actions</h3>
 <pre><code class="language-js">// result contains the resolved address (exact format depends on WPS)
 const result = await map.$store.dispatch(
   'plugin/reverseGeocoder/reverseGeocode',
diff --git a/docs/generic/plugin-scale.html b/docs/generic/plugin-scale.html
index e671f8429..f5ac165df 100644
--- a/docs/generic/plugin-scale.html
+++ b/docs/generic/plugin-scale.html
@@ -22,14 +22,14 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Scale</h1>
+    <h1 id="scale" tabindex="-1">Scale</h1>
 <blockquote>
 <p>⚠ The Scale plugin is currently meant for passive usage only. It's API has not yet been finally defined, and is subject to change without further notice.</p>
 </blockquote>
-<h2>Scope</h2>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The scale plugin shows the current map resolution as relative scale (1:x) and/or absolute scale (a drawn line has length x units).</p>
-<h2>Configuration</h2>
-<h3>scale</h3>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
+<h3 id="scale-1" tabindex="-1">scale</h3>
 <table>
 <thead>
 <tr>
diff --git a/docs/generic/plugin-toast.html b/docs/generic/plugin-toast.html
index b3dcc0732..135b35011 100644
--- a/docs/generic/plugin-toast.html
+++ b/docs/generic/plugin-toast.html
@@ -22,12 +22,12 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Toast</h1>
-<h2>Scope</h2>
+    <h1 id="toast" tabindex="-1">Toast</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The toast plugin offers global functionality to display text messages to the user. These are the classic success, warning, info, and error messages, helping to understand what's going on or why something happened.</p>
-<h2>Configuration</h2>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
 <p>Please check the vuetify documentation to override the success, warning, info, or errors colors in general. To affect only this plugin, the following configuration parameters can be added to either the plugin instantiation or the mapConfiguration:</p>
-<h3>toast</h3>
+<h3 id="toast-1" tabindex="-1">toast</h3>
 <table>
 <thead>
 <tr>
@@ -60,7 +60,7 @@ <h3>toast</h3>
 </tbody>
 </table>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/generic/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
-<h4>toast.toastStyle</h4>
+<h4 id="toast.toaststyle" tabindex="-1">toast.toastStyle</h4>
 <table>
 <thead>
 <tr>
@@ -82,12 +82,12 @@ <h4>toast.toastStyle</h4>
 </tr>
 </tbody>
 </table>
-<h2>Store</h2>
-<h3>Actions</h3>
+<h2 id="store" tabindex="-1">Store</h2>
+<h3 id="actions" tabindex="-1">Actions</h3>
 <p>New entries are made via action. They are either dismissed after a timeout or by user interaction.</p>
 <pre><code class="language-js">map.$store.dispatch('plugin/toast/addToast', payload)
 </code></pre>
-<h4>Payload structure</h4>
+<h4 id="payload-structure" tabindex="-1">Payload structure</h4>
 <table>
 <thead>
 <tr>
@@ -124,7 +124,7 @@ <h4>Payload structure</h4>
 </tr>
 </tbody>
 </table>
-<h4>Usage example</h4>
+<h4 id="usage-example" tabindex="-1">Usage example</h4>
 <pre><code class="language-js">map.$store.dispatch('plugin/toast/addToast', {
   type: 'warning',
   text: 'Wrong hammer for screw.',
diff --git a/docs/generic/plugin-zoom.html b/docs/generic/plugin-zoom.html
index 31a453618..28eaf436d 100644
--- a/docs/generic/plugin-zoom.html
+++ b/docs/generic/plugin-zoom.html
@@ -22,10 +22,10 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Zoom</h1>
-<h2>Scope</h2>
+    <h1 id="zoom" tabindex="-1">Zoom</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The Zoom plugin offers functionality regarding map zooming.</p>
-<h2>Configuration</h2>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
 <p>The Zoom plugin offers a plus/minus button, and will adjust itself to the map's zoom settings on initialization.<br>
 It can be configured as followed.</p>
 <table>
@@ -55,8 +55,8 @@ <h2>Configuration</h2>
 </tbody>
 </table>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/generic/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
-<h2>Store</h2>
-<h3>State</h3>
+<h2 id="store" tabindex="-1">Store</h2>
+<h3 id="state" tabindex="-1">State</h3>
 <p>The map's zoom level can be listened to.</p>
 <table>
 <thead>
@@ -88,7 +88,7 @@ <h3>State</h3>
   /* This code is called on any zoomLevel update. */
 })
 </code></pre>
-<h3>Getters</h3>
+<h3 id="getters" tabindex="-1">Getters</h3>
 <table>
 <thead>
 <tr>
@@ -117,7 +117,7 @@ <h3>Getters</h3>
   }
 )
 </code></pre>
-<h3>Actions</h3>
+<h3 id="actions" tabindex="-1">Actions</h3>
 <p>The zoomLevel can be set programmatically.</p>
 <pre><code class="language-js">map.$store.dispatch('plugin/zoom/setZoomLevel', zoomLevelNumber)
 map.$store.dispatch('plugin/zoom/increaseZoomLevel')
diff --git a/docs/meldemichel/client-meldemichel.html b/docs/meldemichel/client-meldemichel.html
index 8eec41625..e96ddc4d2 100644
--- a/docs/meldemichel/client-meldemichel.html
+++ b/docs/meldemichel/client-meldemichel.html
@@ -22,11 +22,11 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Meldemichel MapClient API 🗺️ <code>@polar/client-meldemichel</code></h1>
+    <h1 id="meldemichel-mapclient-api-%F0%9F%97%BA%EF%B8%8F-%40polar%2Fclient-meldemichel" tabindex="-1">Meldemichel MapClient API 🗺️ <code>@polar/client-meldemichel</code></h1>
 <p>This client is based on <a href="https://github.com/Dataport/polar">POLAR</a> and subsequently the <a href="https://bitbucket.org/geowerkstatt-hamburg/masterportalapi/src/master/">masterportalAPI</a>. The following documentation only contains how this specific client can be used, and the minimal information required to get it running.</p>
 
 <p>For the development test deployments, <a href="./example/index.html">see here</a>.</p>
-<h2>Basic usage</h2>
+<h2 id="basic-usage" tabindex="-1">Basic usage</h2>
 <p>The NPM package <code>@polar/client-meldemichel</code> can be installed via NPM or downloaded from the <a href="https://github.com/Dataport/polar/releases">release page</a>. When using <code>import mapClient from '@polar/client-meldemichel'</code>, the object <code>mapClient</code> contains a method <code>createMap</code>. This is the main method required to get the client up and running. Should you use another import method, check the package's <code>dist</code> folder for available files.</p>
 <p>The method expects a single object with the following parameters.</p>
 <table>
@@ -76,11 +76,11 @@ <h2>Basic usage</h2>
 </code></pre>
 <p>The value to <code>stylePath</code> is the same as as a <code>link</code> tag would have in its <code>href</code>.</p>
 <p>The <code>index.html</code> is used in <code>COMPLETE</code> mode, which is not run in the AfM. You may, however, use it for testing or inspecting an example.</p>
-<h3>Instance reuse</h3>
+<h3 id="instance-reuse" tabindex="-1">Instance reuse</h3>
 <p>The <code>mapInstance</code> and its HTML environment are kept in the client; it is returned and rerendered on subsequent <code>createMap</code> calls to a div with the given <code>id</code>. Due to this, everything will appear to the user as it was previously left, including opened menus.</p>
 <p>Since in <code>SINGLE</code> mode, changes to the pins are required between renders, hence the parameters in <code>configOverride.pins</code> are used to update the client. Should additional updates be required, please let us know.</p>
 <p>Calling <code>watch</code>/<code>subscribe</code> on the client will return an <code>unwatch</code>/<code>unsubscribe</code> method. It should be called on leaving the map's page; depending on framework/library in e.g. the <code>beforeDestroy</code> or <code>beforeUnmount</code> method.</p>
-<h2>Rendering in SINGLE or REPORT mode</h2>
+<h2 id="rendering-in-single-or-report-mode" tabindex="-1">Rendering in SINGLE or REPORT mode</h2>
 <p>A document rendering the map client could e.g. look like this:</p>
 <pre><code class="language-html">&lt;!DOCTYPE html&gt;
 &lt;html&gt;
@@ -167,7 +167,7 @@ <h2>Rendering in SINGLE or REPORT mode</h2>
   &lt;/body&gt;
 &lt;/html&gt;
 </code></pre>
-<h2>Rendering COMPLETE mode</h2>
+<h2 id="rendering-complete-mode" tabindex="-1">Rendering COMPLETE mode</h2>
 <p>The <code>index.html</code> included in the package's <code>dist</code> folder has been prepared for this mode and must merely be hosted.</p>
 <p>Please see the table in chapter <code>Basic usage</code> about configuration options.</p>
 
diff --git a/docs/meldemichel/core.html b/docs/meldemichel/core.html
index 30ed9bbdf..aa70cc755 100644
--- a/docs/meldemichel/core.html
+++ b/docs/meldemichel/core.html
@@ -22,8 +22,8 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Core</h1>
-<h2>Scope</h2>
+    <h1 id="core" tabindex="-1">Core</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The client's core is the base package to create clients in the POLAR environment.</p>
 <p>It offers this functionality:</p>
 <ul>
@@ -31,15 +31,15 @@ <h2>Scope</h2>
 <li>@masterportal/masterportalapi functionality</li>
 <li>Localization mechanism</li>
 </ul>
-<h2>Interaction</h2>
+<h2 id="interaction" tabindex="-1">Interaction</h2>
 <p>If a client is rendered as part of another page, the zoom and drag-pan behaviour is different to if the client is rendered as complete page.<br>
 If it's part of another page, drag-panning on mobile devices is only usable if at least two fingers are being used while on desktop clients the user can only zoom if using the respective platform modifier key (e.g. CTRL).</p>
 <p>It is important to note that the behaviour will be desktop-like on larger touchscreen devices (e.g. tablets).</p>
-<h2>Initialization / Configuration</h2>
+<h2 id="initialization-%2F-configuration" tabindex="-1">Initialization / Configuration</h2>
 <p>It depends on the client how exactly the initialization will take place for the embedding programmer. However, the core mechanism remains the same.</p>
 <p>The exported default object is an extended masterportalAPI, adding the <code>addPlugins</code> and extending the <code>createMap</code> functions. For masterportalAPI details, <a href="https://bitbucket.org/geowerkstatt-hamburg/masterportalapi/src/master/">see their repository</a>.</p>
 <p>To be able to see the map in production mode, the imported stylesheet has to have the property <code>data-polar</code>. The value can be chosen arbitrarily. ⚠️ Deprecated. The new field 'stylePath' should be used instead.</p>
-<h3>addPlugins</h3>
+<h3 id="addplugins" tabindex="-1">addPlugins</h3>
 <p>Before instantiating the map, all required plugins have to be added. Depending on how you use POLAR, this may already have been done. Ready-made clients (that is, packages prefixed <code>@polar/client-</code>) come with plugins prepared. You may add further plugins or proceed with <code>createMap</code>.</p>
 <p>In case you're integrating new plugins, call <code>addPlugins</code> with an array of instances.</p>
 <pre><code class="language-js">client.addPlugins([Plugin({ pluginConfig })])
@@ -55,7 +55,7 @@ <h3>addPlugins</h3>
   })
 </code></pre>
 <p>If the storeModule features a <code>setupModule</code> action, it will be executed automatically after initialization.</p>
-<h3>createMap</h3>
+<h3 id="createmap" tabindex="-1">createMap</h3>
 <p>The map is created by calling the <code>createMap</code> method. Depending on how you use POLAR, this may already have been done, as some clients come as ready-made standalone HTML pages that do this for you.</p>
 <pre><code class="language-js">MapClient.createMap({
   // arbitrary id, must point to a div
@@ -66,7 +66,7 @@ <h3>createMap</h3>
   /* Your Code, e.g. for setting up callbacks. */
 })
 </code></pre>
-<h4>mapConfiguration</h4>
+<h4 id="mapconfiguration" tabindex="-1">mapConfiguration</h4>
 <p>The mapConfiguration allows controlling many client instance details.</p>
 <table>
 <thead>
@@ -124,7 +124,7 @@ <h4>mapConfiguration</h4>
 </tr>
 </tbody>
 </table>
-<h5>mapConfiguration.LanguageOption</h5>
+<h5 id="mapconfiguration.languageoption" tabindex="-1">mapConfiguration.LanguageOption</h5>
 <p>A language option is an object consisting of a type (its language key) and the i18next resource definition. You may e.g. decide that the texts offered in the LayerChooser do not fit the style of your client, or that they could be more precise in your situation since you're only using <em>very specific</em> overlays.</p>
 <p>An example for a LanguageOption array usable in <code>createMap</code> is this array:</p>
 <pre><code class="language-ts">const languageOptions: LanguageOption[] = [
@@ -151,7 +151,7 @@ <h5>mapConfiguration.LanguageOption</h5>
 ]
 </code></pre>
 <p>To figure out the name of the locales to override, inspect the matching plugin in GitHub's file browser. In <code>packages/plugins</code>, open the plugin you desire to override. Each plugin's <code>src</code> folder contains a <code>language.ts</code> listing all used locale keys with appropriate nesting.</p>
-<h5>mapConfiguration.extendedMasterportalapiMarkers</h5>
+<h5 id="mapconfiguration.extendedmasterportalapimarkers" tabindex="-1">mapConfiguration.extendedMasterportalapiMarkers</h5>
 <table>
 <thead>
 <tr>
@@ -193,7 +193,7 @@ <h5>mapConfiguration.extendedMasterportalapiMarkers</h5>
 </tr>
 </tbody>
 </table>
-<h6>mapConfiguration.extendedMasterportalapiMarkers.MarkerStyle</h6>
+<h6 id="mapconfiguration.extendedmasterportalapimarkers.markerstyle" tabindex="-1">mapConfiguration.extendedMasterportalapiMarkers.MarkerStyle</h6>
 <table>
 <thead>
 <tr>
@@ -281,7 +281,7 @@ <h6>mapConfiguration.extendedMasterportalapiMarkers.MarkerStyle</h6>
 </tbody>
 </table>
 </blockquote>
-<h5>mapConfiguration.LayerConf</h5>
+<h5 id="mapconfiguration.layerconf" tabindex="-1">mapConfiguration.LayerConf</h5>
 <p>The layer configuration (or: service register) is read by the masterportalAPI. The full definition can be read <a href="https://bitbucket.org/geowerkstatt-hamburg/masterportal/src/dev/doc/services.json.md">here</a>.</p>
 <p>However, not all listed services have been implemented in the masterportalAPI yet, and no documentation regarding implemented properties exists there yet.</p>
 <p>Whitelisted and confirmed parameters include:</p>
@@ -289,7 +289,7 @@ <h5>mapConfiguration.LayerConf</h5>
 <li>WMS: id, name, url, typ, format, version, transparent, layers, STYLES</li>
 <li>WFS: id, name, url, typ, outputFormat, version, featureType</li>
 </ul>
-<h6>Example services register</h6>
+<h6 id="example-services-register" tabindex="-1">Example services register</h6>
 <pre><code class="language-json">[
   {
     &quot;id&quot;: &quot;my-wfs-id&quot;,
@@ -313,7 +313,7 @@ <h6>Example services register</h6>
 ]
 </code></pre>
 <p>Since this is the base for many functions, the service ID set in this is used to reference map material in many places of the map client.</p>
-<h5>&lt;...masterportalAPI.fields&gt;</h5>
+<h5 id="%3C...masterportalapi.fields%3E" tabindex="-1">&lt;...masterportalAPI.fields&gt;</h5>
 <p>The <code>&lt;...masterportalAPI.fields&gt;</code> means that any masterportalAPI field may also be used here <em>directly</em>. The most common fields are the following ones; for more, see masterportalAPI.</p>
 <table>
 <thead>
@@ -356,10 +356,10 @@ <h5>&lt;...masterportalAPI.fields&gt;</h5>
 </tr>
 </tbody>
 </table>
-<h5>&lt;plugin.fields&gt;</h5>
-<p>Plugins in POLAR are modular components that extend the functionality of the map client. They can be added using the <a href="#addPlugins">addPlugins</a> method and configured through the <code>mapConfiguration</code> object. Each plugin has its own set of fields and options that can be customized.</p>
+<h5 id="%3Cplugin.fields%3E" tabindex="-1">&lt;plugin.fields&gt;</h5>
+<p>Plugins in POLAR are modular components that extend the functionality of the map client. They can be added using the <a href="#addplugins">addPlugins</a> method and configured through the <code>mapConfiguration</code> object. Each plugin has its own set of fields and options that can be customized.</p>
 <p>On how to configure a plugin, see the respective plugin. The configuration is given in the <code>mapConfiguration</code> object by the plugin's name as specified in its respective documentation.</p>
-<h6>Global Plugin Parameters</h6>
+<h6 id="global-plugin-parameters" tabindex="-1">Global Plugin Parameters</h6>
 <p>Most plugins honor this additional field.</p>
 <table>
 <thead>
@@ -377,7 +377,7 @@ <h6>Global Plugin Parameters</h6>
 </tr>
 </tbody>
 </table>
-<h6>Example Configuration</h6>
+<h6 id="example-configuration" tabindex="-1">Example Configuration</h6>
 <p>For example, a <code>@polar/plugin-address-search</code> plugin can be configured like this:</p>
 <pre><code class="language-js">{
   addressSearch: {
@@ -387,7 +387,7 @@ <h6>Example Configuration</h6>
   }
 }
 </code></pre>
-<h5>mapConfiguration.vuetify</h5>
+<h5 id="mapconfiguration.vuetify" tabindex="-1">mapConfiguration.vuetify</h5>
 <p>These fields let you e.g. specify a <a href="https://vuetifyjs.com/en/features/theme/">Vuetify-Theme</a>. For more options, refer to the official vuetify documentation.</p>
 <p>Additionally to the regular fields, <code>primaryContrast</code> and <code>secondaryContrast</code> are interpreted. They serve as contrast colors to their respective fields and are used for e.g. button icons.</p>
 <pre><code class="language-js">{
@@ -403,7 +403,7 @@ <h5>mapConfiguration.vuetify</h5>
   }
 }
 </code></pre>
-<h2>Store</h2>
+<h2 id="store" tabindex="-1">Store</h2>
 <p>The core module features a vuex root store that all plugin vuex modules are plugged into. However, the root contents are only relevant to plugins. It is accessible with <code>map.$store</code>, and can be used as a starting point for plugin access.</p>
 <p>To ease use, the map instance also features a <code>subscribe</code> method that will register a watcher to any state field. Please mind that only documented paths should be used, and all others are subject to change without notice.</p>
 <pre><code class="language-js">// state subscription – listening to data held by the map client
diff --git a/docs/meldemichel/lib-custom-types.html b/docs/meldemichel/lib-custom-types.html
index fc8188e5f..775c6e0a3 100644
--- a/docs/meldemichel/lib-custom-types.html
+++ b/docs/meldemichel/lib-custom-types.html
@@ -22,7 +22,7 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Custom Types</h1>
+    <h1 id="custom-types" tabindex="-1">Custom Types</h1>
 <p>This is a custom type library for overarching types. They can be used both in core, plugin, and lib packages to develop a common custom package-global type system.</p>
 <p>Keep it as small as possible and sort types where they belong, whenever possible.</p>
 
diff --git a/docs/meldemichel/lib-invisible-style.html b/docs/meldemichel/lib-invisible-style.html
index a82796a9e..9f2713f2e 100644
--- a/docs/meldemichel/lib-invisible-style.html
+++ b/docs/meldemichel/lib-invisible-style.html
@@ -22,7 +22,7 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>invisibleStyle</h1>
+    <h1 id="invisiblestyle" tabindex="-1">invisibleStyle</h1>
 <p>Exports a style for vector layer features that results in invisibility. Plugins that work with feature visibility ought to use this package to keep them interoperable.</p>
 <pre><code class="language-js">import { InvisibleStyle, isInvisible, isVisible } from '@polar/lib-invisible-style'
 
diff --git a/docs/meldemichel/plugin-address-search.html b/docs/meldemichel/plugin-address-search.html
index 089a333e5..4376accb0 100644
--- a/docs/meldemichel/plugin-address-search.html
+++ b/docs/meldemichel/plugin-address-search.html
@@ -22,8 +22,8 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>AddressSearch</h1>
-<h2>Scope</h2>
+    <h1 id="addresssearch" tabindex="-1">AddressSearch</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The AddressSearch plugin allows users to search for an address. If multiple addresses are returned by services, the user is prompted to select a result.</p>
 <p>The plugin saves the chosen information as GeoJSON to the store so that following procedures may grab it or so that other plugins may use it.</p>
 <p>Currently supported services:</p>
@@ -32,8 +32,8 @@ <h2>Scope</h2>
 <li>WFS</li>
 <li>Some gazetteers/WFS-G (please request a check or try yourself, not 100% done)</li>
 </ul>
-<h2>Configuration</h2>
-<h3>addressSearch</h3>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
+<h3 id="addresssearch-1" tabindex="-1">addressSearch</h3>
 <p>The configuration allows defining and grouping services. Grouped services can be requested in a search at the same time, and one group of searches can be active at a time. When multiple searches are in a group, they may be extended with category information to make the results easier to browse.</p>
 <p>It is advised to either use one-search-per-group <em>or</em> all services in a singular group to avoid an overly complex UI. Mixed configurations may be required for more complex search requirements.</p>
 <p>In <code>categoryProperties</code> and <code>groupProperties</code>, id strings called <code>groupId</code> and <code>categoryId</code> are used. These are arbitrary strings you can introduce and reuse to group or categorize elements together. Regarding what groups and categories are, see further below.</p>
@@ -104,7 +104,7 @@ <h3>addressSearch</h3>
 </tbody>
 </table>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/meldemichel/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
-<h4>addressSearch.searchMethodsObject</h4>
+<h4 id="addresssearch.searchmethodsobject" tabindex="-1">addressSearch.searchMethodsObject</h4>
 <table>
 <thead>
 <tr>
@@ -156,7 +156,7 @@ <h4>addressSearch.searchMethodsObject</h4>
 </tr>
 </tbody>
 </table>
-<h4>addressSearch.customSearchMethod</h4>
+<h4 id="addresssearch.customsearchmethod" tabindex="-1">addressSearch.customSearchMethod</h4>
 <p>This is a function with the following signature:</p>
 <pre><code>(
   // should be used to actually abort request
@@ -170,7 +170,7 @@ <h4>addressSearch.customSearchMethod</h4>
 ) =&gt; Promise&lt;FeatureCollection&gt; | never
 </code></pre>
 <p>With this, arbitrary services can be supported.</p>
-<h4>addressSearch.customSelectFunction</h4>
+<h4 id="addresssearch.customselectfunction" tabindex="-1">addressSearch.customSelectFunction</h4>
 <p>This is a function with the following signature:</p>
 <pre><code>({
   // VueX context object
@@ -182,7 +182,7 @@ <h4>addressSearch.customSelectFunction</h4>
 }) =&gt; void
 </code></pre>
 <p>With this, arbitrary click results can be supported. Please mind that undocumented mutations and actions fired in such a function are subject to change without further notice.</p>
-<h4>addressSearch.groupProperties</h4>
+<h4 id="addresssearch.groupproperties" tabindex="-1">addressSearch.groupProperties</h4>
 <table>
 <thead>
 <tr>
@@ -219,7 +219,7 @@ <h4>addressSearch.groupProperties</h4>
 </tr>
 </tbody>
 </table>
-<h4>addressSearch.categoryProperties</h4>
+<h4 id="addresssearch.categoryproperties" tabindex="-1">addressSearch.categoryProperties</h4>
 <table>
 <thead>
 <tr>
@@ -236,7 +236,7 @@ <h4>addressSearch.categoryProperties</h4>
 </tr>
 </tbody>
 </table>
-<h5>addressSearch.searchMethodsObject.queryParameters (type:common)</h5>
+<h5 id="addresssearch.searchmethodsobject.queryparameters-(type%3Acommon)" tabindex="-1">addressSearch.searchMethodsObject.queryParameters (type:common)</h5>
 <p>These fields are interpreted by all implemented services.</p>
 <table>
 <thead>
@@ -254,7 +254,7 @@ <h5>addressSearch.searchMethodsObject.queryParameters (type:common)</h5>
 </tr>
 </tbody>
 </table>
-<h5>addressSearch.searchMethodsObject.queryParameters (type:wfs)</h5>
+<h5 id="addresssearch.searchmethodsobject.queryparameters-(type%3Awfs)" tabindex="-1">addressSearch.searchMethodsObject.queryParameters (type:wfs)</h5>
 <table>
 <thead>
 <tr>
@@ -317,7 +317,7 @@ <h5>addressSearch.searchMethodsObject.queryParameters (type:wfs)</h5>
 <li>WFS 2.0.0 <code>{wildCard: &quot;%&quot;, singleChar: &quot;*&quot;, escapeChar: &quot;\&quot;}</code></li>
 <li>WFS 1.0.0 <code>{wildCard: &quot;*&quot;, singleChar: &quot;*&quot;, escape: &quot;\&quot;}</code></li>
 </ul>
-<h5>addressSearch.searchMethodsObject.queryParameters (type:gazetteer)</h5>
+<h5 id="addresssearch.searchmethodsobject.queryparameters-(type%3Agazetteer)" tabindex="-1">addressSearch.searchMethodsObject.queryParameters (type:gazetteer)</h5>
 <blockquote>
 <p>⚠️ &quot;gazetteer&quot; is deprecated. Please use &quot;mpapi&quot; instead.</p>
 </blockquote>
@@ -362,7 +362,7 @@ <h5>addressSearch.searchMethodsObject.queryParameters (type:gazetteer)</h5>
 </tr>
 </tbody>
 </table>
-<h5>addressSearch.searchMethodsObject.queryParameters (type:mpapi)</h5>
+<h5 id="addresssearch.searchmethodsobject.queryparameters-(type%3Ampapi)" tabindex="-1">addressSearch.searchMethodsObject.queryParameters (type:mpapi)</h5>
 <blockquote>
 <p><strong>Please mind that this requires a configured backend. A WFS's Stored Query is requested with predefined parameters using the <a href="https://bitbucket.org/geowerkstatt-hamburg/masterportalapi/src/master/">masterportalApi</a>. This implementation is meant for e.g. https://geodienste.hamburg.de/HH_WFS_GAGES, but works with other WFS configured in the same manner.</strong></p>
 </blockquote>
@@ -408,14 +408,14 @@ <h5>addressSearch.searchMethodsObject.queryParameters (type:mpapi)</h5>
 </tbody>
 </table>
 <p>While all fields are optional, configuring none of them will yield undefined behaviour. At least one search instruction should be set to <code>true</code>.</p>
-<h5>addressSearch.searchMethodsObject.queryParameters (type:bkg)</h5>
+<h5 id="addresssearch.searchmethodsobject.queryparameters-(type%3Abkg)" tabindex="-1">addressSearch.searchMethodsObject.queryParameters (type:bkg)</h5>
 <p>In <em>BKG</em> mode, queryParameter's key-value pairs are used in the service query. E.g. <code>{filter: { bundesland: 'Bremen' }}</code> results in the GET request URL having <code>&amp;filter=bundesland:Bremen</code> as suffix.</p>
 <p>For more options, please check the <a href="https://sg.geodatenzentrum.de/web_public/gdz/dokumentation/deu/geokodierungsdienst.pdf">official documentation</a> regarding what query parameters are interpreted.</p>
 <p>Additionally, it is possible to configure the parameters <code>accesstoken</code> (<code>Authorization</code>) or <code>apiKey</code> (custom header <code>X-Api-Key</code>) to send the described headers to the search service for authentication purposes.
 Note that this changes the request to be non-simple. To be able to use the parameters, the request has to be sent in <a href="https://developer.mozilla.org/en-US/docs/Web/API/Request/mode"><code>cors</code> mode</a> and has to support preflight request <code>OPTIONS</code>.</p>
-<h2>Store</h2>
-<h3>Mutations</h3>
-<h4>setSelectedGroupName</h4>
+<h2 id="store" tabindex="-1">Store</h2>
+<h3 id="mutations" tabindex="-1">Mutations</h3>
+<h4 id="setselectedgroupname" tabindex="-1">setSelectedGroupName</h4>
 <p>This can be used to change the selected search group by name.</p>
 <pre><code class="language-js">map.$store.commit(
   'plugin/addressSearch/setSelectedGroupName',
@@ -423,8 +423,8 @@ <h4>setSelectedGroupName</h4>
 )
 </code></pre>
 <p>Please mind that programmatically changing the search group will <em>not</em> trigger a search, unlike a search group change by the user. If you need a search after change, consider the <code>search</code> action.</p>
-<h3>Actions</h3>
-<h4>search</h4>
+<h3 id="actions" tabindex="-1">Actions</h3>
+<h4 id="search" tabindex="-1">search</h4>
 <p>This is a purely programmatical search method. It is not used by user input.</p>
 <pre><code class="language-js">map.$store.dispatch('plugin/addressSearch/search', {
   input: 'Bahnhofsstraße 12',
@@ -453,7 +453,7 @@ <h4>search</h4>
 </tr>
 </tbody>
 </table>
-<h3>State</h3>
+<h3 id="state" tabindex="-1">State</h3>
 <pre><code class="language-js">map.subscribe('plugin/addressSearch/chosenAddress', (chosenAddress) =&gt; {
   /* Your code. */
 })
diff --git a/docs/meldemichel/plugin-attributions.html b/docs/meldemichel/plugin-attributions.html
index 370a4eddb..489f7f883 100644
--- a/docs/meldemichel/plugin-attributions.html
+++ b/docs/meldemichel/plugin-attributions.html
@@ -22,11 +22,11 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Attributions</h1>
-<h2>Scope</h2>
+    <h1 id="attributions" tabindex="-1">Attributions</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>This plugin shows attributions (that is, legal information) regarding copyrights and sources of the currently visible layers.</p>
-<h2>Configuration</h2>
-<h3>attributions</h3>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
+<h3 id="attributions-1" tabindex="-1">attributions</h3>
 <p>All parameters are optional. However, setting neither <code>layerAttributions</code> nor <code>staticAttributions</code> results in an empty window.</p>
 <table>
 <thead>
@@ -70,7 +70,7 @@ <h3>attributions</h3>
 </tbody>
 </table>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/meldemichel/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
-<h4>attributions.layerAttribution</h4>
+<h4 id="attributions.layerattribution" tabindex="-1">attributions.layerAttribution</h4>
 <table>
 <thead>
 <tr>
diff --git a/docs/meldemichel/plugin-filter.html b/docs/meldemichel/plugin-filter.html
index 72a748b60..4541cc9d5 100644
--- a/docs/meldemichel/plugin-filter.html
+++ b/docs/meldemichel/plugin-filter.html
@@ -22,11 +22,11 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Filter</h1>
-<h2>Scope</h2>
+    <h1 id="filter" tabindex="-1">Filter</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The Filter plugin can be used to filter arbitrary configurable vector layers by their properties.</p>
-<h3>Configuration</h3>
-<h4>filter</h4>
+<h3 id="configuration" tabindex="-1">Configuration</h3>
+<h4 id="filter-1" tabindex="-1">filter</h4>
 <table>
 <thead>
 <tr>
@@ -46,7 +46,7 @@ <h4>filter</h4>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/meldemichel/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
 <pre><code>The following chapters contain drafts in this format. Please mind that they neither represent UI nor localisation, but are merely there to communicate the idea with an example.
 </code></pre>
-<h5>filter.filterConfiguration</h5>
+<h5 id="filter.filterconfiguration" tabindex="-1">filter.filterConfiguration</h5>
 <table>
 <thead>
 <tr>
@@ -68,7 +68,7 @@ <h5>filter.filterConfiguration</h5>
 </tr>
 </tbody>
 </table>
-<h6>filter.filterConfiguration.category</h6>
+<h6 id="filter.filterconfiguration.category" tabindex="-1">filter.filterConfiguration.category</h6>
 <table>
 <thead>
 <tr>
@@ -101,7 +101,7 @@ <h6>filter.filterConfiguration.category</h6>
 ▢ Vanilla
 ▢ Strawberry
 </code></pre>
-<h6>filter.filterConfiguration.time</h6>
+<h6 id="filter.filterconfiguration.time" tabindex="-1">filter.filterConfiguration.time</h6>
 <table>
 <thead>
 <tr>
@@ -139,7 +139,7 @@ <h6>filter.filterConfiguration.time</h6>
 </tbody>
 </table>
 <p>Of all time restrictions, at most one can be selected at any time. The produced options are selectable by radio buttons.</p>
-<h6>filter.filterConfiguration.time.options</h6>
+<h6 id="filter.filterconfiguration.time.options" tabindex="-1">filter.filterConfiguration.time.options</h6>
 <table>
 <thead>
 <tr>
@@ -166,7 +166,7 @@ <h6>filter.filterConfiguration.time.options</h6>
 ◯ Last 7 days
 </code></pre>
 <p>In <code>'days'</code> mode, the selections will always include full days, and additionally the current day. Due to this, the time frame of &quot;last 7 days&quot; is actually 8*24h long. This seems unexpected at first, but follows intuition – if it's Monday and a user filters to the &quot;last seven days&quot;, they would expect to fully see last week's Monday, but also features from that day's morning.</p>
-<h6>filter.filterConfiguration.time.freeSelection</h6>
+<h6 id="filter.filterconfiguration.time.freeselection" tabindex="-1">filter.filterConfiguration.time.freeSelection</h6>
 <table>
 <thead>
 <tr>
@@ -193,7 +193,7 @@ <h6>filter.filterConfiguration.time.freeSelection</h6>
    From ▒▒▒▒▒▒▒▒▒▒▒ // clicking input opens a selector restricted *until* today
    To   ▇▇▇▇▇▇▇▇▇▇▇ // clicking input opens a selector restricted *until* today
 </code></pre>
-<h4>Example configuration</h4>
+<h4 id="example-configuration" tabindex="-1">Example configuration</h4>
 <pre><code class="language-js">{
   filter: {
     layers: {
diff --git a/docs/meldemichel/plugin-fullscreen.html b/docs/meldemichel/plugin-fullscreen.html
index 870c17b34..99bed0368 100644
--- a/docs/meldemichel/plugin-fullscreen.html
+++ b/docs/meldemichel/plugin-fullscreen.html
@@ -22,11 +22,11 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Fullscreen</h1>
-<h2>Scope</h2>
+    <h1 id="fullscreen" tabindex="-1">Fullscreen</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The fullscreen plugin allows viewing the map in fullscreen mode. It relies solely on the <a href="https://developer.mozilla.org/en-US/docs/Web/API/Fullscreen_API">HTML Fullscreen API</a>, where you can also find more about browser support.</p>
-<h2>Configuration</h2>
-<h3>fullscreen</h3>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
+<h3 id="fullscreen-1" tabindex="-1">fullscreen</h3>
 <table>
 <thead>
 <tr>
@@ -49,8 +49,8 @@ <h3>fullscreen</h3>
 </tbody>
 </table>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/meldemichel/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
-<h2>Store</h2>
-<h3>State</h3>
+<h2 id="store" tabindex="-1">Store</h2>
+<h3 id="state" tabindex="-1">State</h3>
 <pre><code class="language-js">map.subscribe('plugin/fullscreen/isInFullscreen', (isInFullscreen) =&gt; {
   /* Your code. */
 })
diff --git a/docs/meldemichel/plugin-geo-location.html b/docs/meldemichel/plugin-geo-location.html
index 6bd06c344..7fb526ce3 100644
--- a/docs/meldemichel/plugin-geo-location.html
+++ b/docs/meldemichel/plugin-geo-location.html
@@ -22,13 +22,13 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>GeoLocation</h1>
-<h2>Scope</h2>
+    <h1 id="geolocation" tabindex="-1">GeoLocation</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The GeoLocation plugin is responsible for collecting and displaying a user's GPS location. It is shown as a crosshair mark on the map.
 The tracking can be triggered initially on startup or via a button. This behavior can be controlled by setting <code>checkLocationInitially</code> to
 either <code>true</code> or <code>false</code>. When a users denies the location tracking, the button for this plugin gets disabled.</p>
-<h2>Configuration</h2>
-<h4>geoLocation</h4>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
+<h4 id="geolocation-1" tabindex="-1">geoLocation</h4>
 <table>
 <thead>
 <tr>
@@ -81,7 +81,7 @@ <h4>geoLocation</h4>
 </tbody>
 </table>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/meldemichel/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
-<h4>Example configuration</h4>
+<h4 id="example-configuration" tabindex="-1">Example configuration</h4>
 <pre><code class="language-json">{
   &quot;geoLocation&quot;: {
     &quot;checkLocationInitially&quot;: true,
@@ -89,8 +89,8 @@ <h4>Example configuration</h4>
   }
 }
 </code></pre>
-<h2>Store</h2>
-<h3>State</h3>
+<h2 id="store" tabindex="-1">Store</h2>
+<h3 id="state" tabindex="-1">State</h3>
 <p>If the access to an users location has been granted, the coordinates get stored in the <code>position</code> state value. This value can be subscribed through the path <code>'plugin/geoLocation/position'</code>.</p>
 <pre><code class="language-js">map.subscribe('plugin/geoLocation/position', (position) =&gt; {
   /* Your code here */
diff --git a/docs/meldemichel/plugin-gfi.html b/docs/meldemichel/plugin-gfi.html
index 1f3f4586c..99823b974 100644
--- a/docs/meldemichel/plugin-gfi.html
+++ b/docs/meldemichel/plugin-gfi.html
@@ -22,14 +22,14 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>GFI</h1>
-<h2>Scope</h2>
+    <h1 id="gfi" tabindex="-1">GFI</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The GFI plugin can be used to fetch and optionally display GFI (GetFeatureInfo) from WMS and WFS services as well as layers based on GeoJSON files. In a first step, the information is stored in the VueX store to allow for easy access. Display is optional and quite obstructive within the map client.</p>
 <blockquote>
 <p>⚠️ The display feature is currently not meant for production. Please use data bindings for display to avoid obstructing the map client.</p>
 </blockquote>
-<h3>Configuration</h3>
-<h4>gfi</h4>
+<h3 id="configuration" tabindex="-1">Configuration</h3>
+<h4 id="gfi-1" tabindex="-1">gfi</h4>
 <table>
 <thead>
 <tr>
@@ -92,7 +92,7 @@ <h4>gfi</h4>
 </tbody>
 </table>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/meldemichel/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
-<h5>gfi.gfiLayerConfiguration</h5>
+<h5 id="gfi.gfilayerconfiguration" tabindex="-1">gfi.gfiLayerConfiguration</h5>
 <table>
 <thead>
 <tr>
@@ -156,7 +156,7 @@ <h5>gfi.gfiLayerConfiguration</h5>
 </tr>
 </tbody>
 </table>
-<h5>gfi.customHighlightStyle</h5>
+<h5 id="gfi.customhighlightstyle" tabindex="-1">gfi.customHighlightStyle</h5>
 <table>
 <thead>
 <tr>
@@ -178,7 +178,7 @@ <h5>gfi.customHighlightStyle</h5>
 </tr>
 </tbody>
 </table>
-<h5>gfi.featureList</h5>
+<h5 id="gfi.featurelist" tabindex="-1">gfi.featureList</h5>
 <table>
 <thead>
 <tr>
@@ -210,7 +210,7 @@ <h5>gfi.featureList</h5>
 </tr>
 </tbody>
 </table>
-<h4>Example configuration</h4>
+<h4 id="example-configuration" tabindex="-1">Example configuration</h4>
 <pre><code class="language-js">layers: {
   [serviceId]: {
     geometry: true,
@@ -235,8 +235,8 @@ <h4>Example configuration</h4>
   },
 },
 </code></pre>
-<h2>Store</h2>
-<h3>State</h3>
+<h2 id="store" tabindex="-1">Store</h2>
+<h3 id="state" tabindex="-1">State</h3>
 <p>If a successful query has been sent and a response has been received, the result will be saved in the store and can be subscribed through the path <code>'plugin/gfi/featureInformation'</code>. If, however, a query for a layer fails, a <code>Symbol</code> containing the error will be saved in the store instead to indicate the error.</p>
 <p>The exact value of <code>featureInformation</code> may vary wildly depending on the service used, but is always given as json representation here.</p>
 <pre><code class="language-js">map.subscribe('plugin/gfi/featureInformation', (featureInformation) =&gt; {
diff --git a/docs/meldemichel/plugin-icon-menu.html b/docs/meldemichel/plugin-icon-menu.html
index aa7616687..c376bb04b 100644
--- a/docs/meldemichel/plugin-icon-menu.html
+++ b/docs/meldemichel/plugin-icon-menu.html
@@ -22,13 +22,13 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>IconMenu</h1>
+    <h1 id="iconmenu" tabindex="-1">IconMenu</h1>
 <p>The IconMenu offers an icon-button based menu to open various functionality as cards. This way, obstructive UI can be hidden until the user desires to open it. Please use carefully – users may have issues finding process-relevant buttons/interactions if you hide them here.<br>
 Currently, the IconMenu should only be rendered with <code>layoutTag</code> set to <code>NineLayoutTag.TOP_RIGHT</code>.</p>
-<h2>Scope</h2>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>It is meant for additional information/functionality (legend, other layers) or power users in non-public clients.</p>
 <p><em>Please note that the average user has never seen the client before and just wants to get done with it, not learn a map client.</em></p>
-<h2>Configuration</h2>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
 <blockquote>
 <p>⚠️ This plugin can't be configured with the <code>mapConfiguration</code>, but is configured during client construction. Currently, no way exists to add plugins to it after the build took place.</p>
 </blockquote>
@@ -60,7 +60,7 @@ <h2>Configuration</h2>
   ],
 }
 </code></pre>
-<h3>menus</h3>
+<h3 id="menus" tabindex="-1">menus</h3>
 <p>When landscape mode is active the IconMenu is oriented horizontally. Currently, the IconMenu works fine only if there is not more than one row of Icons in landscape mode.</p>
 
     
diff --git a/docs/meldemichel/plugin-layer-chooser.html b/docs/meldemichel/plugin-layer-chooser.html
index 3fbf04a0f..4d6453bfc 100644
--- a/docs/meldemichel/plugin-layer-chooser.html
+++ b/docs/meldemichel/plugin-layer-chooser.html
@@ -22,12 +22,12 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>LayerChooser</h1>
+    <h1 id="layerchooser" tabindex="-1">LayerChooser</h1>
 <p>The tool offers layer selection to the user.</p>
-<h2>Scope</h2>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The LayerChooser offers an additive (usually Overlays, technically named with <code>type: 'mask'</code>) and an exclusive (usually background maps, <code>type: 'background'</code>) selection of layers to the users.</p>
 <p>Order of layers within a layer is currently always as initially configured.</p>
-<h2>Configuration</h2>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
 <p>The tool does not require any configuration for itself, but is based on the <code>mapConfiguration.layers</code> array. It will infer its options from there, and change layer visibility and availability depending on <code>minZoom</code> and <code>maxZoom</code>.</p>
 <p>Each object in <code>mapConfiguration.layers</code> array fits this definition:</p>
 <table>
@@ -82,7 +82,7 @@ <h2>Configuration</h2>
 </tbody>
 </table>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/meldemichel/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
-<h3>mapConfiguration.layers.options</h3>
+<h3 id="mapconfiguration.layers.options" tabindex="-1">mapConfiguration.layers.options</h3>
 <p>An option wheel will appear in the layer chooser that allows opening a sub-menu with configured configuration options for the end user.</p>
 <table>
 <thead>
@@ -100,7 +100,7 @@ <h3>mapConfiguration.layers.options</h3>
 </tr>
 </tbody>
 </table>
-<h4>mapConfiguration.layers.options.layers</h4>
+<h4 id="mapconfiguration.layers.options.layers" tabindex="-1">mapConfiguration.layers.options.layers</h4>
 <p>This field is named like this to match the OGC specification for their name; that is, layers have layers that may have layers that may have layers, and so on. However, only the first level (a layer's layers) is currently implemented.</p>
 <table>
 <thead>
diff --git a/docs/meldemichel/plugin-loading-indicator.html b/docs/meldemichel/plugin-loading-indicator.html
index 3e12ffc31..10ae7ff9f 100644
--- a/docs/meldemichel/plugin-loading-indicator.html
+++ b/docs/meldemichel/plugin-loading-indicator.html
@@ -22,13 +22,13 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>LoadingIndicator</h1>
-<h2>Scope</h2>
+    <h1 id="loadingindicator" tabindex="-1">LoadingIndicator</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>A generic loading indicator that may be used by any plugin or outside procedure to indicate loading.</p>
-<h2>Configuration</h2>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/meldemichel/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
-<h2>Store</h2>
-<h3>Mutations</h3>
+<h2 id="store" tabindex="-1">Store</h2>
+<h3 id="mutations" tabindex="-1">Mutations</h3>
 <pre><code class="language-js">// show loading indicator
 map.$store.commit('plugin/loadingIndicator/addLoadingKey', key)
 // hide loading indicator
@@ -37,7 +37,7 @@ <h3>Mutations</h3>
 <p><img src="./readme_loadingIndicator_example.png" alt="Loading indicator example"></p>
 <p>The key must be unique and is kept track of via a Set. It can't be added multiple times, and removing it once always removes it altogether. It is advised to use a key like <code>{my-plugin-or-application-name}-{procedure-name}</code> to avoid name conflicts. The LoadingIndicator will usually be used for asynchronous code.</p>
 <p>As such, <strong>always call <code>removeLoadingKey</code> in the <code>finally</code> section of your code</strong> to prevent hanging loading indicators.</p>
-<h3>Getters</h3>
+<h3 id="getters" tabindex="-1">Getters</h3>
 <p>You may desire to listen to whether the loader is currently being shown.</p>
 <table>
 <thead>
diff --git a/docs/meldemichel/plugin-pins.html b/docs/meldemichel/plugin-pins.html
index 1985b16de..2c36045af 100644
--- a/docs/meldemichel/plugin-pins.html
+++ b/docs/meldemichel/plugin-pins.html
@@ -22,12 +22,12 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Pins</h1>
-<h2>Scope</h2>
+    <h1 id="pins" tabindex="-1">Pins</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The pins plugin handles marking locations. Embedding processes can then use that coordinate for further steps. The plugin may react to other plugins, especially address searches.</p>
-<h2>Configuration</h2>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
 <p>The usage of <code>displayComponent</code> has no influence on the creation of Pins on the Map if this plugin is being used.</p>
-<h3>pins</h3>
+<h3 id="pins-1" tabindex="-1">pins</h3>
 <table>
 <thead>
 <tr>
@@ -84,7 +84,7 @@ <h3>pins</h3>
 </tr>
 </tbody>
 </table>
-<h4>pins.appearOnClick</h4>
+<h4 id="pins.appearonclick" tabindex="-1">pins.appearOnClick</h4>
 <table>
 <thead>
 <tr>
@@ -106,7 +106,7 @@ <h4>pins.appearOnClick</h4>
 </tr>
 </tbody>
 </table>
-<h4>pins.initial</h4>
+<h4 id="pins.initial" tabindex="-1">pins.initial</h4>
 <table>
 <thead>
 <tr>
@@ -133,7 +133,7 @@ <h4>pins.initial</h4>
 </tr>
 </tbody>
 </table>
-<h4>pins.style</h4>
+<h4 id="pins.style" tabindex="-1">pins.style</h4>
 <table>
 <thead>
 <tr>
@@ -155,8 +155,8 @@ <h4>pins.style</h4>
 </tr>
 </tbody>
 </table>
-<h2>Store</h2>
-<h3>State</h3>
+<h2 id="store" tabindex="-1">Store</h2>
+<h3 id="state" tabindex="-1">State</h3>
 <pre><code class="language-js">map.subscribe('plugin/pins/transformedCoordinate', (pinCoordinate) =&gt; {
   /* Your Code. */
 })
diff --git a/docs/meldemichel/plugin-reverse-geocoder.html b/docs/meldemichel/plugin-reverse-geocoder.html
index ba1db2ce2..855c2e77a 100644
--- a/docs/meldemichel/plugin-reverse-geocoder.html
+++ b/docs/meldemichel/plugin-reverse-geocoder.html
@@ -22,12 +22,12 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Reverse Geocoder</h1>
-<h2>Scope</h2>
+    <h1 id="reverse-geocoder" tabindex="-1">Reverse Geocoder</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>Reverse Geocoder Plugin that turns coordinates into addresses via a WPS. It does not offer any UI by itself.</p>
 <p>This module has been written for the HH WPS service. The return format is custom and no other WPS are currently supported. Please mind this when trying to use this plugin with any other WPS. For usage with other WPS, those must either fit the HH WPS, or a generalization of this plugin is required.</p>
-<h2>Configuration</h2>
-<h3>reverseGeocoder</h3>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
+<h3 id="reversegeocoder" tabindex="-1">reverseGeocoder</h3>
 <table>
 <thead>
 <tr>
@@ -69,9 +69,9 @@ <h3>reverseGeocoder</h3>
 </tr>
 </tbody>
 </table>
-<h2>Store</h2>
+<h2 id="store" tabindex="-1">Store</h2>
 <p>The ReverseGeocoder plugin does not hold any state.</p>
-<h3>Actions</h3>
+<h3 id="actions" tabindex="-1">Actions</h3>
 <pre><code class="language-js">// result contains the resolved address (exact format depends on WPS)
 const result = await map.$store.dispatch(
   'plugin/reverseGeocoder/reverseGeocode',
diff --git a/docs/meldemichel/plugin-scale.html b/docs/meldemichel/plugin-scale.html
index bd3861294..55070bb6e 100644
--- a/docs/meldemichel/plugin-scale.html
+++ b/docs/meldemichel/plugin-scale.html
@@ -22,14 +22,14 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Scale</h1>
+    <h1 id="scale" tabindex="-1">Scale</h1>
 <blockquote>
 <p>⚠ The Scale plugin is currently meant for passive usage only. It's API has not yet been finally defined, and is subject to change without further notice.</p>
 </blockquote>
-<h2>Scope</h2>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The scale plugin shows the current map resolution as relative scale (1:x) and/or absolute scale (a drawn line has length x units).</p>
-<h2>Configuration</h2>
-<h3>scale</h3>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
+<h3 id="scale-1" tabindex="-1">scale</h3>
 <table>
 <thead>
 <tr>
diff --git a/docs/meldemichel/plugin-toast.html b/docs/meldemichel/plugin-toast.html
index a85b9e5a5..2b3505c04 100644
--- a/docs/meldemichel/plugin-toast.html
+++ b/docs/meldemichel/plugin-toast.html
@@ -22,12 +22,12 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Toast</h1>
-<h2>Scope</h2>
+    <h1 id="toast" tabindex="-1">Toast</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The toast plugin offers global functionality to display text messages to the user. These are the classic success, warning, info, and error messages, helping to understand what's going on or why something happened.</p>
-<h2>Configuration</h2>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
 <p>Please check the vuetify documentation to override the success, warning, info, or errors colors in general. To affect only this plugin, the following configuration parameters can be added to either the plugin instantiation or the mapConfiguration:</p>
-<h3>toast</h3>
+<h3 id="toast-1" tabindex="-1">toast</h3>
 <table>
 <thead>
 <tr>
@@ -60,7 +60,7 @@ <h3>toast</h3>
 </tbody>
 </table>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/meldemichel/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
-<h4>toast.toastStyle</h4>
+<h4 id="toast.toaststyle" tabindex="-1">toast.toastStyle</h4>
 <table>
 <thead>
 <tr>
@@ -82,12 +82,12 @@ <h4>toast.toastStyle</h4>
 </tr>
 </tbody>
 </table>
-<h2>Store</h2>
-<h3>Actions</h3>
+<h2 id="store" tabindex="-1">Store</h2>
+<h3 id="actions" tabindex="-1">Actions</h3>
 <p>New entries are made via action. They are either dismissed after a timeout or by user interaction.</p>
 <pre><code class="language-js">map.$store.dispatch('plugin/toast/addToast', payload)
 </code></pre>
-<h4>Payload structure</h4>
+<h4 id="payload-structure" tabindex="-1">Payload structure</h4>
 <table>
 <thead>
 <tr>
@@ -124,7 +124,7 @@ <h4>Payload structure</h4>
 </tr>
 </tbody>
 </table>
-<h4>Usage example</h4>
+<h4 id="usage-example" tabindex="-1">Usage example</h4>
 <pre><code class="language-js">map.$store.dispatch('plugin/toast/addToast', {
   type: 'warning',
   text: 'Wrong hammer for screw.',
diff --git a/docs/meldemichel/plugin-zoom.html b/docs/meldemichel/plugin-zoom.html
index 2a9da01bd..42aaab204 100644
--- a/docs/meldemichel/plugin-zoom.html
+++ b/docs/meldemichel/plugin-zoom.html
@@ -22,10 +22,10 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Zoom</h1>
-<h2>Scope</h2>
+    <h1 id="zoom" tabindex="-1">Zoom</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The Zoom plugin offers functionality regarding map zooming.</p>
-<h2>Configuration</h2>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
 <p>The Zoom plugin offers a plus/minus button, and will adjust itself to the map's zoom settings on initialization.<br>
 It can be configured as followed.</p>
 <table>
@@ -55,8 +55,8 @@ <h2>Configuration</h2>
 </tbody>
 </table>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/meldemichel/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
-<h2>Store</h2>
-<h3>State</h3>
+<h2 id="store" tabindex="-1">Store</h2>
+<h3 id="state" tabindex="-1">State</h3>
 <p>The map's zoom level can be listened to.</p>
 <table>
 <thead>
@@ -88,7 +88,7 @@ <h3>State</h3>
   /* This code is called on any zoomLevel update. */
 })
 </code></pre>
-<h3>Getters</h3>
+<h3 id="getters" tabindex="-1">Getters</h3>
 <table>
 <thead>
 <tr>
@@ -117,7 +117,7 @@ <h3>Getters</h3>
   }
 )
 </code></pre>
-<h3>Actions</h3>
+<h3 id="actions" tabindex="-1">Actions</h3>
 <p>The zoomLevel can be set programmatically.</p>
 <pre><code class="language-js">map.$store.dispatch('plugin/zoom/setZoomLevel', zoomLevelNumber)
 map.$store.dispatch('plugin/zoom/increaseZoomLevel')
diff --git a/docs/snowbox/client-snowbox.html b/docs/snowbox/client-snowbox.html
index d6e83fb8c..d15bc2513 100644
--- a/docs/snowbox/client-snowbox.html
+++ b/docs/snowbox/client-snowbox.html
@@ -22,7 +22,7 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Snowbox API Documentation</h1>
+    <h1 id="snowbox-api-documentation" tabindex="-1">Snowbox API Documentation</h1>
 <p>This is an API file that is used as part of the generated documentation. It will appear as main document in the snowbox's documentation.</p>
 <p>If the snowbox implemented any own features that are not derived from either core of plugins, this would be the place to document them. However, since that's not the case, it only features this introduction text and the link list below.</p>
 
diff --git a/docs/snowbox/core.html b/docs/snowbox/core.html
index 30ed9bbdf..aa70cc755 100644
--- a/docs/snowbox/core.html
+++ b/docs/snowbox/core.html
@@ -22,8 +22,8 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Core</h1>
-<h2>Scope</h2>
+    <h1 id="core" tabindex="-1">Core</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The client's core is the base package to create clients in the POLAR environment.</p>
 <p>It offers this functionality:</p>
 <ul>
@@ -31,15 +31,15 @@ <h2>Scope</h2>
 <li>@masterportal/masterportalapi functionality</li>
 <li>Localization mechanism</li>
 </ul>
-<h2>Interaction</h2>
+<h2 id="interaction" tabindex="-1">Interaction</h2>
 <p>If a client is rendered as part of another page, the zoom and drag-pan behaviour is different to if the client is rendered as complete page.<br>
 If it's part of another page, drag-panning on mobile devices is only usable if at least two fingers are being used while on desktop clients the user can only zoom if using the respective platform modifier key (e.g. CTRL).</p>
 <p>It is important to note that the behaviour will be desktop-like on larger touchscreen devices (e.g. tablets).</p>
-<h2>Initialization / Configuration</h2>
+<h2 id="initialization-%2F-configuration" tabindex="-1">Initialization / Configuration</h2>
 <p>It depends on the client how exactly the initialization will take place for the embedding programmer. However, the core mechanism remains the same.</p>
 <p>The exported default object is an extended masterportalAPI, adding the <code>addPlugins</code> and extending the <code>createMap</code> functions. For masterportalAPI details, <a href="https://bitbucket.org/geowerkstatt-hamburg/masterportalapi/src/master/">see their repository</a>.</p>
 <p>To be able to see the map in production mode, the imported stylesheet has to have the property <code>data-polar</code>. The value can be chosen arbitrarily. ⚠️ Deprecated. The new field 'stylePath' should be used instead.</p>
-<h3>addPlugins</h3>
+<h3 id="addplugins" tabindex="-1">addPlugins</h3>
 <p>Before instantiating the map, all required plugins have to be added. Depending on how you use POLAR, this may already have been done. Ready-made clients (that is, packages prefixed <code>@polar/client-</code>) come with plugins prepared. You may add further plugins or proceed with <code>createMap</code>.</p>
 <p>In case you're integrating new plugins, call <code>addPlugins</code> with an array of instances.</p>
 <pre><code class="language-js">client.addPlugins([Plugin({ pluginConfig })])
@@ -55,7 +55,7 @@ <h3>addPlugins</h3>
   })
 </code></pre>
 <p>If the storeModule features a <code>setupModule</code> action, it will be executed automatically after initialization.</p>
-<h3>createMap</h3>
+<h3 id="createmap" tabindex="-1">createMap</h3>
 <p>The map is created by calling the <code>createMap</code> method. Depending on how you use POLAR, this may already have been done, as some clients come as ready-made standalone HTML pages that do this for you.</p>
 <pre><code class="language-js">MapClient.createMap({
   // arbitrary id, must point to a div
@@ -66,7 +66,7 @@ <h3>createMap</h3>
   /* Your Code, e.g. for setting up callbacks. */
 })
 </code></pre>
-<h4>mapConfiguration</h4>
+<h4 id="mapconfiguration" tabindex="-1">mapConfiguration</h4>
 <p>The mapConfiguration allows controlling many client instance details.</p>
 <table>
 <thead>
@@ -124,7 +124,7 @@ <h4>mapConfiguration</h4>
 </tr>
 </tbody>
 </table>
-<h5>mapConfiguration.LanguageOption</h5>
+<h5 id="mapconfiguration.languageoption" tabindex="-1">mapConfiguration.LanguageOption</h5>
 <p>A language option is an object consisting of a type (its language key) and the i18next resource definition. You may e.g. decide that the texts offered in the LayerChooser do not fit the style of your client, or that they could be more precise in your situation since you're only using <em>very specific</em> overlays.</p>
 <p>An example for a LanguageOption array usable in <code>createMap</code> is this array:</p>
 <pre><code class="language-ts">const languageOptions: LanguageOption[] = [
@@ -151,7 +151,7 @@ <h5>mapConfiguration.LanguageOption</h5>
 ]
 </code></pre>
 <p>To figure out the name of the locales to override, inspect the matching plugin in GitHub's file browser. In <code>packages/plugins</code>, open the plugin you desire to override. Each plugin's <code>src</code> folder contains a <code>language.ts</code> listing all used locale keys with appropriate nesting.</p>
-<h5>mapConfiguration.extendedMasterportalapiMarkers</h5>
+<h5 id="mapconfiguration.extendedmasterportalapimarkers" tabindex="-1">mapConfiguration.extendedMasterportalapiMarkers</h5>
 <table>
 <thead>
 <tr>
@@ -193,7 +193,7 @@ <h5>mapConfiguration.extendedMasterportalapiMarkers</h5>
 </tr>
 </tbody>
 </table>
-<h6>mapConfiguration.extendedMasterportalapiMarkers.MarkerStyle</h6>
+<h6 id="mapconfiguration.extendedmasterportalapimarkers.markerstyle" tabindex="-1">mapConfiguration.extendedMasterportalapiMarkers.MarkerStyle</h6>
 <table>
 <thead>
 <tr>
@@ -281,7 +281,7 @@ <h6>mapConfiguration.extendedMasterportalapiMarkers.MarkerStyle</h6>
 </tbody>
 </table>
 </blockquote>
-<h5>mapConfiguration.LayerConf</h5>
+<h5 id="mapconfiguration.layerconf" tabindex="-1">mapConfiguration.LayerConf</h5>
 <p>The layer configuration (or: service register) is read by the masterportalAPI. The full definition can be read <a href="https://bitbucket.org/geowerkstatt-hamburg/masterportal/src/dev/doc/services.json.md">here</a>.</p>
 <p>However, not all listed services have been implemented in the masterportalAPI yet, and no documentation regarding implemented properties exists there yet.</p>
 <p>Whitelisted and confirmed parameters include:</p>
@@ -289,7 +289,7 @@ <h5>mapConfiguration.LayerConf</h5>
 <li>WMS: id, name, url, typ, format, version, transparent, layers, STYLES</li>
 <li>WFS: id, name, url, typ, outputFormat, version, featureType</li>
 </ul>
-<h6>Example services register</h6>
+<h6 id="example-services-register" tabindex="-1">Example services register</h6>
 <pre><code class="language-json">[
   {
     &quot;id&quot;: &quot;my-wfs-id&quot;,
@@ -313,7 +313,7 @@ <h6>Example services register</h6>
 ]
 </code></pre>
 <p>Since this is the base for many functions, the service ID set in this is used to reference map material in many places of the map client.</p>
-<h5>&lt;...masterportalAPI.fields&gt;</h5>
+<h5 id="%3C...masterportalapi.fields%3E" tabindex="-1">&lt;...masterportalAPI.fields&gt;</h5>
 <p>The <code>&lt;...masterportalAPI.fields&gt;</code> means that any masterportalAPI field may also be used here <em>directly</em>. The most common fields are the following ones; for more, see masterportalAPI.</p>
 <table>
 <thead>
@@ -356,10 +356,10 @@ <h5>&lt;...masterportalAPI.fields&gt;</h5>
 </tr>
 </tbody>
 </table>
-<h5>&lt;plugin.fields&gt;</h5>
-<p>Plugins in POLAR are modular components that extend the functionality of the map client. They can be added using the <a href="#addPlugins">addPlugins</a> method and configured through the <code>mapConfiguration</code> object. Each plugin has its own set of fields and options that can be customized.</p>
+<h5 id="%3Cplugin.fields%3E" tabindex="-1">&lt;plugin.fields&gt;</h5>
+<p>Plugins in POLAR are modular components that extend the functionality of the map client. They can be added using the <a href="#addplugins">addPlugins</a> method and configured through the <code>mapConfiguration</code> object. Each plugin has its own set of fields and options that can be customized.</p>
 <p>On how to configure a plugin, see the respective plugin. The configuration is given in the <code>mapConfiguration</code> object by the plugin's name as specified in its respective documentation.</p>
-<h6>Global Plugin Parameters</h6>
+<h6 id="global-plugin-parameters" tabindex="-1">Global Plugin Parameters</h6>
 <p>Most plugins honor this additional field.</p>
 <table>
 <thead>
@@ -377,7 +377,7 @@ <h6>Global Plugin Parameters</h6>
 </tr>
 </tbody>
 </table>
-<h6>Example Configuration</h6>
+<h6 id="example-configuration" tabindex="-1">Example Configuration</h6>
 <p>For example, a <code>@polar/plugin-address-search</code> plugin can be configured like this:</p>
 <pre><code class="language-js">{
   addressSearch: {
@@ -387,7 +387,7 @@ <h6>Example Configuration</h6>
   }
 }
 </code></pre>
-<h5>mapConfiguration.vuetify</h5>
+<h5 id="mapconfiguration.vuetify" tabindex="-1">mapConfiguration.vuetify</h5>
 <p>These fields let you e.g. specify a <a href="https://vuetifyjs.com/en/features/theme/">Vuetify-Theme</a>. For more options, refer to the official vuetify documentation.</p>
 <p>Additionally to the regular fields, <code>primaryContrast</code> and <code>secondaryContrast</code> are interpreted. They serve as contrast colors to their respective fields and are used for e.g. button icons.</p>
 <pre><code class="language-js">{
@@ -403,7 +403,7 @@ <h5>mapConfiguration.vuetify</h5>
   }
 }
 </code></pre>
-<h2>Store</h2>
+<h2 id="store" tabindex="-1">Store</h2>
 <p>The core module features a vuex root store that all plugin vuex modules are plugged into. However, the root contents are only relevant to plugins. It is accessible with <code>map.$store</code>, and can be used as a starting point for plugin access.</p>
 <p>To ease use, the map instance also features a <code>subscribe</code> method that will register a watcher to any state field. Please mind that only documented paths should be used, and all others are subject to change without notice.</p>
 <pre><code class="language-js">// state subscription – listening to data held by the map client
diff --git a/docs/snowbox/lib-custom-types.html b/docs/snowbox/lib-custom-types.html
index fc8188e5f..775c6e0a3 100644
--- a/docs/snowbox/lib-custom-types.html
+++ b/docs/snowbox/lib-custom-types.html
@@ -22,7 +22,7 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Custom Types</h1>
+    <h1 id="custom-types" tabindex="-1">Custom Types</h1>
 <p>This is a custom type library for overarching types. They can be used both in core, plugin, and lib packages to develop a common custom package-global type system.</p>
 <p>Keep it as small as possible and sort types where they belong, whenever possible.</p>
 
diff --git a/docs/snowbox/plugin-address-search.html b/docs/snowbox/plugin-address-search.html
index 8526727fd..91b3975a9 100644
--- a/docs/snowbox/plugin-address-search.html
+++ b/docs/snowbox/plugin-address-search.html
@@ -22,8 +22,8 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>AddressSearch</h1>
-<h2>Scope</h2>
+    <h1 id="addresssearch" tabindex="-1">AddressSearch</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The AddressSearch plugin allows users to search for an address. If multiple addresses are returned by services, the user is prompted to select a result.</p>
 <p>The plugin saves the chosen information as GeoJSON to the store so that following procedures may grab it or so that other plugins may use it.</p>
 <p>Currently supported services:</p>
@@ -32,8 +32,8 @@ <h2>Scope</h2>
 <li>WFS</li>
 <li>Some gazetteers/WFS-G (please request a check or try yourself, not 100% done)</li>
 </ul>
-<h2>Configuration</h2>
-<h3>addressSearch</h3>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
+<h3 id="addresssearch-1" tabindex="-1">addressSearch</h3>
 <p>The configuration allows defining and grouping services. Grouped services can be requested in a search at the same time, and one group of searches can be active at a time. When multiple searches are in a group, they may be extended with category information to make the results easier to browse.</p>
 <p>It is advised to either use one-search-per-group <em>or</em> all services in a singular group to avoid an overly complex UI. Mixed configurations may be required for more complex search requirements.</p>
 <p>In <code>categoryProperties</code> and <code>groupProperties</code>, id strings called <code>groupId</code> and <code>categoryId</code> are used. These are arbitrary strings you can introduce and reuse to group or categorize elements together. Regarding what groups and categories are, see further below.</p>
@@ -104,7 +104,7 @@ <h3>addressSearch</h3>
 </tbody>
 </table>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/snowbox/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
-<h4>addressSearch.searchMethodsObject</h4>
+<h4 id="addresssearch.searchmethodsobject" tabindex="-1">addressSearch.searchMethodsObject</h4>
 <table>
 <thead>
 <tr>
@@ -156,7 +156,7 @@ <h4>addressSearch.searchMethodsObject</h4>
 </tr>
 </tbody>
 </table>
-<h4>addressSearch.customSearchMethod</h4>
+<h4 id="addresssearch.customsearchmethod" tabindex="-1">addressSearch.customSearchMethod</h4>
 <p>This is a function with the following signature:</p>
 <pre><code>(
   // should be used to actually abort request
@@ -170,7 +170,7 @@ <h4>addressSearch.customSearchMethod</h4>
 ) =&gt; Promise&lt;FeatureCollection&gt; | never
 </code></pre>
 <p>With this, arbitrary services can be supported.</p>
-<h4>addressSearch.customSelectFunction</h4>
+<h4 id="addresssearch.customselectfunction" tabindex="-1">addressSearch.customSelectFunction</h4>
 <p>This is a function with the following signature:</p>
 <pre><code>({
   // VueX context object
@@ -182,7 +182,7 @@ <h4>addressSearch.customSelectFunction</h4>
 }) =&gt; void
 </code></pre>
 <p>With this, arbitrary click results can be supported. Please mind that undocumented mutations and actions fired in such a function are subject to change without further notice.</p>
-<h4>addressSearch.groupProperties</h4>
+<h4 id="addresssearch.groupproperties" tabindex="-1">addressSearch.groupProperties</h4>
 <table>
 <thead>
 <tr>
@@ -219,7 +219,7 @@ <h4>addressSearch.groupProperties</h4>
 </tr>
 </tbody>
 </table>
-<h4>addressSearch.categoryProperties</h4>
+<h4 id="addresssearch.categoryproperties" tabindex="-1">addressSearch.categoryProperties</h4>
 <table>
 <thead>
 <tr>
@@ -236,7 +236,7 @@ <h4>addressSearch.categoryProperties</h4>
 </tr>
 </tbody>
 </table>
-<h5>addressSearch.searchMethodsObject.queryParameters (type:common)</h5>
+<h5 id="addresssearch.searchmethodsobject.queryparameters-(type%3Acommon)" tabindex="-1">addressSearch.searchMethodsObject.queryParameters (type:common)</h5>
 <p>These fields are interpreted by all implemented services.</p>
 <table>
 <thead>
@@ -254,7 +254,7 @@ <h5>addressSearch.searchMethodsObject.queryParameters (type:common)</h5>
 </tr>
 </tbody>
 </table>
-<h5>addressSearch.searchMethodsObject.queryParameters (type:wfs)</h5>
+<h5 id="addresssearch.searchmethodsobject.queryparameters-(type%3Awfs)" tabindex="-1">addressSearch.searchMethodsObject.queryParameters (type:wfs)</h5>
 <table>
 <thead>
 <tr>
@@ -317,7 +317,7 @@ <h5>addressSearch.searchMethodsObject.queryParameters (type:wfs)</h5>
 <li>WFS 2.0.0 <code>{wildCard: &quot;%&quot;, singleChar: &quot;*&quot;, escapeChar: &quot;\&quot;}</code></li>
 <li>WFS 1.0.0 <code>{wildCard: &quot;*&quot;, singleChar: &quot;*&quot;, escape: &quot;\&quot;}</code></li>
 </ul>
-<h5>addressSearch.searchMethodsObject.queryParameters (type:gazetteer)</h5>
+<h5 id="addresssearch.searchmethodsobject.queryparameters-(type%3Agazetteer)" tabindex="-1">addressSearch.searchMethodsObject.queryParameters (type:gazetteer)</h5>
 <blockquote>
 <p>⚠️ &quot;gazetteer&quot; is deprecated. Please use &quot;mpapi&quot; instead.</p>
 </blockquote>
@@ -362,7 +362,7 @@ <h5>addressSearch.searchMethodsObject.queryParameters (type:gazetteer)</h5>
 </tr>
 </tbody>
 </table>
-<h5>addressSearch.searchMethodsObject.queryParameters (type:mpapi)</h5>
+<h5 id="addresssearch.searchmethodsobject.queryparameters-(type%3Ampapi)" tabindex="-1">addressSearch.searchMethodsObject.queryParameters (type:mpapi)</h5>
 <blockquote>
 <p><strong>Please mind that this requires a configured backend. A WFS's Stored Query is requested with predefined parameters using the <a href="https://bitbucket.org/geowerkstatt-hamburg/masterportalapi/src/master/">masterportalApi</a>. This implementation is meant for e.g. https://geodienste.hamburg.de/HH_WFS_GAGES, but works with other WFS configured in the same manner.</strong></p>
 </blockquote>
@@ -408,14 +408,14 @@ <h5>addressSearch.searchMethodsObject.queryParameters (type:mpapi)</h5>
 </tbody>
 </table>
 <p>While all fields are optional, configuring none of them will yield undefined behaviour. At least one search instruction should be set to <code>true</code>.</p>
-<h5>addressSearch.searchMethodsObject.queryParameters (type:bkg)</h5>
+<h5 id="addresssearch.searchmethodsobject.queryparameters-(type%3Abkg)" tabindex="-1">addressSearch.searchMethodsObject.queryParameters (type:bkg)</h5>
 <p>In <em>BKG</em> mode, queryParameter's key-value pairs are used in the service query. E.g. <code>{filter: { bundesland: 'Bremen' }}</code> results in the GET request URL having <code>&amp;filter=bundesland:Bremen</code> as suffix.</p>
 <p>For more options, please check the <a href="https://sg.geodatenzentrum.de/web_public/gdz/dokumentation/deu/geokodierungsdienst.pdf">official documentation</a> regarding what query parameters are interpreted.</p>
 <p>Additionally, it is possible to configure the parameters <code>accesstoken</code> (<code>Authorization</code>) or <code>apiKey</code> (custom header <code>X-Api-Key</code>) to send the described headers to the search service for authentication purposes.
 Note that this changes the request to be non-simple. To be able to use the parameters, the request has to be sent in <a href="https://developer.mozilla.org/en-US/docs/Web/API/Request/mode"><code>cors</code> mode</a> and has to support preflight request <code>OPTIONS</code>.</p>
-<h2>Store</h2>
-<h3>Mutations</h3>
-<h4>setSelectedGroupName</h4>
+<h2 id="store" tabindex="-1">Store</h2>
+<h3 id="mutations" tabindex="-1">Mutations</h3>
+<h4 id="setselectedgroupname" tabindex="-1">setSelectedGroupName</h4>
 <p>This can be used to change the selected search group by name.</p>
 <pre><code class="language-js">map.$store.commit(
   'plugin/addressSearch/setSelectedGroupName',
@@ -423,8 +423,8 @@ <h4>setSelectedGroupName</h4>
 )
 </code></pre>
 <p>Please mind that programmatically changing the search group will <em>not</em> trigger a search, unlike a search group change by the user. If you need a search after change, consider the <code>search</code> action.</p>
-<h3>Actions</h3>
-<h4>search</h4>
+<h3 id="actions" tabindex="-1">Actions</h3>
+<h4 id="search" tabindex="-1">search</h4>
 <p>This is a purely programmatical search method. It is not used by user input.</p>
 <pre><code class="language-js">map.$store.dispatch('plugin/addressSearch/search', {
   input: 'Bahnhofsstraße 12',
@@ -453,7 +453,7 @@ <h4>search</h4>
 </tr>
 </tbody>
 </table>
-<h3>State</h3>
+<h3 id="state" tabindex="-1">State</h3>
 <pre><code class="language-js">map.subscribe('plugin/addressSearch/chosenAddress', (chosenAddress) =&gt; {
   /* Your code. */
 })
diff --git a/docs/snowbox/plugin-attributions.html b/docs/snowbox/plugin-attributions.html
index 10f911467..10c1b500a 100644
--- a/docs/snowbox/plugin-attributions.html
+++ b/docs/snowbox/plugin-attributions.html
@@ -22,11 +22,11 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Attributions</h1>
-<h2>Scope</h2>
+    <h1 id="attributions" tabindex="-1">Attributions</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>This plugin shows attributions (that is, legal information) regarding copyrights and sources of the currently visible layers.</p>
-<h2>Configuration</h2>
-<h3>attributions</h3>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
+<h3 id="attributions-1" tabindex="-1">attributions</h3>
 <p>All parameters are optional. However, setting neither <code>layerAttributions</code> nor <code>staticAttributions</code> results in an empty window.</p>
 <table>
 <thead>
@@ -70,7 +70,7 @@ <h3>attributions</h3>
 </tbody>
 </table>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/snowbox/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
-<h4>attributions.layerAttribution</h4>
+<h4 id="attributions.layerattribution" tabindex="-1">attributions.layerAttribution</h4>
 <table>
 <thead>
 <tr>
diff --git a/docs/snowbox/plugin-draw.html b/docs/snowbox/plugin-draw.html
index df188e8ef..c3c25c62c 100644
--- a/docs/snowbox/plugin-draw.html
+++ b/docs/snowbox/plugin-draw.html
@@ -22,8 +22,8 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Draw</h1>
-<h2>Scope</h2>
+    <h1 id="draw" tabindex="-1">Draw</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The draw plugin allows users to draw features on the map. Drawn features may be edited and deleted.</p>
 <p>Currently supported OpenLayers geometry types:</p>
 <ul>
@@ -33,15 +33,15 @@ <h2>Scope</h2>
 <li><code>'Polygon'</code></li>
 </ul>
 <p>Also, <code>'Text'</code> is supported which is modeled as an OpenLayers <code>'Point'</code>. This is no default feature, so it must be specified in the configuration to use it.</p>
-<h2>User instructions for Text Mode</h2>
+<h2 id="user-instructions-for-text-mode" tabindex="-1">User instructions for Text Mode</h2>
 <p>The interaction with text features is not intuitive, which is why the text feature should come with instructions for the users:</p>
-<h3>Edit</h3>
+<h3 id="edit" tabindex="-1">Edit</h3>
 <p>To edit the text or the placement of the text feature, the user must click on the center of the text to select the point geometry below it. After selecting it, the user can move the point by keeping the left mouse button pressed, or edit the text in the input field that opens with selecting the feature. If more than one text size is specified in the configuration, the user can change the text size with a slider.</p>
-<h3>Delete</h3>
+<h3 id="delete" tabindex="-1">Delete</h3>
 <p>To delete the text, the user must either click on the point at the center of the text or use CTRL + left mouse button to open a box over all features that he or she wants to delete.</p>
-<h2>Configuration</h2>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
 <p>The styling of the drawn features can be configured to overwrite the default ol-style. Configuration is oriented around the <a href="https://openlayers.org/en/latest/apidoc/module-ol_style_Style.html#~StyleLike">OpenLayers styles</a>.</p>
-<h3>draw</h3>
+<h3 id="draw-1" tabindex="-1">draw</h3>
 <table>
 <thead>
 <tr>
@@ -69,7 +69,7 @@ <h3>draw</h3>
 </tbody>
 </table>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/snowbox/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
-<h5>draw.textStyle</h5>
+<h5 id="draw.textstyle" tabindex="-1">draw.textStyle</h5>
 <table>
 <thead>
 <tr>
@@ -91,7 +91,7 @@ <h5>draw.textStyle</h5>
 </tr>
 </tbody>
 </table>
-<h5>draw.textStyle.font</h5>
+<h5 id="draw.textstyle.font" tabindex="-1">draw.textStyle.font</h5>
 <table>
 <thead>
 <tr>
@@ -113,7 +113,7 @@ <h5>draw.textStyle.font</h5>
 </tr>
 </tbody>
 </table>
-<h4>draw.style (by example)</h4>
+<h4 id="draw.style-(by-example)" tabindex="-1">draw.style (by example)</h4>
 <p>The <code>@masterportal/masterportalapi</code> has vectorStyles in development. As soon as that's done, we shall use its styling syntax and methods.</p>
 <p>For the time being, please use this example as a rough reference as to what can currently be done.</p>
 <pre><code class="language-json">{
@@ -141,14 +141,14 @@ <h4>draw.style (by example)</h4>
   }
 }
 </code></pre>
-<h2>Store</h2>
-<h3>State</h3>
+<h2 id="store" tabindex="-1">Store</h2>
+<h3 id="state" tabindex="-1">State</h3>
 <pre><code class="language-js">map.subscribe('plugin/draw/featureCollection', (featureCollection) =&gt; {
   /* Your code. */
 })
 </code></pre>
 <p>The returned featureCollection is a <a href="https://geojson.org/">GeoJSON</a> FeatureCollection. It includes all drawn features and updates on changes.</p>
-<h2>Actions</h2>
+<h2 id="actions" tabindex="-1">Actions</h2>
 <pre><code class="language-js">map.$store.dispatch('plugin/draw/addFeatures', {
   geoJSON: {
     type: 'FeatureCollection',
diff --git a/docs/snowbox/plugin-export.html b/docs/snowbox/plugin-export.html
index 544acedcb..5c16361ef 100644
--- a/docs/snowbox/plugin-export.html
+++ b/docs/snowbox/plugin-export.html
@@ -22,11 +22,11 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Export</h1>
-<h2>Scope</h2>
+    <h1 id="export" tabindex="-1">Export</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The Export plugin offers users to download the currently visible map canvas in a variety of file formats and by a variety of methods.</p>
-<h2>Configuration</h2>
-<h3>export</h3>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
+<h3 id="export-1" tabindex="-1">export</h3>
 <table>
 <thead>
 <tr>
@@ -60,12 +60,12 @@ <h3>export</h3>
 </table>
 <p>To remove user control, add <code>displayComponent: false</code> to the configuration and use the following interactions.</p>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/snowbox/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
-<h3>Actions</h3>
+<h3 id="actions" tabindex="-1">Actions</h3>
 <p>To programmatically trigger a &quot;screenshot&quot;, use this action.</p>
 <pre><code class="language-js">// type is 'Png', 'Jpg', or 'Pdf'
 map.$store.dispatch('plugin/export/exportAs', type)
 </code></pre>
-<h3>State</h3>
+<h3 id="state" tabindex="-1">State</h3>
 <p>This shows how a callback can be used to show the exported data in a suitable html element. The value of the <code>screenshot</code> variable is a base64-encoded string.</p>
 <pre><code class="language-js">const someElement = // ... however you retrieve your html element
   map.subscribe('plugin/export/exportedMap', (screenshot) =&gt;
diff --git a/docs/snowbox/plugin-fullscreen.html b/docs/snowbox/plugin-fullscreen.html
index ef67a60a5..0d00873d8 100644
--- a/docs/snowbox/plugin-fullscreen.html
+++ b/docs/snowbox/plugin-fullscreen.html
@@ -22,11 +22,11 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Fullscreen</h1>
-<h2>Scope</h2>
+    <h1 id="fullscreen" tabindex="-1">Fullscreen</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The fullscreen plugin allows viewing the map in fullscreen mode. It relies solely on the <a href="https://developer.mozilla.org/en-US/docs/Web/API/Fullscreen_API">HTML Fullscreen API</a>, where you can also find more about browser support.</p>
-<h2>Configuration</h2>
-<h3>fullscreen</h3>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
+<h3 id="fullscreen-1" tabindex="-1">fullscreen</h3>
 <table>
 <thead>
 <tr>
@@ -49,8 +49,8 @@ <h3>fullscreen</h3>
 </tbody>
 </table>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/snowbox/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
-<h2>Store</h2>
-<h3>State</h3>
+<h2 id="store" tabindex="-1">Store</h2>
+<h3 id="state" tabindex="-1">State</h3>
 <pre><code class="language-js">map.subscribe('plugin/fullscreen/isInFullscreen', (isInFullscreen) =&gt; {
   /* Your code. */
 })
diff --git a/docs/snowbox/plugin-geo-location.html b/docs/snowbox/plugin-geo-location.html
index 6a482b2ab..c5cad3201 100644
--- a/docs/snowbox/plugin-geo-location.html
+++ b/docs/snowbox/plugin-geo-location.html
@@ -22,13 +22,13 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>GeoLocation</h1>
-<h2>Scope</h2>
+    <h1 id="geolocation" tabindex="-1">GeoLocation</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The GeoLocation plugin is responsible for collecting and displaying a user's GPS location. It is shown as a crosshair mark on the map.
 The tracking can be triggered initially on startup or via a button. This behavior can be controlled by setting <code>checkLocationInitially</code> to
 either <code>true</code> or <code>false</code>. When a users denies the location tracking, the button for this plugin gets disabled.</p>
-<h2>Configuration</h2>
-<h4>geoLocation</h4>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
+<h4 id="geolocation-1" tabindex="-1">geoLocation</h4>
 <table>
 <thead>
 <tr>
@@ -81,7 +81,7 @@ <h4>geoLocation</h4>
 </tbody>
 </table>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/snowbox/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
-<h4>Example configuration</h4>
+<h4 id="example-configuration" tabindex="-1">Example configuration</h4>
 <pre><code class="language-json">{
   &quot;geoLocation&quot;: {
     &quot;checkLocationInitially&quot;: true,
@@ -89,8 +89,8 @@ <h4>Example configuration</h4>
   }
 }
 </code></pre>
-<h2>Store</h2>
-<h3>State</h3>
+<h2 id="store" tabindex="-1">Store</h2>
+<h3 id="state" tabindex="-1">State</h3>
 <p>If the access to an users location has been granted, the coordinates get stored in the <code>position</code> state value. This value can be subscribed through the path <code>'plugin/geoLocation/position'</code>.</p>
 <pre><code class="language-js">map.subscribe('plugin/geoLocation/position', (position) =&gt; {
   /* Your code here */
diff --git a/docs/snowbox/plugin-gfi.html b/docs/snowbox/plugin-gfi.html
index 542ea566e..21d0d5030 100644
--- a/docs/snowbox/plugin-gfi.html
+++ b/docs/snowbox/plugin-gfi.html
@@ -22,14 +22,14 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>GFI</h1>
-<h2>Scope</h2>
+    <h1 id="gfi" tabindex="-1">GFI</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The GFI plugin can be used to fetch and optionally display GFI (GetFeatureInfo) from WMS and WFS services as well as layers based on GeoJSON files. In a first step, the information is stored in the VueX store to allow for easy access. Display is optional and quite obstructive within the map client.</p>
 <blockquote>
 <p>⚠️ The display feature is currently not meant for production. Please use data bindings for display to avoid obstructing the map client.</p>
 </blockquote>
-<h3>Configuration</h3>
-<h4>gfi</h4>
+<h3 id="configuration" tabindex="-1">Configuration</h3>
+<h4 id="gfi-1" tabindex="-1">gfi</h4>
 <table>
 <thead>
 <tr>
@@ -92,7 +92,7 @@ <h4>gfi</h4>
 </tbody>
 </table>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/snowbox/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
-<h5>gfi.gfiLayerConfiguration</h5>
+<h5 id="gfi.gfilayerconfiguration" tabindex="-1">gfi.gfiLayerConfiguration</h5>
 <table>
 <thead>
 <tr>
@@ -156,7 +156,7 @@ <h5>gfi.gfiLayerConfiguration</h5>
 </tr>
 </tbody>
 </table>
-<h5>gfi.customHighlightStyle</h5>
+<h5 id="gfi.customhighlightstyle" tabindex="-1">gfi.customHighlightStyle</h5>
 <table>
 <thead>
 <tr>
@@ -178,7 +178,7 @@ <h5>gfi.customHighlightStyle</h5>
 </tr>
 </tbody>
 </table>
-<h5>gfi.featureList</h5>
+<h5 id="gfi.featurelist" tabindex="-1">gfi.featureList</h5>
 <table>
 <thead>
 <tr>
@@ -210,7 +210,7 @@ <h5>gfi.featureList</h5>
 </tr>
 </tbody>
 </table>
-<h4>Example configuration</h4>
+<h4 id="example-configuration" tabindex="-1">Example configuration</h4>
 <pre><code class="language-js">layers: {
   [serviceId]: {
     geometry: true,
@@ -235,8 +235,8 @@ <h4>Example configuration</h4>
   },
 },
 </code></pre>
-<h2>Store</h2>
-<h3>State</h3>
+<h2 id="store" tabindex="-1">Store</h2>
+<h3 id="state" tabindex="-1">State</h3>
 <p>If a successful query has been sent and a response has been received, the result will be saved in the store and can be subscribed through the path <code>'plugin/gfi/featureInformation'</code>. If, however, a query for a layer fails, a <code>Symbol</code> containing the error will be saved in the store instead to indicate the error.</p>
 <p>The exact value of <code>featureInformation</code> may vary wildly depending on the service used, but is always given as json representation here.</p>
 <pre><code class="language-js">map.subscribe('plugin/gfi/featureInformation', (featureInformation) =&gt; {
diff --git a/docs/snowbox/plugin-icon-menu.html b/docs/snowbox/plugin-icon-menu.html
index dccf342ed..510295a08 100644
--- a/docs/snowbox/plugin-icon-menu.html
+++ b/docs/snowbox/plugin-icon-menu.html
@@ -22,13 +22,13 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>IconMenu</h1>
+    <h1 id="iconmenu" tabindex="-1">IconMenu</h1>
 <p>The IconMenu offers an icon-button based menu to open various functionality as cards. This way, obstructive UI can be hidden until the user desires to open it. Please use carefully – users may have issues finding process-relevant buttons/interactions if you hide them here.<br>
 Currently, the IconMenu should only be rendered with <code>layoutTag</code> set to <code>NineLayoutTag.TOP_RIGHT</code>.</p>
-<h2>Scope</h2>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>It is meant for additional information/functionality (legend, other layers) or power users in non-public clients.</p>
 <p><em>Please note that the average user has never seen the client before and just wants to get done with it, not learn a map client.</em></p>
-<h2>Configuration</h2>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
 <blockquote>
 <p>⚠️ This plugin can't be configured with the <code>mapConfiguration</code>, but is configured during client construction. Currently, no way exists to add plugins to it after the build took place.</p>
 </blockquote>
@@ -60,7 +60,7 @@ <h2>Configuration</h2>
   ],
 }
 </code></pre>
-<h3>menus</h3>
+<h3 id="menus" tabindex="-1">menus</h3>
 <p>When landscape mode is active the IconMenu is oriented horizontally. Currently, the IconMenu works fine only if there is not more than one row of Icons in landscape mode.</p>
 
     
diff --git a/docs/snowbox/plugin-layer-chooser.html b/docs/snowbox/plugin-layer-chooser.html
index 9566e0385..130cccbbf 100644
--- a/docs/snowbox/plugin-layer-chooser.html
+++ b/docs/snowbox/plugin-layer-chooser.html
@@ -22,12 +22,12 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>LayerChooser</h1>
+    <h1 id="layerchooser" tabindex="-1">LayerChooser</h1>
 <p>The tool offers layer selection to the user.</p>
-<h2>Scope</h2>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The LayerChooser offers an additive (usually Overlays, technically named with <code>type: 'mask'</code>) and an exclusive (usually background maps, <code>type: 'background'</code>) selection of layers to the users.</p>
 <p>Order of layers within a layer is currently always as initially configured.</p>
-<h2>Configuration</h2>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
 <p>The tool does not require any configuration for itself, but is based on the <code>mapConfiguration.layers</code> array. It will infer its options from there, and change layer visibility and availability depending on <code>minZoom</code> and <code>maxZoom</code>.</p>
 <p>Each object in <code>mapConfiguration.layers</code> array fits this definition:</p>
 <table>
@@ -82,7 +82,7 @@ <h2>Configuration</h2>
 </tbody>
 </table>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/snowbox/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
-<h3>mapConfiguration.layers.options</h3>
+<h3 id="mapconfiguration.layers.options" tabindex="-1">mapConfiguration.layers.options</h3>
 <p>An option wheel will appear in the layer chooser that allows opening a sub-menu with configured configuration options for the end user.</p>
 <table>
 <thead>
@@ -100,7 +100,7 @@ <h3>mapConfiguration.layers.options</h3>
 </tr>
 </tbody>
 </table>
-<h4>mapConfiguration.layers.options.layers</h4>
+<h4 id="mapconfiguration.layers.options.layers" tabindex="-1">mapConfiguration.layers.options.layers</h4>
 <p>This field is named like this to match the OGC specification for their name; that is, layers have layers that may have layers that may have layers, and so on. However, only the first level (a layer's layers) is currently implemented.</p>
 <table>
 <thead>
diff --git a/docs/snowbox/plugin-legend.html b/docs/snowbox/plugin-legend.html
index 1b092f6dd..e51935467 100644
--- a/docs/snowbox/plugin-legend.html
+++ b/docs/snowbox/plugin-legend.html
@@ -22,9 +22,9 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Legend</h1>
+    <h1 id="legend" tabindex="-1">Legend</h1>
 <p>The Legend module offers legend images as supplied by OGC services.</p>
-<h2>Configuration</h2>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/snowbox/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
 
     
diff --git a/docs/snowbox/plugin-loading-indicator.html b/docs/snowbox/plugin-loading-indicator.html
index 703a713fa..ee598c231 100644
--- a/docs/snowbox/plugin-loading-indicator.html
+++ b/docs/snowbox/plugin-loading-indicator.html
@@ -22,13 +22,13 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>LoadingIndicator</h1>
-<h2>Scope</h2>
+    <h1 id="loadingindicator" tabindex="-1">LoadingIndicator</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>A generic loading indicator that may be used by any plugin or outside procedure to indicate loading.</p>
-<h2>Configuration</h2>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/snowbox/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
-<h2>Store</h2>
-<h3>Mutations</h3>
+<h2 id="store" tabindex="-1">Store</h2>
+<h3 id="mutations" tabindex="-1">Mutations</h3>
 <pre><code class="language-js">// show loading indicator
 map.$store.commit('plugin/loadingIndicator/addLoadingKey', key)
 // hide loading indicator
@@ -37,7 +37,7 @@ <h3>Mutations</h3>
 <p><img src="./readme_loadingIndicator_example.png" alt="Loading indicator example"></p>
 <p>The key must be unique and is kept track of via a Set. It can't be added multiple times, and removing it once always removes it altogether. It is advised to use a key like <code>{my-plugin-or-application-name}-{procedure-name}</code> to avoid name conflicts. The LoadingIndicator will usually be used for asynchronous code.</p>
 <p>As such, <strong>always call <code>removeLoadingKey</code> in the <code>finally</code> section of your code</strong> to prevent hanging loading indicators.</p>
-<h3>Getters</h3>
+<h3 id="getters" tabindex="-1">Getters</h3>
 <p>You may desire to listen to whether the loader is currently being shown.</p>
 <table>
 <thead>
diff --git a/docs/snowbox/plugin-pins.html b/docs/snowbox/plugin-pins.html
index 1985b16de..2c36045af 100644
--- a/docs/snowbox/plugin-pins.html
+++ b/docs/snowbox/plugin-pins.html
@@ -22,12 +22,12 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Pins</h1>
-<h2>Scope</h2>
+    <h1 id="pins" tabindex="-1">Pins</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The pins plugin handles marking locations. Embedding processes can then use that coordinate for further steps. The plugin may react to other plugins, especially address searches.</p>
-<h2>Configuration</h2>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
 <p>The usage of <code>displayComponent</code> has no influence on the creation of Pins on the Map if this plugin is being used.</p>
-<h3>pins</h3>
+<h3 id="pins-1" tabindex="-1">pins</h3>
 <table>
 <thead>
 <tr>
@@ -84,7 +84,7 @@ <h3>pins</h3>
 </tr>
 </tbody>
 </table>
-<h4>pins.appearOnClick</h4>
+<h4 id="pins.appearonclick" tabindex="-1">pins.appearOnClick</h4>
 <table>
 <thead>
 <tr>
@@ -106,7 +106,7 @@ <h4>pins.appearOnClick</h4>
 </tr>
 </tbody>
 </table>
-<h4>pins.initial</h4>
+<h4 id="pins.initial" tabindex="-1">pins.initial</h4>
 <table>
 <thead>
 <tr>
@@ -133,7 +133,7 @@ <h4>pins.initial</h4>
 </tr>
 </tbody>
 </table>
-<h4>pins.style</h4>
+<h4 id="pins.style" tabindex="-1">pins.style</h4>
 <table>
 <thead>
 <tr>
@@ -155,8 +155,8 @@ <h4>pins.style</h4>
 </tr>
 </tbody>
 </table>
-<h2>Store</h2>
-<h3>State</h3>
+<h2 id="store" tabindex="-1">Store</h2>
+<h3 id="state" tabindex="-1">State</h3>
 <pre><code class="language-js">map.subscribe('plugin/pins/transformedCoordinate', (pinCoordinate) =&gt; {
   /* Your Code. */
 })
diff --git a/docs/snowbox/plugin-reverse-geocoder.html b/docs/snowbox/plugin-reverse-geocoder.html
index ba1db2ce2..855c2e77a 100644
--- a/docs/snowbox/plugin-reverse-geocoder.html
+++ b/docs/snowbox/plugin-reverse-geocoder.html
@@ -22,12 +22,12 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Reverse Geocoder</h1>
-<h2>Scope</h2>
+    <h1 id="reverse-geocoder" tabindex="-1">Reverse Geocoder</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>Reverse Geocoder Plugin that turns coordinates into addresses via a WPS. It does not offer any UI by itself.</p>
 <p>This module has been written for the HH WPS service. The return format is custom and no other WPS are currently supported. Please mind this when trying to use this plugin with any other WPS. For usage with other WPS, those must either fit the HH WPS, or a generalization of this plugin is required.</p>
-<h2>Configuration</h2>
-<h3>reverseGeocoder</h3>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
+<h3 id="reversegeocoder" tabindex="-1">reverseGeocoder</h3>
 <table>
 <thead>
 <tr>
@@ -69,9 +69,9 @@ <h3>reverseGeocoder</h3>
 </tr>
 </tbody>
 </table>
-<h2>Store</h2>
+<h2 id="store" tabindex="-1">Store</h2>
 <p>The ReverseGeocoder plugin does not hold any state.</p>
-<h3>Actions</h3>
+<h3 id="actions" tabindex="-1">Actions</h3>
 <pre><code class="language-js">// result contains the resolved address (exact format depends on WPS)
 const result = await map.$store.dispatch(
   'plugin/reverseGeocoder/reverseGeocode',
diff --git a/docs/snowbox/plugin-scale.html b/docs/snowbox/plugin-scale.html
index a818a819a..8f74cbf29 100644
--- a/docs/snowbox/plugin-scale.html
+++ b/docs/snowbox/plugin-scale.html
@@ -22,14 +22,14 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Scale</h1>
+    <h1 id="scale" tabindex="-1">Scale</h1>
 <blockquote>
 <p>⚠ The Scale plugin is currently meant for passive usage only. It's API has not yet been finally defined, and is subject to change without further notice.</p>
 </blockquote>
-<h2>Scope</h2>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The scale plugin shows the current map resolution as relative scale (1:x) and/or absolute scale (a drawn line has length x units).</p>
-<h2>Configuration</h2>
-<h3>scale</h3>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
+<h3 id="scale-1" tabindex="-1">scale</h3>
 <table>
 <thead>
 <tr>
diff --git a/docs/snowbox/plugin-toast.html b/docs/snowbox/plugin-toast.html
index e65f74762..8575fb2ce 100644
--- a/docs/snowbox/plugin-toast.html
+++ b/docs/snowbox/plugin-toast.html
@@ -22,12 +22,12 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Toast</h1>
-<h2>Scope</h2>
+    <h1 id="toast" tabindex="-1">Toast</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The toast plugin offers global functionality to display text messages to the user. These are the classic success, warning, info, and error messages, helping to understand what's going on or why something happened.</p>
-<h2>Configuration</h2>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
 <p>Please check the vuetify documentation to override the success, warning, info, or errors colors in general. To affect only this plugin, the following configuration parameters can be added to either the plugin instantiation or the mapConfiguration:</p>
-<h3>toast</h3>
+<h3 id="toast-1" tabindex="-1">toast</h3>
 <table>
 <thead>
 <tr>
@@ -60,7 +60,7 @@ <h3>toast</h3>
 </tbody>
 </table>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/snowbox/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
-<h4>toast.toastStyle</h4>
+<h4 id="toast.toaststyle" tabindex="-1">toast.toastStyle</h4>
 <table>
 <thead>
 <tr>
@@ -82,12 +82,12 @@ <h4>toast.toastStyle</h4>
 </tr>
 </tbody>
 </table>
-<h2>Store</h2>
-<h3>Actions</h3>
+<h2 id="store" tabindex="-1">Store</h2>
+<h3 id="actions" tabindex="-1">Actions</h3>
 <p>New entries are made via action. They are either dismissed after a timeout or by user interaction.</p>
 <pre><code class="language-js">map.$store.dispatch('plugin/toast/addToast', payload)
 </code></pre>
-<h4>Payload structure</h4>
+<h4 id="payload-structure" tabindex="-1">Payload structure</h4>
 <table>
 <thead>
 <tr>
@@ -124,7 +124,7 @@ <h4>Payload structure</h4>
 </tr>
 </tbody>
 </table>
-<h4>Usage example</h4>
+<h4 id="usage-example" tabindex="-1">Usage example</h4>
 <pre><code class="language-js">map.$store.dispatch('plugin/toast/addToast', {
   type: 'warning',
   text: 'Wrong hammer for screw.',
diff --git a/docs/snowbox/plugin-zoom.html b/docs/snowbox/plugin-zoom.html
index 6566d72c5..ce5b642ac 100644
--- a/docs/snowbox/plugin-zoom.html
+++ b/docs/snowbox/plugin-zoom.html
@@ -22,10 +22,10 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Zoom</h1>
-<h2>Scope</h2>
+    <h1 id="zoom" tabindex="-1">Zoom</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The Zoom plugin offers functionality regarding map zooming.</p>
-<h2>Configuration</h2>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
 <p>The Zoom plugin offers a plus/minus button, and will adjust itself to the map's zoom settings on initialization.<br>
 It can be configured as followed.</p>
 <table>
@@ -55,8 +55,8 @@ <h2>Configuration</h2>
 </tbody>
 </table>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/snowbox/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
-<h2>Store</h2>
-<h3>State</h3>
+<h2 id="store" tabindex="-1">Store</h2>
+<h3 id="state" tabindex="-1">State</h3>
 <p>The map's zoom level can be listened to.</p>
 <table>
 <thead>
@@ -88,7 +88,7 @@ <h3>State</h3>
   /* This code is called on any zoomLevel update. */
 })
 </code></pre>
-<h3>Getters</h3>
+<h3 id="getters" tabindex="-1">Getters</h3>
 <table>
 <thead>
 <tr>
@@ -117,7 +117,7 @@ <h3>Getters</h3>
   }
 )
 </code></pre>
-<h3>Actions</h3>
+<h3 id="actions" tabindex="-1">Actions</h3>
 <p>The zoomLevel can be set programmatically.</p>
 <pre><code class="language-js">map.$store.dispatch('plugin/zoom/setZoomLevel', zoomLevelNumber)
 map.$store.dispatch('plugin/zoom/increaseZoomLevel')
diff --git a/docs/textLocator/client-textLocator.html b/docs/textLocator/client-textLocator.html
index 9a353daa2..f04d7e859 100644
--- a/docs/textLocator/client-textLocator.html
+++ b/docs/textLocator/client-textLocator.html
@@ -22,7 +22,7 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>TextLocator MapClient API 🗺️ <code>@polar/client-text-locator</code></h1>
+    <h1 id="textlocator-mapclient-api-%F0%9F%97%BA%EF%B8%8F-%40polar%2Fclient-text-locator" tabindex="-1">TextLocator MapClient API 🗺️ <code>@polar/client-text-locator</code></h1>
 <p>There is no API to this package; it is not configurable, but delivers a hostable website containing the client in question. All reconfiguration must be done in the source code and requires a new build.</p>
 <p>When configuring before building, please mind that the <code>index.html</code> in the source folder contains configuration parameters that are later bundled.</p>
 
diff --git a/docs/textLocator/core.html b/docs/textLocator/core.html
index 30ed9bbdf..aa70cc755 100644
--- a/docs/textLocator/core.html
+++ b/docs/textLocator/core.html
@@ -22,8 +22,8 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Core</h1>
-<h2>Scope</h2>
+    <h1 id="core" tabindex="-1">Core</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The client's core is the base package to create clients in the POLAR environment.</p>
 <p>It offers this functionality:</p>
 <ul>
@@ -31,15 +31,15 @@ <h2>Scope</h2>
 <li>@masterportal/masterportalapi functionality</li>
 <li>Localization mechanism</li>
 </ul>
-<h2>Interaction</h2>
+<h2 id="interaction" tabindex="-1">Interaction</h2>
 <p>If a client is rendered as part of another page, the zoom and drag-pan behaviour is different to if the client is rendered as complete page.<br>
 If it's part of another page, drag-panning on mobile devices is only usable if at least two fingers are being used while on desktop clients the user can only zoom if using the respective platform modifier key (e.g. CTRL).</p>
 <p>It is important to note that the behaviour will be desktop-like on larger touchscreen devices (e.g. tablets).</p>
-<h2>Initialization / Configuration</h2>
+<h2 id="initialization-%2F-configuration" tabindex="-1">Initialization / Configuration</h2>
 <p>It depends on the client how exactly the initialization will take place for the embedding programmer. However, the core mechanism remains the same.</p>
 <p>The exported default object is an extended masterportalAPI, adding the <code>addPlugins</code> and extending the <code>createMap</code> functions. For masterportalAPI details, <a href="https://bitbucket.org/geowerkstatt-hamburg/masterportalapi/src/master/">see their repository</a>.</p>
 <p>To be able to see the map in production mode, the imported stylesheet has to have the property <code>data-polar</code>. The value can be chosen arbitrarily. ⚠️ Deprecated. The new field 'stylePath' should be used instead.</p>
-<h3>addPlugins</h3>
+<h3 id="addplugins" tabindex="-1">addPlugins</h3>
 <p>Before instantiating the map, all required plugins have to be added. Depending on how you use POLAR, this may already have been done. Ready-made clients (that is, packages prefixed <code>@polar/client-</code>) come with plugins prepared. You may add further plugins or proceed with <code>createMap</code>.</p>
 <p>In case you're integrating new plugins, call <code>addPlugins</code> with an array of instances.</p>
 <pre><code class="language-js">client.addPlugins([Plugin({ pluginConfig })])
@@ -55,7 +55,7 @@ <h3>addPlugins</h3>
   })
 </code></pre>
 <p>If the storeModule features a <code>setupModule</code> action, it will be executed automatically after initialization.</p>
-<h3>createMap</h3>
+<h3 id="createmap" tabindex="-1">createMap</h3>
 <p>The map is created by calling the <code>createMap</code> method. Depending on how you use POLAR, this may already have been done, as some clients come as ready-made standalone HTML pages that do this for you.</p>
 <pre><code class="language-js">MapClient.createMap({
   // arbitrary id, must point to a div
@@ -66,7 +66,7 @@ <h3>createMap</h3>
   /* Your Code, e.g. for setting up callbacks. */
 })
 </code></pre>
-<h4>mapConfiguration</h4>
+<h4 id="mapconfiguration" tabindex="-1">mapConfiguration</h4>
 <p>The mapConfiguration allows controlling many client instance details.</p>
 <table>
 <thead>
@@ -124,7 +124,7 @@ <h4>mapConfiguration</h4>
 </tr>
 </tbody>
 </table>
-<h5>mapConfiguration.LanguageOption</h5>
+<h5 id="mapconfiguration.languageoption" tabindex="-1">mapConfiguration.LanguageOption</h5>
 <p>A language option is an object consisting of a type (its language key) and the i18next resource definition. You may e.g. decide that the texts offered in the LayerChooser do not fit the style of your client, or that they could be more precise in your situation since you're only using <em>very specific</em> overlays.</p>
 <p>An example for a LanguageOption array usable in <code>createMap</code> is this array:</p>
 <pre><code class="language-ts">const languageOptions: LanguageOption[] = [
@@ -151,7 +151,7 @@ <h5>mapConfiguration.LanguageOption</h5>
 ]
 </code></pre>
 <p>To figure out the name of the locales to override, inspect the matching plugin in GitHub's file browser. In <code>packages/plugins</code>, open the plugin you desire to override. Each plugin's <code>src</code> folder contains a <code>language.ts</code> listing all used locale keys with appropriate nesting.</p>
-<h5>mapConfiguration.extendedMasterportalapiMarkers</h5>
+<h5 id="mapconfiguration.extendedmasterportalapimarkers" tabindex="-1">mapConfiguration.extendedMasterportalapiMarkers</h5>
 <table>
 <thead>
 <tr>
@@ -193,7 +193,7 @@ <h5>mapConfiguration.extendedMasterportalapiMarkers</h5>
 </tr>
 </tbody>
 </table>
-<h6>mapConfiguration.extendedMasterportalapiMarkers.MarkerStyle</h6>
+<h6 id="mapconfiguration.extendedmasterportalapimarkers.markerstyle" tabindex="-1">mapConfiguration.extendedMasterportalapiMarkers.MarkerStyle</h6>
 <table>
 <thead>
 <tr>
@@ -281,7 +281,7 @@ <h6>mapConfiguration.extendedMasterportalapiMarkers.MarkerStyle</h6>
 </tbody>
 </table>
 </blockquote>
-<h5>mapConfiguration.LayerConf</h5>
+<h5 id="mapconfiguration.layerconf" tabindex="-1">mapConfiguration.LayerConf</h5>
 <p>The layer configuration (or: service register) is read by the masterportalAPI. The full definition can be read <a href="https://bitbucket.org/geowerkstatt-hamburg/masterportal/src/dev/doc/services.json.md">here</a>.</p>
 <p>However, not all listed services have been implemented in the masterportalAPI yet, and no documentation regarding implemented properties exists there yet.</p>
 <p>Whitelisted and confirmed parameters include:</p>
@@ -289,7 +289,7 @@ <h5>mapConfiguration.LayerConf</h5>
 <li>WMS: id, name, url, typ, format, version, transparent, layers, STYLES</li>
 <li>WFS: id, name, url, typ, outputFormat, version, featureType</li>
 </ul>
-<h6>Example services register</h6>
+<h6 id="example-services-register" tabindex="-1">Example services register</h6>
 <pre><code class="language-json">[
   {
     &quot;id&quot;: &quot;my-wfs-id&quot;,
@@ -313,7 +313,7 @@ <h6>Example services register</h6>
 ]
 </code></pre>
 <p>Since this is the base for many functions, the service ID set in this is used to reference map material in many places of the map client.</p>
-<h5>&lt;...masterportalAPI.fields&gt;</h5>
+<h5 id="%3C...masterportalapi.fields%3E" tabindex="-1">&lt;...masterportalAPI.fields&gt;</h5>
 <p>The <code>&lt;...masterportalAPI.fields&gt;</code> means that any masterportalAPI field may also be used here <em>directly</em>. The most common fields are the following ones; for more, see masterportalAPI.</p>
 <table>
 <thead>
@@ -356,10 +356,10 @@ <h5>&lt;...masterportalAPI.fields&gt;</h5>
 </tr>
 </tbody>
 </table>
-<h5>&lt;plugin.fields&gt;</h5>
-<p>Plugins in POLAR are modular components that extend the functionality of the map client. They can be added using the <a href="#addPlugins">addPlugins</a> method and configured through the <code>mapConfiguration</code> object. Each plugin has its own set of fields and options that can be customized.</p>
+<h5 id="%3Cplugin.fields%3E" tabindex="-1">&lt;plugin.fields&gt;</h5>
+<p>Plugins in POLAR are modular components that extend the functionality of the map client. They can be added using the <a href="#addplugins">addPlugins</a> method and configured through the <code>mapConfiguration</code> object. Each plugin has its own set of fields and options that can be customized.</p>
 <p>On how to configure a plugin, see the respective plugin. The configuration is given in the <code>mapConfiguration</code> object by the plugin's name as specified in its respective documentation.</p>
-<h6>Global Plugin Parameters</h6>
+<h6 id="global-plugin-parameters" tabindex="-1">Global Plugin Parameters</h6>
 <p>Most plugins honor this additional field.</p>
 <table>
 <thead>
@@ -377,7 +377,7 @@ <h6>Global Plugin Parameters</h6>
 </tr>
 </tbody>
 </table>
-<h6>Example Configuration</h6>
+<h6 id="example-configuration" tabindex="-1">Example Configuration</h6>
 <p>For example, a <code>@polar/plugin-address-search</code> plugin can be configured like this:</p>
 <pre><code class="language-js">{
   addressSearch: {
@@ -387,7 +387,7 @@ <h6>Example Configuration</h6>
   }
 }
 </code></pre>
-<h5>mapConfiguration.vuetify</h5>
+<h5 id="mapconfiguration.vuetify" tabindex="-1">mapConfiguration.vuetify</h5>
 <p>These fields let you e.g. specify a <a href="https://vuetifyjs.com/en/features/theme/">Vuetify-Theme</a>. For more options, refer to the official vuetify documentation.</p>
 <p>Additionally to the regular fields, <code>primaryContrast</code> and <code>secondaryContrast</code> are interpreted. They serve as contrast colors to their respective fields and are used for e.g. button icons.</p>
 <pre><code class="language-js">{
@@ -403,7 +403,7 @@ <h5>mapConfiguration.vuetify</h5>
   }
 }
 </code></pre>
-<h2>Store</h2>
+<h2 id="store" tabindex="-1">Store</h2>
 <p>The core module features a vuex root store that all plugin vuex modules are plugged into. However, the root contents are only relevant to plugins. It is accessible with <code>map.$store</code>, and can be used as a starting point for plugin access.</p>
 <p>To ease use, the map instance also features a <code>subscribe</code> method that will register a watcher to any state field. Please mind that only documented paths should be used, and all others are subject to change without notice.</p>
 <pre><code class="language-js">// state subscription – listening to data held by the map client
diff --git a/docs/textLocator/lib-custom-types.html b/docs/textLocator/lib-custom-types.html
index fc8188e5f..775c6e0a3 100644
--- a/docs/textLocator/lib-custom-types.html
+++ b/docs/textLocator/lib-custom-types.html
@@ -22,7 +22,7 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Custom Types</h1>
+    <h1 id="custom-types" tabindex="-1">Custom Types</h1>
 <p>This is a custom type library for overarching types. They can be used both in core, plugin, and lib packages to develop a common custom package-global type system.</p>
 <p>Keep it as small as possible and sort types where they belong, whenever possible.</p>
 
diff --git a/docs/textLocator/lib-tooltip.html b/docs/textLocator/lib-tooltip.html
index 48128c3c1..b93940163 100644
--- a/docs/textLocator/lib-tooltip.html
+++ b/docs/textLocator/lib-tooltip.html
@@ -22,7 +22,7 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>tooltip</h1>
+    <h1 id="tooltip" tabindex="-1">tooltip</h1>
 <p>Minimal package that provides a <code>div</code> element factory bound to <code>i18next</code> translations. The element can e.g. be used in <code>ol/Overlay</code>.</p>
 <pre><code class="language-js">import { getTooltip } from '@polar/lib-tooltip'
 
diff --git a/docs/textLocator/plugin-address-search.html b/docs/textLocator/plugin-address-search.html
index 8c2074fe9..0d85ba3a2 100644
--- a/docs/textLocator/plugin-address-search.html
+++ b/docs/textLocator/plugin-address-search.html
@@ -22,8 +22,8 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>AddressSearch</h1>
-<h2>Scope</h2>
+    <h1 id="addresssearch" tabindex="-1">AddressSearch</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The AddressSearch plugin allows users to search for an address. If multiple addresses are returned by services, the user is prompted to select a result.</p>
 <p>The plugin saves the chosen information as GeoJSON to the store so that following procedures may grab it or so that other plugins may use it.</p>
 <p>Currently supported services:</p>
@@ -32,8 +32,8 @@ <h2>Scope</h2>
 <li>WFS</li>
 <li>Some gazetteers/WFS-G (please request a check or try yourself, not 100% done)</li>
 </ul>
-<h2>Configuration</h2>
-<h3>addressSearch</h3>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
+<h3 id="addresssearch-1" tabindex="-1">addressSearch</h3>
 <p>The configuration allows defining and grouping services. Grouped services can be requested in a search at the same time, and one group of searches can be active at a time. When multiple searches are in a group, they may be extended with category information to make the results easier to browse.</p>
 <p>It is advised to either use one-search-per-group <em>or</em> all services in a singular group to avoid an overly complex UI. Mixed configurations may be required for more complex search requirements.</p>
 <p>In <code>categoryProperties</code> and <code>groupProperties</code>, id strings called <code>groupId</code> and <code>categoryId</code> are used. These are arbitrary strings you can introduce and reuse to group or categorize elements together. Regarding what groups and categories are, see further below.</p>
@@ -104,7 +104,7 @@ <h3>addressSearch</h3>
 </tbody>
 </table>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/textLocator/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
-<h4>addressSearch.searchMethodsObject</h4>
+<h4 id="addresssearch.searchmethodsobject" tabindex="-1">addressSearch.searchMethodsObject</h4>
 <table>
 <thead>
 <tr>
@@ -156,7 +156,7 @@ <h4>addressSearch.searchMethodsObject</h4>
 </tr>
 </tbody>
 </table>
-<h4>addressSearch.customSearchMethod</h4>
+<h4 id="addresssearch.customsearchmethod" tabindex="-1">addressSearch.customSearchMethod</h4>
 <p>This is a function with the following signature:</p>
 <pre><code>(
   // should be used to actually abort request
@@ -170,7 +170,7 @@ <h4>addressSearch.customSearchMethod</h4>
 ) =&gt; Promise&lt;FeatureCollection&gt; | never
 </code></pre>
 <p>With this, arbitrary services can be supported.</p>
-<h4>addressSearch.customSelectFunction</h4>
+<h4 id="addresssearch.customselectfunction" tabindex="-1">addressSearch.customSelectFunction</h4>
 <p>This is a function with the following signature:</p>
 <pre><code>({
   // VueX context object
@@ -182,7 +182,7 @@ <h4>addressSearch.customSelectFunction</h4>
 }) =&gt; void
 </code></pre>
 <p>With this, arbitrary click results can be supported. Please mind that undocumented mutations and actions fired in such a function are subject to change without further notice.</p>
-<h4>addressSearch.groupProperties</h4>
+<h4 id="addresssearch.groupproperties" tabindex="-1">addressSearch.groupProperties</h4>
 <table>
 <thead>
 <tr>
@@ -219,7 +219,7 @@ <h4>addressSearch.groupProperties</h4>
 </tr>
 </tbody>
 </table>
-<h4>addressSearch.categoryProperties</h4>
+<h4 id="addresssearch.categoryproperties" tabindex="-1">addressSearch.categoryProperties</h4>
 <table>
 <thead>
 <tr>
@@ -236,7 +236,7 @@ <h4>addressSearch.categoryProperties</h4>
 </tr>
 </tbody>
 </table>
-<h5>addressSearch.searchMethodsObject.queryParameters (type:common)</h5>
+<h5 id="addresssearch.searchmethodsobject.queryparameters-(type%3Acommon)" tabindex="-1">addressSearch.searchMethodsObject.queryParameters (type:common)</h5>
 <p>These fields are interpreted by all implemented services.</p>
 <table>
 <thead>
@@ -254,7 +254,7 @@ <h5>addressSearch.searchMethodsObject.queryParameters (type:common)</h5>
 </tr>
 </tbody>
 </table>
-<h5>addressSearch.searchMethodsObject.queryParameters (type:wfs)</h5>
+<h5 id="addresssearch.searchmethodsobject.queryparameters-(type%3Awfs)" tabindex="-1">addressSearch.searchMethodsObject.queryParameters (type:wfs)</h5>
 <table>
 <thead>
 <tr>
@@ -317,7 +317,7 @@ <h5>addressSearch.searchMethodsObject.queryParameters (type:wfs)</h5>
 <li>WFS 2.0.0 <code>{wildCard: &quot;%&quot;, singleChar: &quot;*&quot;, escapeChar: &quot;\&quot;}</code></li>
 <li>WFS 1.0.0 <code>{wildCard: &quot;*&quot;, singleChar: &quot;*&quot;, escape: &quot;\&quot;}</code></li>
 </ul>
-<h5>addressSearch.searchMethodsObject.queryParameters (type:gazetteer)</h5>
+<h5 id="addresssearch.searchmethodsobject.queryparameters-(type%3Agazetteer)" tabindex="-1">addressSearch.searchMethodsObject.queryParameters (type:gazetteer)</h5>
 <blockquote>
 <p>⚠️ &quot;gazetteer&quot; is deprecated. Please use &quot;mpapi&quot; instead.</p>
 </blockquote>
@@ -362,7 +362,7 @@ <h5>addressSearch.searchMethodsObject.queryParameters (type:gazetteer)</h5>
 </tr>
 </tbody>
 </table>
-<h5>addressSearch.searchMethodsObject.queryParameters (type:mpapi)</h5>
+<h5 id="addresssearch.searchmethodsobject.queryparameters-(type%3Ampapi)" tabindex="-1">addressSearch.searchMethodsObject.queryParameters (type:mpapi)</h5>
 <blockquote>
 <p><strong>Please mind that this requires a configured backend. A WFS's Stored Query is requested with predefined parameters using the <a href="https://bitbucket.org/geowerkstatt-hamburg/masterportalapi/src/master/">masterportalApi</a>. This implementation is meant for e.g. https://geodienste.hamburg.de/HH_WFS_GAGES, but works with other WFS configured in the same manner.</strong></p>
 </blockquote>
@@ -408,14 +408,14 @@ <h5>addressSearch.searchMethodsObject.queryParameters (type:mpapi)</h5>
 </tbody>
 </table>
 <p>While all fields are optional, configuring none of them will yield undefined behaviour. At least one search instruction should be set to <code>true</code>.</p>
-<h5>addressSearch.searchMethodsObject.queryParameters (type:bkg)</h5>
+<h5 id="addresssearch.searchmethodsobject.queryparameters-(type%3Abkg)" tabindex="-1">addressSearch.searchMethodsObject.queryParameters (type:bkg)</h5>
 <p>In <em>BKG</em> mode, queryParameter's key-value pairs are used in the service query. E.g. <code>{filter: { bundesland: 'Bremen' }}</code> results in the GET request URL having <code>&amp;filter=bundesland:Bremen</code> as suffix.</p>
 <p>For more options, please check the <a href="https://sg.geodatenzentrum.de/web_public/gdz/dokumentation/deu/geokodierungsdienst.pdf">official documentation</a> regarding what query parameters are interpreted.</p>
 <p>Additionally, it is possible to configure the parameters <code>accesstoken</code> (<code>Authorization</code>) or <code>apiKey</code> (custom header <code>X-Api-Key</code>) to send the described headers to the search service for authentication purposes.
 Note that this changes the request to be non-simple. To be able to use the parameters, the request has to be sent in <a href="https://developer.mozilla.org/en-US/docs/Web/API/Request/mode"><code>cors</code> mode</a> and has to support preflight request <code>OPTIONS</code>.</p>
-<h2>Store</h2>
-<h3>Mutations</h3>
-<h4>setSelectedGroupName</h4>
+<h2 id="store" tabindex="-1">Store</h2>
+<h3 id="mutations" tabindex="-1">Mutations</h3>
+<h4 id="setselectedgroupname" tabindex="-1">setSelectedGroupName</h4>
 <p>This can be used to change the selected search group by name.</p>
 <pre><code class="language-js">map.$store.commit(
   'plugin/addressSearch/setSelectedGroupName',
@@ -423,8 +423,8 @@ <h4>setSelectedGroupName</h4>
 )
 </code></pre>
 <p>Please mind that programmatically changing the search group will <em>not</em> trigger a search, unlike a search group change by the user. If you need a search after change, consider the <code>search</code> action.</p>
-<h3>Actions</h3>
-<h4>search</h4>
+<h3 id="actions" tabindex="-1">Actions</h3>
+<h4 id="search" tabindex="-1">search</h4>
 <p>This is a purely programmatical search method. It is not used by user input.</p>
 <pre><code class="language-js">map.$store.dispatch('plugin/addressSearch/search', {
   input: 'Bahnhofsstraße 12',
@@ -453,7 +453,7 @@ <h4>search</h4>
 </tr>
 </tbody>
 </table>
-<h3>State</h3>
+<h3 id="state" tabindex="-1">State</h3>
 <pre><code class="language-js">map.subscribe('plugin/addressSearch/chosenAddress', (chosenAddress) =&gt; {
   /* Your code. */
 })
diff --git a/docs/textLocator/plugin-attributions.html b/docs/textLocator/plugin-attributions.html
index 983694ad8..e23317394 100644
--- a/docs/textLocator/plugin-attributions.html
+++ b/docs/textLocator/plugin-attributions.html
@@ -22,11 +22,11 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Attributions</h1>
-<h2>Scope</h2>
+    <h1 id="attributions" tabindex="-1">Attributions</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>This plugin shows attributions (that is, legal information) regarding copyrights and sources of the currently visible layers.</p>
-<h2>Configuration</h2>
-<h3>attributions</h3>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
+<h3 id="attributions-1" tabindex="-1">attributions</h3>
 <p>All parameters are optional. However, setting neither <code>layerAttributions</code> nor <code>staticAttributions</code> results in an empty window.</p>
 <table>
 <thead>
@@ -70,7 +70,7 @@ <h3>attributions</h3>
 </tbody>
 </table>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/textLocator/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
-<h4>attributions.layerAttribution</h4>
+<h4 id="attributions.layerattribution" tabindex="-1">attributions.layerAttribution</h4>
 <table>
 <thead>
 <tr>
diff --git a/docs/textLocator/plugin-draw.html b/docs/textLocator/plugin-draw.html
index 0174a8b52..0974c1f62 100644
--- a/docs/textLocator/plugin-draw.html
+++ b/docs/textLocator/plugin-draw.html
@@ -22,8 +22,8 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Draw</h1>
-<h2>Scope</h2>
+    <h1 id="draw" tabindex="-1">Draw</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The draw plugin allows users to draw features on the map. Drawn features may be edited and deleted.</p>
 <p>Currently supported OpenLayers geometry types:</p>
 <ul>
@@ -33,15 +33,15 @@ <h2>Scope</h2>
 <li><code>'Polygon'</code></li>
 </ul>
 <p>Also, <code>'Text'</code> is supported which is modeled as an OpenLayers <code>'Point'</code>. This is no default feature, so it must be specified in the configuration to use it.</p>
-<h2>User instructions for Text Mode</h2>
+<h2 id="user-instructions-for-text-mode" tabindex="-1">User instructions for Text Mode</h2>
 <p>The interaction with text features is not intuitive, which is why the text feature should come with instructions for the users:</p>
-<h3>Edit</h3>
+<h3 id="edit" tabindex="-1">Edit</h3>
 <p>To edit the text or the placement of the text feature, the user must click on the center of the text to select the point geometry below it. After selecting it, the user can move the point by keeping the left mouse button pressed, or edit the text in the input field that opens with selecting the feature. If more than one text size is specified in the configuration, the user can change the text size with a slider.</p>
-<h3>Delete</h3>
+<h3 id="delete" tabindex="-1">Delete</h3>
 <p>To delete the text, the user must either click on the point at the center of the text or use CTRL + left mouse button to open a box over all features that he or she wants to delete.</p>
-<h2>Configuration</h2>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
 <p>The styling of the drawn features can be configured to overwrite the default ol-style. Configuration is oriented around the <a href="https://openlayers.org/en/latest/apidoc/module-ol_style_Style.html#~StyleLike">OpenLayers styles</a>.</p>
-<h3>draw</h3>
+<h3 id="draw-1" tabindex="-1">draw</h3>
 <table>
 <thead>
 <tr>
@@ -69,7 +69,7 @@ <h3>draw</h3>
 </tbody>
 </table>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/textLocator/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
-<h5>draw.textStyle</h5>
+<h5 id="draw.textstyle" tabindex="-1">draw.textStyle</h5>
 <table>
 <thead>
 <tr>
@@ -91,7 +91,7 @@ <h5>draw.textStyle</h5>
 </tr>
 </tbody>
 </table>
-<h5>draw.textStyle.font</h5>
+<h5 id="draw.textstyle.font" tabindex="-1">draw.textStyle.font</h5>
 <table>
 <thead>
 <tr>
@@ -113,7 +113,7 @@ <h5>draw.textStyle.font</h5>
 </tr>
 </tbody>
 </table>
-<h4>draw.style (by example)</h4>
+<h4 id="draw.style-(by-example)" tabindex="-1">draw.style (by example)</h4>
 <p>The <code>@masterportal/masterportalapi</code> has vectorStyles in development. As soon as that's done, we shall use its styling syntax and methods.</p>
 <p>For the time being, please use this example as a rough reference as to what can currently be done.</p>
 <pre><code class="language-json">{
@@ -141,14 +141,14 @@ <h4>draw.style (by example)</h4>
   }
 }
 </code></pre>
-<h2>Store</h2>
-<h3>State</h3>
+<h2 id="store" tabindex="-1">Store</h2>
+<h3 id="state" tabindex="-1">State</h3>
 <pre><code class="language-js">map.subscribe('plugin/draw/featureCollection', (featureCollection) =&gt; {
   /* Your code. */
 })
 </code></pre>
 <p>The returned featureCollection is a <a href="https://geojson.org/">GeoJSON</a> FeatureCollection. It includes all drawn features and updates on changes.</p>
-<h2>Actions</h2>
+<h2 id="actions" tabindex="-1">Actions</h2>
 <pre><code class="language-js">map.$store.dispatch('plugin/draw/addFeatures', {
   geoJSON: {
     type: 'FeatureCollection',
diff --git a/docs/textLocator/plugin-icon-menu.html b/docs/textLocator/plugin-icon-menu.html
index 06423227a..bdb149cf6 100644
--- a/docs/textLocator/plugin-icon-menu.html
+++ b/docs/textLocator/plugin-icon-menu.html
@@ -22,13 +22,13 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>IconMenu</h1>
+    <h1 id="iconmenu" tabindex="-1">IconMenu</h1>
 <p>The IconMenu offers an icon-button based menu to open various functionality as cards. This way, obstructive UI can be hidden until the user desires to open it. Please use carefully – users may have issues finding process-relevant buttons/interactions if you hide them here.<br>
 Currently, the IconMenu should only be rendered with <code>layoutTag</code> set to <code>NineLayoutTag.TOP_RIGHT</code>.</p>
-<h2>Scope</h2>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>It is meant for additional information/functionality (legend, other layers) or power users in non-public clients.</p>
 <p><em>Please note that the average user has never seen the client before and just wants to get done with it, not learn a map client.</em></p>
-<h2>Configuration</h2>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
 <blockquote>
 <p>⚠️ This plugin can't be configured with the <code>mapConfiguration</code>, but is configured during client construction. Currently, no way exists to add plugins to it after the build took place.</p>
 </blockquote>
@@ -60,7 +60,7 @@ <h2>Configuration</h2>
   ],
 }
 </code></pre>
-<h3>menus</h3>
+<h3 id="menus" tabindex="-1">menus</h3>
 <p>When landscape mode is active the IconMenu is oriented horizontally. Currently, the IconMenu works fine only if there is not more than one row of Icons in landscape mode.</p>
 
     
diff --git a/docs/textLocator/plugin-layer-chooser.html b/docs/textLocator/plugin-layer-chooser.html
index 2c9501586..f5b3d0571 100644
--- a/docs/textLocator/plugin-layer-chooser.html
+++ b/docs/textLocator/plugin-layer-chooser.html
@@ -22,12 +22,12 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>LayerChooser</h1>
+    <h1 id="layerchooser" tabindex="-1">LayerChooser</h1>
 <p>The tool offers layer selection to the user.</p>
-<h2>Scope</h2>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The LayerChooser offers an additive (usually Overlays, technically named with <code>type: 'mask'</code>) and an exclusive (usually background maps, <code>type: 'background'</code>) selection of layers to the users.</p>
 <p>Order of layers within a layer is currently always as initially configured.</p>
-<h2>Configuration</h2>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
 <p>The tool does not require any configuration for itself, but is based on the <code>mapConfiguration.layers</code> array. It will infer its options from there, and change layer visibility and availability depending on <code>minZoom</code> and <code>maxZoom</code>.</p>
 <p>Each object in <code>mapConfiguration.layers</code> array fits this definition:</p>
 <table>
@@ -82,7 +82,7 @@ <h2>Configuration</h2>
 </tbody>
 </table>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/textLocator/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
-<h3>mapConfiguration.layers.options</h3>
+<h3 id="mapconfiguration.layers.options" tabindex="-1">mapConfiguration.layers.options</h3>
 <p>An option wheel will appear in the layer chooser that allows opening a sub-menu with configured configuration options for the end user.</p>
 <table>
 <thead>
@@ -100,7 +100,7 @@ <h3>mapConfiguration.layers.options</h3>
 </tr>
 </tbody>
 </table>
-<h4>mapConfiguration.layers.options.layers</h4>
+<h4 id="mapconfiguration.layers.options.layers" tabindex="-1">mapConfiguration.layers.options.layers</h4>
 <p>This field is named like this to match the OGC specification for their name; that is, layers have layers that may have layers that may have layers, and so on. However, only the first level (a layer's layers) is currently implemented.</p>
 <table>
 <thead>
diff --git a/docs/textLocator/plugin-legend.html b/docs/textLocator/plugin-legend.html
index 263fdcff9..380ad57b4 100644
--- a/docs/textLocator/plugin-legend.html
+++ b/docs/textLocator/plugin-legend.html
@@ -22,9 +22,9 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Legend</h1>
+    <h1 id="legend" tabindex="-1">Legend</h1>
 <p>The Legend module offers legend images as supplied by OGC services.</p>
-<h2>Configuration</h2>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/textLocator/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
 
     
diff --git a/docs/textLocator/plugin-loading-indicator.html b/docs/textLocator/plugin-loading-indicator.html
index 862fbd11f..d802cd44e 100644
--- a/docs/textLocator/plugin-loading-indicator.html
+++ b/docs/textLocator/plugin-loading-indicator.html
@@ -22,13 +22,13 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>LoadingIndicator</h1>
-<h2>Scope</h2>
+    <h1 id="loadingindicator" tabindex="-1">LoadingIndicator</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>A generic loading indicator that may be used by any plugin or outside procedure to indicate loading.</p>
-<h2>Configuration</h2>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/textLocator/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
-<h2>Store</h2>
-<h3>Mutations</h3>
+<h2 id="store" tabindex="-1">Store</h2>
+<h3 id="mutations" tabindex="-1">Mutations</h3>
 <pre><code class="language-js">// show loading indicator
 map.$store.commit('plugin/loadingIndicator/addLoadingKey', key)
 // hide loading indicator
@@ -37,7 +37,7 @@ <h3>Mutations</h3>
 <p><img src="./readme_loadingIndicator_example.png" alt="Loading indicator example"></p>
 <p>The key must be unique and is kept track of via a Set. It can't be added multiple times, and removing it once always removes it altogether. It is advised to use a key like <code>{my-plugin-or-application-name}-{procedure-name}</code> to avoid name conflicts. The LoadingIndicator will usually be used for asynchronous code.</p>
 <p>As such, <strong>always call <code>removeLoadingKey</code> in the <code>finally</code> section of your code</strong> to prevent hanging loading indicators.</p>
-<h3>Getters</h3>
+<h3 id="getters" tabindex="-1">Getters</h3>
 <p>You may desire to listen to whether the loader is currently being shown.</p>
 <table>
 <thead>
diff --git a/docs/textLocator/plugin-scale.html b/docs/textLocator/plugin-scale.html
index c19292d05..c4ab93a96 100644
--- a/docs/textLocator/plugin-scale.html
+++ b/docs/textLocator/plugin-scale.html
@@ -22,14 +22,14 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Scale</h1>
+    <h1 id="scale" tabindex="-1">Scale</h1>
 <blockquote>
 <p>⚠ The Scale plugin is currently meant for passive usage only. It's API has not yet been finally defined, and is subject to change without further notice.</p>
 </blockquote>
-<h2>Scope</h2>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The scale plugin shows the current map resolution as relative scale (1:x) and/or absolute scale (a drawn line has length x units).</p>
-<h2>Configuration</h2>
-<h3>scale</h3>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
+<h3 id="scale-1" tabindex="-1">scale</h3>
 <table>
 <thead>
 <tr>
diff --git a/docs/textLocator/plugin-toast.html b/docs/textLocator/plugin-toast.html
index 5fc55d07e..ee07bfa3a 100644
--- a/docs/textLocator/plugin-toast.html
+++ b/docs/textLocator/plugin-toast.html
@@ -22,12 +22,12 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Toast</h1>
-<h2>Scope</h2>
+    <h1 id="toast" tabindex="-1">Toast</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The toast plugin offers global functionality to display text messages to the user. These are the classic success, warning, info, and error messages, helping to understand what's going on or why something happened.</p>
-<h2>Configuration</h2>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
 <p>Please check the vuetify documentation to override the success, warning, info, or errors colors in general. To affect only this plugin, the following configuration parameters can be added to either the plugin instantiation or the mapConfiguration:</p>
-<h3>toast</h3>
+<h3 id="toast-1" tabindex="-1">toast</h3>
 <table>
 <thead>
 <tr>
@@ -60,7 +60,7 @@ <h3>toast</h3>
 </tbody>
 </table>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/textLocator/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
-<h4>toast.toastStyle</h4>
+<h4 id="toast.toaststyle" tabindex="-1">toast.toastStyle</h4>
 <table>
 <thead>
 <tr>
@@ -82,12 +82,12 @@ <h4>toast.toastStyle</h4>
 </tr>
 </tbody>
 </table>
-<h2>Store</h2>
-<h3>Actions</h3>
+<h2 id="store" tabindex="-1">Store</h2>
+<h3 id="actions" tabindex="-1">Actions</h3>
 <p>New entries are made via action. They are either dismissed after a timeout or by user interaction.</p>
 <pre><code class="language-js">map.$store.dispatch('plugin/toast/addToast', payload)
 </code></pre>
-<h4>Payload structure</h4>
+<h4 id="payload-structure" tabindex="-1">Payload structure</h4>
 <table>
 <thead>
 <tr>
@@ -124,7 +124,7 @@ <h4>Payload structure</h4>
 </tr>
 </tbody>
 </table>
-<h4>Usage example</h4>
+<h4 id="usage-example" tabindex="-1">Usage example</h4>
 <pre><code class="language-js">map.$store.dispatch('plugin/toast/addToast', {
   type: 'warning',
   text: 'Wrong hammer for screw.',
diff --git a/docs/textLocator/plugin-zoom.html b/docs/textLocator/plugin-zoom.html
index 75c2686f0..05cae62e0 100644
--- a/docs/textLocator/plugin-zoom.html
+++ b/docs/textLocator/plugin-zoom.html
@@ -22,10 +22,10 @@
 </head>
 <body>
   <article class="markdown-body">
-    <h1>Zoom</h1>
-<h2>Scope</h2>
+    <h1 id="zoom" tabindex="-1">Zoom</h1>
+<h2 id="scope" tabindex="-1">Scope</h2>
 <p>The Zoom plugin offers functionality regarding map zooming.</p>
-<h2>Configuration</h2>
+<h2 id="configuration" tabindex="-1">Configuration</h2>
 <p>The Zoom plugin offers a plus/minus button, and will adjust itself to the map's zoom settings on initialization.<br>
 It can be configured as followed.</p>
 <table>
@@ -55,8 +55,8 @@ <h2>Configuration</h2>
 </tbody>
 </table>
 <p>For details on the <code>displayComponent</code> attribute, refer to the <a href="https://dataport.github.io/polar/docs/textLocator/core.html#global-plugin-parameters">Global Plugin Parameters</a> section of <code>@polar/core</code>.</p>
-<h2>Store</h2>
-<h3>State</h3>
+<h2 id="store" tabindex="-1">Store</h2>
+<h3 id="state" tabindex="-1">State</h3>
 <p>The map's zoom level can be listened to.</p>
 <table>
 <thead>
@@ -88,7 +88,7 @@ <h3>State</h3>
   /* This code is called on any zoomLevel update. */
 })
 </code></pre>
-<h3>Getters</h3>
+<h3 id="getters" tabindex="-1">Getters</h3>
 <table>
 <thead>
 <tr>
@@ -117,7 +117,7 @@ <h3>Getters</h3>
   }
 )
 </code></pre>
-<h3>Actions</h3>
+<h3 id="actions" tabindex="-1">Actions</h3>
 <p>The zoomLevel can be set programmatically.</p>
 <pre><code class="language-js">map.$store.dispatch('plugin/zoom/setZoomLevel', zoomLevelNumber)
 map.$store.dispatch('plugin/zoom/increaseZoomLevel')
diff --git a/node_modules/@polar/client-generic/node_modules/@polar/core/README.md b/node_modules/@polar/client-generic/node_modules/@polar/core/README.md
index e18f71ef6..b78e1e62b 100644
--- a/node_modules/@polar/client-generic/node_modules/@polar/core/README.md
+++ b/node_modules/@polar/client-generic/node_modules/@polar/core/README.md
@@ -199,7 +199,7 @@ The `<...masterportalAPI.fields>` means that any masterportalAPI field may also
 
 ##### <plugin.fields>
 
-Plugins in POLAR are modular components that extend the functionality of the map client. They can be added using the [addPlugins](#addPlugins) method and configured through the `mapConfiguration` object. Each plugin has its own set of fields and options that can be customized.
+Plugins in POLAR are modular components that extend the functionality of the map client. They can be added using the [addPlugins](#addplugins) method and configured through the `mapConfiguration` object. Each plugin has its own set of fields and options that can be customized.
 
 On how to configure a plugin, see the respective plugin. The configuration is given in the `mapConfiguration` object by the plugin's name as specified in its respective documentation.