@lion/ui 0.11.1 → 0.11.2

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

@@ -1,3 +1,16 @@
+---
+parts:
+  - Overview
+  - Overlays
+  - Systems
+title: 'Overlays: Overview'
+eleventyNavigation:
+  key: Systems >> Overlays >> Overview
+  title: Overview
+  order: 10
+  parent: Systems >> Overlays
+---
+
 # Systems >> Overlays >> Overview ||10
 
 Supports different types of overlays like dialogs, toasts, tooltips, dropdown, etc.
@@ -6,7 +19,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/593b753f0f99acb36ea6009677bc7fdda9184184/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/87a1cb4d5bec301af6688be2c7bf778344d2ae42/docs/components/tooltip/overview.md) for example Web Component implementations using the Overlay System.
 
 ## Features
 
@@ -18,9 +31,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/593b753f0f99acb36ea6009677bc7fdda9184184/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/593b753f0f99acb36ea6009677bc7fdda9184184/docs/fundamentals/systems/overlays/use-cases.md#overlaycontroller), a single controller class for handling overlays
-- [**OverlayMixin**](https://github.com/ing-bank/lion/blob/593b753f0f99acb36ea6009677bc7fdda9184184/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/87a1cb4d5bec301af6688be2c7bf778344d2ae42/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/87a1cb4d5bec301af6688be2c7bf778344d2ae42/docs/fundamentals/systems/overlays/use-cases.md#overlaycontroller), a single controller class for handling overlays
+- [**OverlayMixin**](https://github.com/ing-bank/lion/blob/87a1cb4d5bec301af6688be2c7bf778344d2ae42/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 +123,4 @@ class MyOverlayComponent extends OverlayMixin(LitElement) {
 
 ## Rationales
 
-Please check the [system rationals](https://github.com/ing-bank/lion/blob/593b753f0f99acb36ea6009677bc7fdda9184184/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/87a1cb4d5bec301af6688be2c7bf778344d2ae42/docs/fundamentals/systems/overlays/rationale.md) folder, where we go more in-depth.

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

@@ -1,3 +1,16 @@
+---
+parts:
+  - Rationale
+  - Overlays
+  - Systems
+title: 'Overlays: Rationale'
+eleventyNavigation:
+  key: Systems >> Overlays >> Rationale
+  title: Rationale
+  order: 30
+  parent: Systems >> Overlays
+---
+
 # Systems >> Overlays >> Rationale ||30
 
 This page describes the goal and duties of the overlay system, mainly by identifying all different

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

@@ -1,3 +1,16 @@
+---
+parts:
+  - Use Cases
+  - Overlays
+  - Systems
+title: 'Overlays: Use Cases'
+eleventyNavigation:
+  key: Systems >> Overlays >> Use Cases
+  title: Use Cases
+  order: 20
+  parent: Systems >> Overlays
+---
+
 # Systems >> Overlays >> Use Cases ||20
 
 ```js script
@@ -21,7 +34,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/593b753f0f99acb36ea6009677bc7fdda9184184/docs/fundamentals/systems/overlays/rationale.md).
+For a detailed rationale, please consult [Rationale](https://github.com/ing-bank/lion/blob/87a1cb4d5bec301af6688be2c7bf778344d2ae42/docs/fundamentals/systems/overlays/rationale.md).
 
 ```js preview-story
 export const main = () => html`
@@ -69,7 +82,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/593b753f0f99acb36ea6009677bc7fdda9184184/docs/fundamentals/systems/overlays/configuration.md).
+We also export a few [preset configuration objects](https://github.com/ing-bank/lion/blob/87a1cb4d5bec301af6688be2c7bf778344d2ae42/docs/fundamentals/systems/overlays/configuration.md).
 
 - withModalDialogConfig
 - withDropdownConfig

package/docs/fundamentals/tools/ajax/index.md

@@ -1,3 +1,15 @@
+---
+parts:
+  - Ajax
+  - Tools
+title: 'Tools: Ajax'
+eleventyNavigation:
+  key: Tools >> Ajax
+  title: Ajax
+  order: 20
+  parent: Tools
+---
+
 # Tools >> Ajax ||20
 
 -> go to Overview

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

@@ -1,3 +1,16 @@
+---
+parts:
+  - Overview
+  - Ajax
+  - Tools
+title: 'Ajax: Overview'
+eleventyNavigation:
+  key: Tools >> Ajax >> Overview
+  title: Overview
+  order: 10
+  parent: Tools >> Ajax
+---
+
 # Tools >> Ajax >> Overview ||10
 
 `Ajax` is a small wrapper around `fetch` which:

package/docs/fundamentals/tools/ajax/use-cases.md

@@ -1,3 +1,16 @@
+---
+parts:
+  - Use Cases
+  - Ajax
+  - Tools
+title: 'Ajax: Use Cases'
+eleventyNavigation:
+  key: Tools >> Ajax >> Use Cases
+  title: Use Cases
+  order: 20
+  parent: Tools >> Ajax
+---
+
 # Tools >> Ajax >> Use Cases ||20
 
 ```js script

package/docs/fundamentals/tools/helpers/action-logger.md

@@ -1,3 +1,16 @@
+---
+parts:
+  - Action Logger
+  - Helpers
+  - Tools
+title: 'Helpers: Action Logger'
+eleventyNavigation:
+  key: Tools >> Helpers >> Action Logger
+  title: Action Logger
+  order: 20
+  parent: Tools >> Helpers
+---
+
 # Tools >> Helpers >> Action Logger ||20
 
 A visual element to show action logs in demos `sb-action-logger`

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

@@ -1,3 +1,15 @@
+---
+parts:
+  - Helpers
+  - Tools
+title: 'Tools: Helpers'
+eleventyNavigation:
+  key: Tools >> Helpers
+  title: Helpers
+  order: 0
+  parent: Tools
+---
+
 # Tools >> Helpers
 
 -> go to Overview

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

@@ -1,3 +1,16 @@
+---
+parts:
+  - Overview
+  - Helpers
+  - Tools
+title: 'Helpers: Overview'
+eleventyNavigation:
+  key: Tools >> Helpers >> Overview
+  title: Overview
+  order: 10
+  parent: Tools >> Helpers
+---
+
 # Tools >> Helpers >> Overview ||10
 
 A helpers package that contains several helpers that are used inside lion but can be used outside as well.
@@ -9,7 +22,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/593b753f0f99acb36ea6009677bc7fdda9184184/docs/fundamentals/tools/helpers/action-logger.md) | Storybook action logger |
+| [sb-action-logger](https://github.com/ing-bank/lion/blob/87a1cb4d5bec301af6688be2c7bf778344d2ae42/docs/fundamentals/tools/helpers/action-logger.md) | Storybook action logger |
 
 ## Installation
 

package/docs/fundamentals/tools/index.md

@@ -1 +1,11 @@
+---
+parts:
+  - Tools
+title: Tools
+eleventyNavigation:
+  key: Tools
+  title: Tools
+  order: 20
+---
+
 # Tools ||20

package/docs/fundamentals/tools/singleton-manager/example-complex/index.md

@@ -1,3 +1,16 @@
+---
+parts:
+  - Example Complex
+  - Singleton Manager
+  - Tools
+title: 'Singleton Manager: Example Complex'
+eleventyNavigation:
+  key: Tools >> Singleton Manager >> Example Complex
+  title: Example Complex
+  order: 40
+  parent: Tools >> Singleton Manager
+---
+
 # Tools >> Singleton Manager >> Example Complex ||40
 
 In this SPA (Single Page Application) demo you will be able to reproduce the solution.

package/docs/fundamentals/tools/singleton-manager/example-fail/index.md

@@ -1,3 +1,16 @@
+---
+parts:
+  - Example Fail
+  - Singleton Manager
+  - Tools
+title: 'Singleton Manager: Example Fail'
+eleventyNavigation:
+  key: Tools >> Singleton Manager >> Example Fail
+  title: Example Fail
+  order: 20
+  parent: Tools >> Singleton Manager
+---
+
 # Tools >> Singleton Manager >> Example Fail ||20
 
 In this SPA (Single Page Application) demo you will be able to reproduce the issue.

package/docs/fundamentals/tools/singleton-manager/example-success/index.md

@@ -1,3 +1,16 @@
+---
+parts:
+  - Example Success
+  - Singleton Manager
+  - Tools
+title: 'Singleton Manager: Example Success'
+eleventyNavigation:
+  key: Tools >> Singleton Manager >> Example Success
+  title: Example Success
+  order: 30
+  parent: Tools >> Singleton Manager
+---
+
 # Tools >> Singleton Manager >> Example Success ||30
 
 In this SPA (Single Page Application) demo you will be able to reproduce the solution.

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

@@ -1,3 +1,15 @@
+---
+parts:
+  - Singleton Manager
+  - Tools
+title: 'Tools: Singleton Manager'
+eleventyNavigation:
+  key: Tools >> Singleton Manager
+  title: Singleton Manager
+  order: 20
+  parent: Tools
+---
+
 # Tools >> Singleton Manager ||20
 
 -> go to Overview

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

@@ -1,3 +1,16 @@
+---
+parts:
+  - Overview
+  - Singleton Manager
+  - Tools
+title: 'Singleton Manager: Overview'
+eleventyNavigation:
+  key: Tools >> Singleton Manager >> Overview
+  title: Overview
+  order: 10
+  parent: Tools >> Singleton Manager
+---
+
 # Tools >> Singleton Manager >> Overview ||10
 
 A singleton manager provides a way to make sure a singleton instance loaded from multiple file locations stays a singleton.
@@ -9,7 +22,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/593b753f0f99acb36ea6009677bc7fdda9184184/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/87a1cb4d5bec301af6688be2c7bf778344d2ae42/docs/fundamentals/tools/singleton-manager/#non-goals).
 
 ### Example Singleton Users
 
@@ -159,7 +172,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/593b753f0f99acb36ea6009677bc7fdda9184184/docs/fundamentals/tools/singleton-manager/example-fail/index.md). <br>
+➡️ See [it on the example page](https://github.com/ing-bank/lion/blob/87a1cb4d5bec301af6688be2c7bf778344d2ae42/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 +215,7 @@ See it in action
 npm run start:singleton
 ```
 
-➡️ See [it on the example page](https://github.com/ing-bank/lion/blob/593b753f0f99acb36ea6009677bc7fdda9184184/docs/fundamentals/tools/singleton-manager/example-success/index.md). <br>
+➡️ See [it on the example page](https://github.com/ing-bank/lion/blob/87a1cb4d5bec301af6688be2c7bf778344d2ae42/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 +256,7 @@ See it in action
 npm run start:singleton-complex
 ```
 
-➡️ See [it on the example page](https://github.com/ing-bank/lion/blob/593b753f0f99acb36ea6009677bc7fdda9184184/docs/fundamentals/tools/singleton-manager/example-complex/index.md). <br>
+➡️ See [it on the example page](https://github.com/ing-bank/lion/blob/87a1cb4d5bec301af6688be2c7bf778344d2ae42/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

@@ -1,4 +1,16 @@
-# How To >> Create a custom field ||20
+---
+parts:
+  - How To
+  - Create a custom field
+title: 'How To: Create a custom field'
+eleventyNavigation:
+  key: 'How To: Create a custom field'
+  order: 20
+  parent: How To
+  title: Create a custom field
+---
+
+# How To: Create a custom field
 
 ```js script
 import { html, css, LitElement } from '@mdjs/mdjs-preview';
@@ -75,9 +87,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/593b753f0f99acb36ea6009677bc7fdda9184184/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/87a1cb4d5bec301af6688be2c7bf778344d2ae42/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/593b753f0f99acb36ea6009677bc7fdda9184184/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/87a1cb4d5bec301af6688be2c7bf778344d2ae42/docs/guides/how-to/extend-a-native-input.md).
 
 ## A) an interaction element
 
@@ -126,7 +138,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/593b753f0f99acb36ea6009677bc7fdda9184184/docs/components/input/overview.md).
+validation support and all other [benefits of LionField](https://github.com/ing-bank/lion/blob/87a1cb4d5bec301af6688be2c7bf778344d2ae42/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 +151,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/593b753f0f99acb36ea6009677bc7fdda9184184/docs/fundamentals/systems/form/model-value.md), which can be regarded as
+  You now synchronized [modelValue](https://github.com/ing-bank/lion/blob/87a1cb4d5bec301af6688be2c7bf778344d2ae42/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 +159,7 @@ Then we follow the steps below:
 > because those properties will lose 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/593b753f0f99acb36ea6009677bc7fdda9184184/docs/fundamentals/systems/form/formatting-and-parsing.md)
+> [parser/formatter/serializer](https://github.com/ing-bank/lion/blob/87a1cb4d5bec301af6688be2c7bf778344d2ae42/docs/fundamentals/systems/form/formatting-and-parsing.md)
 
 Implement with the following code:
 

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

@@ -1,4 +1,16 @@
-# How To >> Create a form ||15
+---
+parts:
+  - How To
+  - Create a form
+title: 'How To: Create a form'
+eleventyNavigation:
+  key: 'How To: Create a form'
+  order: 15
+  parent: How To
+  title: Create a form
+---
+
+# How To: Create a form
 
 Creating your own forms as an Application Developer is really simple. Only two rules need to be followed.
 
@@ -27,7 +39,7 @@ Large or complex forms might need to be split up into multiple files. This compo
 
 In the latter case: make sure that your components don't have a shadow root. This can be achieved by rendering into Light DOM. The form 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.
 
-> Today, rendering to light dom is the only way to [stay accessible](https://github.com/ing-bank/lion/blob/593b753f0f99acb36ea6009677bc7fdda9184184/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/87a1cb4d5bec301af6688be2c7bf778344d2ae42/docs/fundamentals/rationales/accessibility.md#shadow-roots-and-accessibility).
 
 ### Example of a component that renders into Light DOM
 
@@ -74,7 +86,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/593b753f0f99acb36ea6009677bc7fdda9184184/docs/guides/how-to/#exceptional-cases) below.
+[exceptional cases](https://github.com/ing-bank/lion/blob/87a1cb4d5bec301af6688be2c7bf778344d2ae42/docs/guides/how-to/#exceptional-cases) below.
 
 ### Exceptional cases
 
@@ -82,8 +94,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/593b753f0f99acb36ea6009677bc7fdda9184184/docs/guides/how-to/create-a-custom-field.md)
-  - follow [extend a native input](https://github.com/ing-bank/lion/blob/593b753f0f99acb36ea6009677bc7fdda9184184/docs/guides/how-to/extend-a-native-input.md)
+  - follow [create a custom field](https://github.com/ing-bank/lion/blob/87a1cb4d5bec301af6688be2c7bf778344d2ae42/docs/guides/how-to/create-a-custom-field.md)
+  - follow [extend a native input](https://github.com/ing-bank/lion/blob/87a1cb4d5bec301af6688be2c7bf778344d2ae42/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

@@ -1,4 +1,16 @@
-# How To >> Extend a native input ||20
+---
+parts:
+  - How To
+  - Extend a native input
+title: 'How To: Extend a native input'
+eleventyNavigation:
+  key: 'How To: Extend a native input'
+  order: 20
+  parent: How To
+  title: Extend a native input
+---
+
+# How To: Extend a native input
 
 ```js script
 import { html } from '@mdjs/mdjs-preview';
@@ -11,9 +23,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/593b753f0f99acb36ea6009677bc7fdda9184184/docs/components/input/overview.md).
+Input fields can be created by extending [LionInput](https://github.com/ing-bank/lion/blob/87a1cb4d5bec301af6688be2c7bf778344d2ae42/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/593b753f0f99acb36ea6009677bc7fdda9184184/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/87a1cb4d5bec301af6688be2c7bf778344d2ae42/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/how-to/get-started.md

@@ -1,4 +1,16 @@
-# How To >> Get Started ||10
+---
+parts:
+  - How To
+  - Get Started
+title: 'How To: Get Started'
+eleventyNavigation:
+  key: 'How To: Get Started'
+  order: 10
+  parent: How To
+  title: Get Started
+---
+
+# How To: Get Started
 
 ## Technologies Used
 

package/docs/guides/how-to/index.md

@@ -1 +1,11 @@
-# How To ||20
+---
+parts:
+  - How To
+title: How To
+eleventyNavigation:
+  key: How To
+  order: 20
+  title: How To
+---
+
+# How To

package/docs/guides/index.md

@@ -1,4 +1,14 @@
-# Guides ||30
+---
+parts:
+  - Guides
+title: Guides
+eleventyNavigation:
+  key: Guides
+  order: 30
+  title: Guides
+---
+
+# Guides
 
 Lion is a set of white label Web Components that can be extended to your own styled layer of components.
 
@@ -12,9 +22,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/593b753f0f99acb36ea6009677bc7fdda9184184/docs/guides/principles/definitions-and-terms.md)
-- [Styling](https://github.com/ing-bank/lion/blob/593b753f0f99acb36ea6009677bc7fdda9184184/docs/guides/principles/styling.md)
-- [Scoped Elements](https://github.com/ing-bank/lion/blob/593b753f0f99acb36ea6009677bc7fdda9184184/docs/guides/principles/scoped-elements.md)
+- [Definitions and Terms](https://github.com/ing-bank/lion/blob/87a1cb4d5bec301af6688be2c7bf778344d2ae42/docs/guides/principles/definitions-and-terms.md)
+- [Styling](https://github.com/ing-bank/lion/blob/87a1cb4d5bec301af6688be2c7bf778344d2ae42/docs/guides/principles/styling.md)
+- [Scoped Elements](https://github.com/ing-bank/lion/blob/87a1cb4d5bec301af6688be2c7bf778344d2ae42/docs/guides/principles/scoped-elements.md)
 
 ## Extending Developer
 
@@ -22,13 +32,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/593b753f0f99acb36ea6009677bc7fdda9184184/docs/guides/principles/subclasser-apis.md)
-- [Extend documentation](https://github.com/ing-bank/lion/blob/593b753f0f99acb36ea6009677bc7fdda9184184/docs/blog/extending-documentation.md)
+- [Subclasser APIs](https://github.com/ing-bank/lion/blob/87a1cb4d5bec301af6688be2c7bf778344d2ae42/docs/guides/principles/subclasser-apis.md)
+- [Extend documentation](https://github.com/ing-bank/lion/blob/87a1cb4d5bec301af6688be2c7bf778344d2ae42/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/593b753f0f99acb36ea6009677bc7fdda9184184/docs/guides/how-to/get-started.md)
-- [Create a custom field](https://github.com/ing-bank/lion/blob/593b753f0f99acb36ea6009677bc7fdda9184184/docs/guides/how-to/create-a-custom-field.md)
-- [Extend a native input](https://github.com/ing-bank/lion/blob/593b753f0f99acb36ea6009677bc7fdda9184184/docs/guides/how-to/extend-a-native-input.md)
+- [Get started](https://github.com/ing-bank/lion/blob/87a1cb4d5bec301af6688be2c7bf778344d2ae42/docs/guides/how-to/get-started.md)
+- [Create a custom field](https://github.com/ing-bank/lion/blob/87a1cb4d5bec301af6688be2c7bf778344d2ae42/docs/guides/how-to/create-a-custom-field.md)
+- [Extend a native input](https://github.com/ing-bank/lion/blob/87a1cb4d5bec301af6688be2c7bf778344d2ae42/docs/guides/how-to/extend-a-native-input.md)

package/docs/guides/principles/definitions-and-terms.md

@@ -1,4 +1,16 @@
-# Principles >> Definitions and Terms ||20
+---
+parts:
+  - Principles
+  - Definitions and Terms
+title: 'Principles: Definitions and Terms'
+eleventyNavigation:
+  key: 'Principles: Definitions and Terms'
+  order: 20
+  parent: Principles
+  title: Definitions and Terms
+---
+
+# Principles: Definitions and Terms
 
 Below you will find a list of definitions and terms that will be used throughout our code
 documentation.

package/docs/guides/principles/index.md

@@ -1,4 +1,14 @@
-# Principles ||10
+---
+parts:
+  - Principles
+title: Principles
+eleventyNavigation:
+  key: Principles
+  order: 10
+  title: Principles
+---
+
+# Principles
 
 Lion is a set of white label Web Components that can be extended to your own styled layer of components.
 
@@ -12,9 +22,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/593b753f0f99acb36ea6009677bc7fdda9184184/docs/guides/principles/definitions-and-terms.md)
-- [Styling](https://github.com/ing-bank/lion/blob/593b753f0f99acb36ea6009677bc7fdda9184184/docs/guides/principles/styling.md)
-- [Scoped Elements](https://github.com/ing-bank/lion/blob/593b753f0f99acb36ea6009677bc7fdda9184184/docs/guides/principles/scoped-elements.md)
+- [Definitions and Terms](https://github.com/ing-bank/lion/blob/87a1cb4d5bec301af6688be2c7bf778344d2ae42/docs/guides/principles/definitions-and-terms.md)
+- [Styling](https://github.com/ing-bank/lion/blob/87a1cb4d5bec301af6688be2c7bf778344d2ae42/docs/guides/principles/styling.md)
+- [Scoped Elements](https://github.com/ing-bank/lion/blob/87a1cb4d5bec301af6688be2c7bf778344d2ae42/docs/guides/principles/scoped-elements.md)
 
 ## Extending Developer
 
@@ -22,5 +32,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/593b753f0f99acb36ea6009677bc7fdda9184184/docs/guides/principles/subclasser-apis.md)
-- [Extend documentation](https://github.com/ing-bank/lion/blob/593b753f0f99acb36ea6009677bc7fdda9184184/docs/blog/extending-documentation.md)
+- [Subclasser APIs](https://github.com/ing-bank/lion/blob/87a1cb4d5bec301af6688be2c7bf778344d2ae42/docs/guides/principles/subclasser-apis.md)
+- [Extend documentation](https://github.com/ing-bank/lion/blob/87a1cb4d5bec301af6688be2c7bf778344d2ae42/docs/blog/extending-documentation.md)

package/docs/guides/principles/scoped-elements.md

@@ -1,4 +1,16 @@
-# Principles >> Scoped Elements ||40
+---
+parts:
+  - Principles
+  - Scoped Elements
+title: 'Principles: Scoped Elements'
+eleventyNavigation:
+  key: 'Principles: Scoped Elements'
+  order: 40
+  parent: Principles
+  title: Scoped Elements
+---
+
+# Principles: Scoped Elements
 
 The [CustomElementRegistry](https://developer.mozilla.org/en-US/docs/Web/API/CustomElementRegistry) provides methods for registering custom elements. One of the limitations of working with this global registry is that multiple versions of the same element cannot co-exist. This causes bottlenecks in software delivery that should be managed by the teams and complex build systems. [Scoped Custom Element Registries](https://github.com/w3c/webcomponents/issues/716) is a proposal that will solve the problem. Since this functionality won't be available (especially not cross browser) anytime soon, we've adopted [OpenWC's Scoped Elements](https://open-wc.org/docs/development/scoped-elements/).