@lion/ui 0.11.1 → 0.11.3

package/docs/guides/principles/styling.md

@@ -1,4 +1,16 @@
-# Principles >> Styling ||30
+---
+parts:
+  - Principles
+  - Styling
+title: 'Principles: Styling'
+eleventyNavigation:
+  key: 'Principles: Styling'
+  order: 30
+  parent: Principles
+  title: Styling
+---
+
+# Principles: Styling
 
 ## Markup and styling
 
@@ -19,7 +31,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/593b753f0f99acb36ea6009677bc7fdda9184184/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/0c3425c2b9f0cbb8c2680b033ba775170b92c641/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/docs/guides/principles/subclasser-apis.md

@@ -1,4 +1,16 @@
-# Principles >> Subclasser apis ||50
+---
+parts:
+  - Principles
+  - Subclasser apis
+title: 'Principles: Subclasser apis'
+eleventyNavigation:
+  key: 'Principles: Subclasser apis'
+  order: 50
+  parent: Principles
+  title: Subclasser apis
+---
+
+# Principles: Subclasser apis
 
 In order to make it easy for Subclassers to extend our components, we follow a certain set
 of best practices naming conventions to make our code predictable.

package/package.json

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