@lion/ui 0.4.1 → 0.5.0

package/docs/fundamentals/node-tools/publish-docs/overview.md

@@ -31,7 +31,7 @@ For a Mono Repository
    ```md
    # My Pkg
 
-   [=> See Source <=](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/fundamentals/docs/deep/dir/overview.md)
+   [=> See Source <=](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/fundamentals/docs/deep/dir/overview.md)
    ```
 
 ## CLI flags
@@ -61,7 +61,7 @@ Bring the `overview.md` in a docs folder along.
 👉 `packages/[my-package]/docs/overview.md`
 
 ```md
-[=> See Source <=](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/fundamentals/docs/deep/dir/overview.md)
+[=> See Source <=](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/fundamentals/docs/deep/dir/overview.md)
 ```
 
 Add a `use-cases.md`
@@ -69,7 +69,7 @@ Add a `use-cases.md`
 👉 `packages/[my-package]/docs/use-cases.md`
 
 ```md
-[=> See Source <=](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/fundamentals/docs/deep/dir/use-cases.md)
+[=> See Source <=](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/fundamentals/docs/deep/dir/use-cases.md)
 ```
 
 So you will end up with something like this in your package.

package/docs/fundamentals/node-tools/rocket-preset-extend-lion-docs/overview.md

@@ -7,7 +7,7 @@ To do this automatically you can use this preset for [rocket](https://rocket.mod
 
 ## Features
 
-- Import lion documentation and adjust it using [remark-extend](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/fundamentals/node-tools/remark-extend/overview.md)
+- Import lion documentation and adjust it using [remark-extend](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/fundamentals/node-tools/remark-extend/overview.md)
 - Renames named imports and all it's usage
 - Adjusts import paths
 - Replace tags in template literals
@@ -38,7 +38,7 @@ export default {
 
 ## Reusing documentation
 
-To take an existing documentation you can "import" it using [remark-extend](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/fundamentals/node-tools/remark-extend/overview.md).
+To take an existing documentation you can "import" it using [remark-extend](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/fundamentals/node-tools/remark-extend/overview.md).
 
 As an example you can create `docs/components/tabs/overview.md`.
 

package/docs/fundamentals/rationales/accessibility.md

@@ -10,8 +10,8 @@ More on this topic can be found in the online panel discussion [Web Components,
 
 ## Shadow roots and accessibility
 
-Since our components and applications consist of multiple shadow roots that need to be able to reference each other, designing accessible components takes extra strategy and planning.
-A practical example: all form components inside a form need to be able to lay accessible relations for presenting feedback messages via the screen reader. For this, they need consistent designs so that all form components are interoperable. So, light dom needs to be leveraged until the [AOM specification](https://wicg.github.io/aom/explainer.html) is implemented.
+Since our components and applications consist of multiple shadow roots that need to be able to reference each other, architecting accessible components takes extra strategy and planning.
+A practical example: all form controls inside a fieldset need to be able to lay accessible id relations to their parent (the fieldset). In other words, id relations should be cross component (which usually means cross shadow root). Scenarios like these require consistent architecture, allowing all form components to be interoperable. In general, light dom needs to be leveraged until a solution for cross root aria is available. For a deeper understanding of the topic, be sure to view these [slides about cross root aria](https://github.com/home/runner/work/lion/lion/_merged_assets/_static/crossRootAriaLion.pdf).
 
 ## Some details about the form system
 
@@ -25,4 +25,4 @@ Internally, we delegate all intricacies involved in managing light dom to SlotMi
 SlotMixin automatically mediates between light dom provided by the user ('public slots') and light dom provided by the component author ('private slots').
 Also, SlotMixin allows to hook into the reactive update loop of LitElement (automatically rerendering on property changes) and it automatically respects
 the scoped registry belonging to the shadow root.
-More details about SlotMixin can be found in the [SlotMixin documentation](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/fundamentals/systems/core/SlotMixin.md)
+More details about SlotMixin can be found in the [SlotMixin documentation](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/fundamentals/systems/core/SlotMixin.md)

package/docs/fundamentals/systems/core/SlotMixin.md

@@ -145,4 +145,4 @@ This will make sure that the slot provided by the user always takes precedence a
 
 ### Default slot
 
-As can be seen in the example of [SlotFunctionResults](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/fundamentals/systems/core/#slotfunctionresults), '' can be used to add content to the default slot
+As can be seen in the example of [SlotFunctionResults](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/fundamentals/systems/core/#slotfunctionresults), '' can be used to add content to the default slot

package/docs/fundamentals/systems/core/overview.md

@@ -15,7 +15,7 @@ import { LitElement, html, render } from 'lit-element';
 
 ## Features
 
-- [function to deduplicate mixins (dedupeMixin)](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/fundamentals/systems/core/#deduping-of-mixins)
+- [function to deduplicate mixins (dedupeMixin)](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/fundamentals/systems/core/#deduping-of-mixins)
 - Mixin to handle disabled (DisabledMixin)
 - Mixin to handle disabled AND tabIndex (DisabledWithTabIndexMixin)
 - Mixin to manage auto-generated needed slot elements in light dom (SlotMixin)

package/docs/fundamentals/systems/form/formatting-and-parsing.md

@@ -23,7 +23,7 @@ Our fields can automatically format/parse/serialize user input or an input set i
 
 Below are some concrete examples of implementations of formatters and parsers mimicking a (basic) amount input.
 
-> For an actual amount input, check out [lion-input-amount](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/components/input-amount/overview.md).
+> For an actual amount input, check out [lion-input-amount](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/components/input-amount/overview.md).
 > This comes with its own formatter, parser, serializer.
 
 ### Parsers & modelValue
@@ -230,16 +230,16 @@ Below we show three flow diagrams to show the flow of formatting, serializing an
 
 Where a user changes the input with their keyboard:
 
-![Standard flow](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/fundamentals/systems/form/assets/FormatMixinDiagram-1.svg 'Standard flow')
+![Standard flow](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/fundamentals/systems/form/assets/FormatMixinDiagram-1.svg 'Standard flow')
 
 ### Unparseable flow
 
 Where a user sets the input to something that is not parseable by the parser:
 
-![Unparseable flow](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/fundamentals/systems/form/assets/FormatMixinDiagram-2.svg 'Unparseable flow')
+![Unparseable flow](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/fundamentals/systems/form/assets/FormatMixinDiagram-2.svg 'Unparseable flow')
 
 ### Imperative / programmatic flow
 
 Where the developer sets the modelValue of the input programmatically:
 
-![Imperative flow](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/fundamentals/systems/form/assets/FormatMixinDiagram-3.svg 'Imperative flow')
+![Imperative flow](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/fundamentals/systems/form/assets/FormatMixinDiagram-3.svg 'Imperative flow')

package/docs/fundamentals/systems/form/model-value.md

@@ -21,7 +21,7 @@ level, via:
 > Internal/private concepts like viewValue, formattedValue, serializedValue are therefore not
 > recommended as a means of interaction.
 
-For more information about parsing and the Unparseable type, see [Formatting and Parsing](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/fundamentals/systems/form/formatting-and-parsing.md)
+For more information about parsing and the Unparseable type, see [Formatting and Parsing](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/fundamentals/systems/form/formatting-and-parsing.md)
 
 ### Event meta
 

package/docs/fundamentals/systems/form/overview.md

@@ -20,9 +20,9 @@ Fields (think of an input, textarea, select) are the actual form controls the en
 
 On top of this, they feature:
 
-- [formatting/parsing/serializing](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/fundamentals/systems/form/formatting-and-parsing.md) of view values.
-- Advanced [validation](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/fundamentals/systems/form/validate.md) possibilities.
-- Creation of advanced user interaction scenarios via [interaction states](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/fundamentals/systems/form/interaction-states.md).
+- [formatting/parsing/serializing](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/fundamentals/systems/form/formatting-and-parsing.md) of view values.
+- Advanced [validation](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/fundamentals/systems/form/validate.md) possibilities.
+- Creation of advanced user interaction scenarios via [interaction states](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/fundamentals/systems/form/interaction-states.md).
 - Provision of labels and help texts in an easy, declarative manner.
 - Accessibility out of the box.
 - Advanced styling possibilities: map your own Design System to the internal HTML structure.
@@ -31,33 +31,33 @@ On top of this, they feature:
 
 ### Platform fields (wrappers)
 
-- [LionInput](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/components/input/overview.md), a wrapper for `<input>`.
-- [LionTextarea](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/components/textarea/overview.md), a wrapper for `<textarea>`.
-- [LionSelect](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/components/select/overview.md), a wrapper for `<select>`.
+- [LionInput](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/components/input/overview.md), a wrapper for `<input>`.
+- [LionTextarea](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/components/textarea/overview.md), a wrapper for `<textarea>`.
+- [LionSelect](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/components/select/overview.md), a wrapper for `<select>`.
 
 ### Custom fields (wrappers)
 
-Whenever a native form control doesn't exist or is not sufficient, a [custom form field](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/guides/how-to/create-a-custom-field.md) should be created. One could think of components like:
+Whenever a native form control doesn't exist or is not sufficient, a [custom form field](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/guides/how-to/create-a-custom-field.md) should be created. One could think of components like:
 
-- [LionCombobox](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/components/combobox/overview.md), a custom implementation of a combobox.
-- [LionDate](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/components/input-date/overview.md), an alternative for `<input type="date">`.
-- [LionDatepicker](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/components/input-datepicker/overview.md), an alternative for `<input type="date">` including a calendar dropdown.
-- [LionListbox](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/components/listbox/overview.md), a custom implementation of a listbox.
-- [LionInputAmount](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/components/input-amount/overview.md), an alternative for `<input type="number">` special for amounts.
-- [LionInputEmail](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/components/input-email/overview.md), an alternative for `<input type="email">`.
-- [LionInputIban](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/components/input-iban/overview.md), an ING specific for an input with IBAN numbers.
-- [LionInputRange](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/components/input-range/overview.md), an alternative for `<input type="range">`.
-- [LionInputStepper](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/components/input-stepper/overview.md), an alternative for `<input type="number">`.
-- [LionSelectRich](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/components/select-rich/overview.md), an alternative for `<select>` with multiline options.
+- [LionCombobox](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/components/combobox/overview.md), a custom implementation of a combobox.
+- [LionDate](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/components/input-date/overview.md), an alternative for `<input type="date">`.
+- [LionDatepicker](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/components/input-datepicker/overview.md), an alternative for `<input type="date">` including a calendar dropdown.
+- [LionListbox](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/components/listbox/overview.md), a custom implementation of a listbox.
+- [LionInputAmount](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/components/input-amount/overview.md), an alternative for `<input type="number">` special for amounts.
+- [LionInputEmail](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/components/input-email/overview.md), an alternative for `<input type="email">`.
+- [LionInputIban](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/components/input-iban/overview.md), an ING specific for an input with IBAN numbers.
+- [LionInputRange](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/components/input-range/overview.md), an alternative for `<input type="range">`.
+- [LionInputStepper](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/components/input-stepper/overview.md), an alternative for `<input type="number">`.
+- [LionSelectRich](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/components/select-rich/overview.md), an alternative for `<select>` with multiline options.
 
 ### Choice Input Fields
 
 For form controls which return a `checked-state` you can use the `lion-choice-input` mixin. It is used in:
 
-- [LionCheckbox](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/components/checkbox-group/overview.md), a wrapper for `<input type="checkbox">`.
+- [LionCheckbox](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/components/checkbox-group/overview.md), a wrapper for `<input type="checkbox">`.
 - LionOption, an alternative for `<option>`.
-- [LionRadio](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/components/radio-group/overview.md), a wrapper for `<input type="radio">`.
-- [LionSwitch](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/components/switch/overview.md), a custom implementation of a switch.
+- [LionRadio](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/components/radio-group/overview.md), a wrapper for `<input type="radio">`.
+- [LionSwitch](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/components/switch/overview.md), a custom implementation of a switch.
 
 Which contains the following features:
 
@@ -69,14 +69,14 @@ Which contains the following features:
 
 Fieldsets are groups of fields. They can be considered fields on their own as well, since they partly share the normalized API via `FormControlMixin`. Fieldsets are the basis for:
 
-- [LionFieldset](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/components/fieldset/overview.md), a wrapper around multiple input fields or other fieldsets.
-- [LionForm](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/components/form/overview.md), enhances the functionality of the native `<form>` component.
-- [LionCheckboxGroup](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/components/checkbox-group/overview.md), a wrapper component for multiple checkboxes.
-- [LionRadioGroup](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/components/radio-group/overview.md), a wrapper component for multiple radio inputs.
+- [LionFieldset](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/components/fieldset/overview.md), a wrapper around multiple input fields or other fieldsets.
+- [LionForm](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/components/form/overview.md), enhances the functionality of the native `<form>` component.
+- [LionCheckboxGroup](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/components/checkbox-group/overview.md), a wrapper component for multiple checkboxes.
+- [LionRadioGroup](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/components/radio-group/overview.md), a wrapper component for multiple radio inputs.
 
 ## Other Resources
 
-- [Model Value](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/fundamentals/systems/form/model-value.md)
-- [Formatting and parsing](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/fundamentals/systems/form/formatting-and-parsing.md)
-- [Interaction states](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/fundamentals/systems/form/interaction-states.md)
-- [Validation System](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/fundamentals/systems/form/validate.md)
+- [Model Value](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/fundamentals/systems/form/model-value.md)
+- [Formatting and parsing](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/fundamentals/systems/form/formatting-and-parsing.md)
+- [Interaction states](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/fundamentals/systems/form/interaction-states.md)
+- [Validation System](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/fundamentals/systems/form/validate.md)

package/docs/fundamentals/systems/form/validate.md

@@ -58,7 +58,7 @@ Validation happens on every change of `modelValue`. A change in modelValue can b
 
 ## When validation feedback will be shown
 
-Although validation happens realtime under the hood, displaying validity feedback in realtime may not always lead to the desired User Experience. Together with [interaction states](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/fundamentals/systems/form/interaction-states.md),
+Although validation happens realtime under the hood, displaying validity feedback in realtime may not always lead to the desired User Experience. Together with [interaction states](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/fundamentals/systems/form/interaction-states.md),
 validity states can determine whether a validation message should be shown along the input field.
 
 ## Assessing field validation state programmatically
@@ -346,7 +346,7 @@ export const emailValidator = () => html`
 `;
 ```
 
-### Override Default Messages
+### Override default messages with custom text
 
 To get default validation messages you need to import and call the `loadDefaultFeedbackMessages` function once in your application.
 
@@ -374,6 +374,22 @@ export const defaultMessages = () => html`
 `;
 ```
 
+### Override default messages with custom HTML
+
+Similarly to overriding the default messages with a custom text it is possible to override the messages with a custom HTML.
+
+```js preview-story
+export const defaultMessagesWithCustomHtml = () => html`
+  <lion-input
+    .validators="${[
+      new EqualsLength(4, { getMessage: () => html`<div><b>Note</b> 4 chars please...</div>` }),
+    ]}"
+    .modelValue="${'123'}"
+    label="Custom message for validator instance"
+  ></lion-input>
+`;
+```
+
 ### Override fieldName
 
 In the scenario that the default messages are correct, but you only want to change the `fieldName`, this can both be done for a single specific validator or for all at once.

package/docs/fundamentals/systems/localize/overview.md

@@ -9,15 +9,15 @@ In it's simplest form it is a function that returns the translated text for a na
 - Formatting of numbers, amounts
 - Formatting of dates
 
-Further examples and a more in depth description can be found at the [Use Cases Page](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/fundamentals/systems/localize/use-cases.md).
+Further examples and a more in depth description can be found at the [Use Cases Page](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/fundamentals/systems/localize/use-cases.md).
 
 ## Content
 
 | Feature                                  | Description                                   |
 | ---------------------------------------- | --------------------------------------------- |
-| [Translate Text](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/fundamentals/systems/localize/text.md)    | Load and translate text in multiple languages |
-| [Format Numbers](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/fundamentals/systems/localize/numbers.md) | Format numbers in multiple languages          |
-| [Format Dates](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/fundamentals/systems/localize/dates.md)     | Format dates in multiple languages            |
+| [Translate Text](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/fundamentals/systems/localize/text.md)    | Load and translate text in multiple languages |
+| [Format Numbers](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/fundamentals/systems/localize/numbers.md) | Format numbers in multiple languages          |
+| [Format Dates](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/fundamentals/systems/localize/dates.md)     | Format dates in multiple languages            |
 
 ## Installation
 

package/docs/fundamentals/systems/overlays/configuration.md

@@ -4,6 +4,7 @@
 import { html } from '@mdjs/mdjs-preview';
 import './assets/demo-el-using-overlaymixin.mjs';
 import './assets/applyDemoOverlayStyles.mjs';
+import { withDropdownConfig, withTooltipConfig } from '@lion/ui/overlays.js';
 ```
 
 The `OverlayController` has many configuration options.
@@ -68,7 +69,7 @@ export const placementGlobal = () => {
 
 ## isTooltip (placementMode: 'local')
 
-As specified in the [overlay rationale](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/fundamentals/systems/overlays/rationale.md) there are only two official types of overlays: dialogs and tooltips. And their main differences are:
+As specified in the [overlay rationale](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/fundamentals/systems/overlays/rationale.md) there are only two official types of overlays: dialogs and tooltips. And their main differences are:
 
 - Dialogs have a modal option, tooltips don’t
 - Dialogs have interactive content, tooltips don’t
@@ -373,7 +374,7 @@ Features:
 
 > Popper strictly is scoped on positioning. **It does not change the dimensions of the content node nor the invoker node**.
 > This also means that if you use the arrow feature, you are in charge of styling it properly, use the data-popper-placement attribute for this.
-> An example implementation can be found in [lion-tooltip](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/components/tooltip/overview.md), where an arrow is set by default.
+> An example implementation can be found in [lion-tooltip](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/components/tooltip/overview.md), where an arrow is set by default.
 
 To override the default options we set for local mode, you add a `popperConfig` object to the config passed to the OverlayController.
 Here's a succinct overview of some often used popper properties:

package/docs/fundamentals/systems/overlays/overview.md

@@ -6,7 +6,7 @@ Manages their position on the screen relative to other elements, including other
 
 Its purpose is to make it easy to use our Overlay System declaratively. It can be easily extended where needed, to override event listeners and more.
 
-See [lion-dialog](../../../components/dialog/overview.md) and [lion-tooltip](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/components/tooltip/overview.md) for example Web Component implementations using the Overlay System.
+See [lion-dialog](../../../components/dialog/overview.md) and [lion-tooltip](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/components/tooltip/overview.md) for example Web Component implementations using the Overlay System.
 
 ## Features
 
@@ -18,9 +18,9 @@ See [lion-dialog](../../../components/dialog/overview.md) and [lion-tooltip](htt
 - lion-overlay web component:
   - Show content when clicking the invoker
   - Have a `.config` object to set or update the OverlayController's configuration
-- [**OverlaysManager**](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/fundamentals/systems/overlays/use-cases.md#overlaysmanager), a global repository keeping track of all different types of overlays
-- [**OverlayController**](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/fundamentals/systems/overlays/use-cases.md#overlaycontroller), a single controller class for handling overlays
-- [**OverlayMixin**](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/fundamentals/systems/overlays/use-cases.md#overlaymixin), a mixin that can be used to create webcomponents that use the OverlayController under the hood
+- [**OverlaysManager**](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/fundamentals/systems/overlays/use-cases.md#overlaysmanager), a global repository keeping track of all different types of overlays
+- [**OverlayController**](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/fundamentals/systems/overlays/use-cases.md#overlaycontroller), a single controller class for handling overlays
+- [**OverlayMixin**](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/fundamentals/systems/overlays/use-cases.md#overlaymixin), a mixin that can be used to create webcomponents that use the OverlayController under the hood
 
 Usually you will use `lion-dialog` (or `lion-tooltip` if this makes more sense).
 
@@ -110,4 +110,4 @@ class MyOverlayComponent extends OverlayMixin(LitElement) {
 
 ## Rationales
 
-Please check the [system rationals](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/fundamentals/systems/overlays/rationale.md) folder, where we go more in-depth.
+Please check the [system rationals](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/fundamentals/systems/overlays/rationale.md) folder, where we go more in-depth.

package/docs/fundamentals/systems/overlays/use-cases.md

@@ -21,7 +21,7 @@ The overlay system allows to create different types of overlays like dialogs, to
 It's designed to be highly flexible, while still delivering sensible defaults.
 On top of this, the system was built having accessibility in mind.
 
-For a detailed rationale, please consult [Rationale](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/fundamentals/systems/overlays/rationale.md).
+For a detailed rationale, please consult [Rationale](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/fundamentals/systems/overlays/rationale.md).
 
 ```js preview-story
 export const main = () => html`
@@ -67,7 +67,7 @@ Global refers to overlays where the content is positioned in a global root node
 
 Overlays can be configured in many ways to suit your needs. We go in-depth into each option in the Overlay System - Configuration chapter.
 
-We also export a few [preset configuration objects](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/fundamentals/systems/overlays/configuration.md).
+We also export a few [preset configuration objects](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/fundamentals/systems/overlays/configuration.md).
 
 - withModalDialogConfig
 - withDropdownConfig

package/docs/fundamentals/tools/helpers/overview.md

@@ -9,7 +9,7 @@ Therefore, they may not have the same quality standards as our other packages.
 
 | Package                                | Description             |
 | -------------------------------------- | ----------------------- |
-| [sb-action-logger](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/fundamentals/tools/helpers/action-logger.md) | Storybook action logger |
+| [sb-action-logger](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/fundamentals/tools/helpers/action-logger.md) | Storybook action logger |
 
 ## Installation
 

package/docs/fundamentals/tools/singleton-manager/example-complex/overlayCompatibility.js

@@ -1,6 +1,5 @@
-import { OverlaysManager } from 'overlays';
+import { OverlaysManager, OverlaysManager as OverlaysManager2 } from 'overlays';
 import { singletonManager } from 'singleton-manager';
-import { OverlaysManager as OverlaysManager2 } from './node_modules/page-b/node_modules/overlays/index.js';
 
 let compatibleManager1;
 let compatibleManager2;

package/docs/fundamentals/tools/singleton-manager/overview.md

@@ -9,7 +9,7 @@ Primarily useful if two major version of a package with a singleton is used.
 npm i --save singleton-manager
 ```
 
-⚠️ You need to make SURE that only ONE version of `singleton-manager` is installed. For how see [Non Goals](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/fundamentals/tools/singleton-manager/#non-goals).
+⚠️ You need to make SURE that only ONE version of `singleton-manager` is installed. For how see [Non Goals](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/fundamentals/tools/singleton-manager/#non-goals).
 
 ### Example Singleton Users
 
@@ -159,7 +159,7 @@ Steps to reproduce:
 1. Page A click on block
 2. Page B => "Blocked: false" (even when hitting the refresh button)
 
-➡️ See [it on the example page](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/fundamentals/tools/singleton-manager/example-fail/index.md). <br>
+➡️ See [it on the example page](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/fundamentals/tools/singleton-manager/example-fail/index.md). <br>
 ➡️ See [the code](https://github.com/ing-bank/lion/tree/master/docs/fundamentals/tools/singleton-manager/example-fail/demo-app.js).
 
 ---
@@ -202,7 +202,7 @@ See it in action
 npm run start:singleton
 ```
 
-➡️ See [it on the example page](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/fundamentals/tools/singleton-manager/example-success/index.md). <br>
+➡️ See [it on the example page](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/fundamentals/tools/singleton-manager/example-success/index.md). <br>
 ➡️ See [the code](https://github.com/ing-bank/lion/tree/master/docs/fundamentals/tools/singleton-manager/example-success/demo-app.js).
 
 ---
@@ -243,7 +243,7 @@ See it in action
 npm run start:singleton-complex
 ```
 
-➡️ See [it on the example page](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/fundamentals/tools/singleton-manager/example-complex/index.md). <br>
+➡️ See [it on the example page](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/fundamentals/tools/singleton-manager/example-complex/index.md). <br>
 ➡️ See [the code](https://github.com/ing-bank/lion/tree/master/docs/fundamentals/tools/singleton-manager/example-complex/demo-app.js).
 
 ---

package/docs/guides/how-to/create-a-custom-field.md

@@ -75,9 +75,9 @@ if (!customElements.get('dummy-slider')) {
 }
 ```
 
-Custom Fields can be created in just a few steps. All you need is an interaction element (like for instance a slider, a listbox or a combobox) and connect it to the [LionField](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/components/input/overview.md).
+Custom Fields can be created in just a few steps. All you need is an interaction element (like for instance a slider, a listbox or a combobox) and connect it to the [LionField](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/components/input/overview.md).
 
-> In case you want to extend a native element, follow [Extend a native Input](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/guides/how-to/extend-a-native-input.md).
+> In case you want to extend a native element, follow [Extend a native Input](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/guides/how-to/extend-a-native-input.md).
 
 ## A) an interaction element
 
@@ -126,7 +126,7 @@ export const createAnInteractiveElement = () => {
 ## B) your LionField extension
 
 Now we want to integrate the slider in our form system to enrich the user interface, get
-validation support and all other [benefits of LionField](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/components/input/overview.md).
+validation support and all other [benefits of LionField](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/components/input/overview.md).
 We start by creating a component `<slider-field>` that extends from `LionField`.
 Then we follow the steps below:
 
@@ -139,7 +139,7 @@ Then we follow the steps below:
 
   The `user-input-changed` event is listened to by the FormatMixin: it should be regarded as the
   equivalent of the `input` event of the platform, but for custom built interaction elements.
-  You now synchronized [modelValue](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/fundamentals/systems/form/model-value.md), which can be regarded as
+  You now synchronized [modelValue](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/fundamentals/systems/form/model-value.md), which can be regarded as
   the glue to integrate all other functionality like parsing/formatting/serializing, validating,
   tracking interaction states etc.
 
@@ -147,7 +147,7 @@ Then we follow the steps below:
 > because those properties will loose their reactivity (they won't be considered anymore in the
 > update loop of LitElement).
 > Whenever a .modelValue/.formattedValue/.serializedValue needs to be computed, use
-> [parser/formatter/serializer](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/fundamentals/systems/form/formatting-and-parsing.md)
+> [parser/formatter/serializer](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/fundamentals/systems/form/formatting-and-parsing.md)
 
 Implement with the following code:
 

package/docs/guides/how-to/create-a-form.md

@@ -63,7 +63,7 @@ class MyForm extends LitElement {
 }
 ```
 
-> Today, rendering to light dom is the only way to [stay accessible](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/fundamentals/rationales/accessibility.md#shadow-roots-and-accessibility).
+> Today, rendering to light dom is the only way to [stay accessible](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/fundamentals/rationales/accessibility.md#shadow-roots-and-accessibility).
 
 The registration mechanism relies on light dom by design: as soon as you do start to use shadow roots, you will notice that your form components won't register themselves anymore to their parents.
 
@@ -73,7 +73,7 @@ Extending form components is not recommended for Application Developers: it shou
 This team will add the styling and default configuration needed to make it fit the particular Design System.
 
 With the toolbox provided by the team that creates your Design System, you should be able to build all your forms. Only if you have a really good reason, look into
-[exceptional cases](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/guides/how-to/#exceptional-cases) below.
+[exceptional cases](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/guides/how-to/#exceptional-cases) below.
 
 ### Exceptional cases
 
@@ -81,8 +81,8 @@ If the form component you need is still missing, you have two options:
 
 - is it a generic primitive that should be part of Lion? Request it in [Lion discussions](https://github.com/ing-bank/lion/discussions)
 - is it a non generic component that is unique to your app?
-  - follow [create a custom field](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/guides/how-to/create-a-custom-field.md)
-  - follow [extend a native input](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/guides/how-to/extend-a-native-input.md)
+  - follow [create a custom field](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/guides/how-to/create-a-custom-field.md)
+  - follow [extend a native input](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/guides/how-to/extend-a-native-input.md)
 
 It's also possible to extend other components, like LionListbox or LionCombobox. You need to be aware that you're building on top of protected apis.
 Changing/overriding functionality is only recommended if the source code in `form-core` is fully understood.

package/docs/guides/how-to/extend-a-native-input.md

@@ -11,9 +11,9 @@ import '../../fundamentals/systems/form/assets/h-output.js';
 loadDefaultFeedbackMessages();
 ```
 
-Input fields can be created by extending [LionInput](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/components/input/overview.md).
+Input fields can be created by extending [LionInput](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/components/input/overview.md).
 
-> In case you want to wrap a custom form element, follow [Create a custom Field](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/guides/how-to/create-a-custom-field.md).
+> In case you want to wrap a custom form element, follow [Create a custom Field](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/guides/how-to/create-a-custom-field.md).
 
 For this tutorial, we create an input that wraps native `input[type=datetime-local]`.
 This is as simple as adding a type:

package/docs/guides/index.md

@@ -12,9 +12,9 @@ Developers consuming our web components inside an application (not extending the
 `Application Developers` are only allowed to interact with `public` properties and methods.
 Can be abbreviated as `AD`. Sometimes also called `Consuming Developer`.
 
-- [Definitions and Terms](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/guides/principles/definitions-and-terms.md)
-- [Styling](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/guides/principles/styling.md)
-- [Scoped Elements](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/guides/principles/scoped-elements.md)
+- [Definitions and Terms](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/guides/principles/definitions-and-terms.md)
+- [Styling](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/guides/principles/styling.md)
+- [Scoped Elements](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/guides/principles/scoped-elements.md)
 
 ## Extending Developer
 
@@ -22,13 +22,13 @@ Developers extending our web components, for instance: `class MaterialInput exte
 
 Especially for subclassers we have some extra documentation:
 
-- [Subclasser APIs](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/guides/principles/subclasser-apis.md)
-- [Extend documentation](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/blog/extending-documentation.md)
+- [Subclasser APIs](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/guides/principles/subclasser-apis.md)
+- [Extend documentation](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/blog/extending-documentation.md)
 
 ## How To
 
 Next to that we have some specific "How To" documentations.
 
-- [Get started](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/guides/how-to/get-started.md)
-- [Create a custom field](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/guides/how-to/create-a-custom-field.md)
-- [Extend a native input](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/guides/how-to/extend-a-native-input.md)
+- [Get started](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/guides/how-to/get-started.md)
+- [Create a custom field](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/guides/how-to/create-a-custom-field.md)
+- [Extend a native input](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/guides/how-to/extend-a-native-input.md)

package/docs/guides/principles/index.md

@@ -12,9 +12,9 @@ Developers consuming our web components inside an application (not extending the
 `Application Developers` are only allowed to interact with `public` properties and methods.
 Can be abbreviated as `AD`. Sometimes also called `Consuming Developer`.
 
-- [Definitions and Terms](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/guides/principles/definitions-and-terms.md)
-- [Styling](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/guides/principles/styling.md)
-- [Scoped Elements](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/guides/principles/scoped-elements.md)
+- [Definitions and Terms](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/guides/principles/definitions-and-terms.md)
+- [Styling](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/guides/principles/styling.md)
+- [Scoped Elements](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/guides/principles/scoped-elements.md)
 
 ## Extending Developer
 
@@ -22,5 +22,5 @@ Developers extending our web components, for instance: `class MaterialInput exte
 
 Especially for subclassers we have some extra documentation:
 
-- [Subclasser APIs](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/guides/principles/subclasser-apis.md)
-- [Extend documentation](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/blog/extending-documentation.md)
+- [Subclasser APIs](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/guides/principles/subclasser-apis.md)
+- [Extend documentation](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/blog/extending-documentation.md)

package/docs/guides/principles/styling.md

@@ -19,7 +19,7 @@ Examples for both categories can be found below:
 - Accessibility examples:
   - Content (for instance a caption in a table) can be `visually hidden`: it will be
     readable by screen readers, but invisible for end users.
-  - When an html table is used, we allow [subclassers](https://github.com/ing-bank/lion/blob/a447ad66a1b07a11ae83bc16db9ccd9b97069928/docs/guides/principles/subclasser-apis.md) to override the display property (`table-cell`) to `flex`. By putting the proper accessible roles (`role="cell"`) in the markup, we guarantee our markup stays accessible.
+  - When an html table is used, we allow [subclassers](https://github.com/ing-bank/lion/blob/64a1b65c989892adfbabaccd892a0af043e35b3b/docs/guides/principles/subclasser-apis.md) to override the display property (`table-cell`) to `flex`. By putting the proper accessible roles (`role="cell"`) in the markup, we guarantee our markup stays accessible.
 
 Although Lion components try to stay as unbiased as possible with regard to styling, defaults will be needed. In these cases we try to follow the platform as much as possible. If the platform doesn't provide defaults, the largest common denominator across existing UI systems is taken as a lead.
 

package/exports/types/form-core.ts

@@ -14,4 +14,8 @@ export { FormRegistrarHost } from '../../components/form-core/types/registration
 export { ElementWithParentFormGroup } from '../../components/form-core/types/registration/FormRegistrarMixinTypes.js';
 export { FormRegistrarPortalHost } from '../../components/form-core/types/registration/FormRegistrarPortalMixinTypes.js';
 export { SyncUpdatableHost } from '../../components/form-core/types/utils/SyncUpdatableMixinTypes.js';
-export { ValidateHost, ValidationType, FeedbackMessage } from '../../components/form-core/types/validate/ValidateMixinTypes.js';
+export {
+  ValidateHost,
+  ValidationType,
+  FeedbackMessage,
+} from '../../components/form-core/types/validate/ValidateMixinTypes.js';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lion/ui",
-  "version": "0.4.1",
+  "version": "0.5.0",
   "description": "A package of extendable web components",
   "license": "MIT",
   "author": "ing-bank",