From 747945f7f807871f58a5ae22e98e93ad162538d3 Mon Sep 17 00:00:00 2001 From: Nico Hoffmann Date: Sun, 11 Aug 2024 12:55:14 +0200 Subject: [PATCH] Fix Lab docs links --- .../1_blueprints/0_file/reference-article.txt | 2 +- .../1_blueprints/0_page/reference-article.txt | 2 +- .../1_blueprints/0_user/reference-article.txt | 544 +++++++++--------- .../3_panel/7_styling/reference-article.txt | 136 ++--- .../1_options/0_panel/reference-article.txt | 2 +- .../0_panel-dialogs/reference-extension.txt | 10 +- .../0_advanced-panel-area/cookbook-recipe.txt | 6 +- .../4_quicktips/0_panel-branding/quicktip.txt | 2 +- content/releases/3-6/changes/panel/link.txt | 2 +- content/releases/3-6/release.txt | 4 +- .../features-for-developers/techstack.php | 2 +- site/snippets/templates/release-36/panel.php | 2 +- 12 files changed, 356 insertions(+), 358 deletions(-) diff --git a/content/docs/2_reference/3_panel/1_blueprints/0_file/reference-article.txt b/content/docs/2_reference/3_panel/1_blueprints/0_file/reference-article.txt index 9f14daa9f4..6232635996 100644 --- a/content/docs/2_reference/3_panel/1_blueprints/0_file/reference-article.txt +++ b/content/docs/2_reference/3_panel/1_blueprints/0_file/reference-article.txt @@ -188,7 +188,7 @@ The `back` and `color` options for also support shorthands for the core CSS c image: back: "purple-400" ``` -Check out the (link: docs/reference/plugins/ui#colors text: list of our color properties) for available options. +Check out the (link: https://lab.getkirby.com/public/lab/basics/design/colors text: list of our color properties) for available options. ```yaml image: diff --git a/content/docs/2_reference/3_panel/1_blueprints/0_page/reference-article.txt b/content/docs/2_reference/3_panel/1_blueprints/0_page/reference-article.txt index 2a262661b6..b9c6cea05a 100644 --- a/content/docs/2_reference/3_panel/1_blueprints/0_page/reference-article.txt +++ b/content/docs/2_reference/3_panel/1_blueprints/0_page/reference-article.txt @@ -333,7 +333,7 @@ The `back` and `color` options for also support shorthands for the core CSS c image: back: "purple-400" ``` -Check out the (link: docs/reference/plugins/ui#colors text: list of our color properties) for available options. +Check out the (link: https://lab.getkirby.com/public/lab/basics/design/colors text: list of our color properties) for available options. ```yaml image: diff --git a/content/docs/2_reference/3_panel/1_blueprints/0_user/reference-article.txt b/content/docs/2_reference/3_panel/1_blueprints/0_user/reference-article.txt index 8aee7a4e42..aebf9890d2 100644 --- a/content/docs/2_reference/3_panel/1_blueprints/0_user/reference-article.txt +++ b/content/docs/2_reference/3_panel/1_blueprints/0_user/reference-article.txt @@ -1,272 +1,272 @@ -Title: User blueprint - ----- - -Intro: User blueprints are located in `/site/blueprints/users` and control the Panel setup, form fields and permissions for a user role. - ----- - -Guide: blueprints/introduction - ----- - -Text: - -## Blueprint location - -```filesystem -/site/blueprints/users/ -``` - -## Default user blueprint - -To create the same set of fields for all roles, you can setup a `default.yml` that is used whenever no custom role blueprint is configured. - -```filesystem -/site/blueprints/users/default.yml -``` - -## Title and description - -The title is required and will appear in the list of selectable roles when a new user is created. An optional description can be displayed as well: - -```yaml -title: Client -description: The client can edit all pages -``` - -### Translated titles - -Title and description can be translated by passing an array of translations with the matching language code as key: - -```yaml -title: - en: Client - de: Kunde -description: - en: The client can edit all pages - de: Der Kunde kann alle Seiten bearbeiten -``` - -## Home option - -When a user logs in to the Panel, they normally get redirected to the last view they were on before they were logged out or the Site view. When you work with permissions, you might want to block the Site view or redirect the user to a completely different view instead. This is now possible with the new `home` option for user blueprints. This way you can define the redirect for each role individually. Redirects can be simple paths or dynamic locations via string queries. - - -### Simple paths - -```yaml "/site/blueprints/users/editor.yml" -title: Editor -home: /panel/account -``` - -### Queries to panel views - -```yaml "/site/blueprints/users/editor.yml" -title: Editor -home: "{{ site.find('blog').children.first.panel.url }}" -``` - -### Queries to pages - -```yaml "/site/blueprints/users/editor.yml" -title: Editor -home: "{{ site.find('blog').children.first.url }}" -``` - - -## Image options - -The image options for users can now be defined directly in their own blueprint. This significantly simplifies the setup of sections as they all inherit the image settings. You can still set image settings in sections the good old way if needed. - -```yaml "site/blueprints/user/editor.yml" -image: - back: blue-200 - icon: 📝 -``` - -### Support for queries - -Panel preview image options now all support our powerful queries: - -```yaml "site/blueprints/users/editor.yml" -image: - back: "{{ user.myCustomBackColor }}" -``` - -### Custom colors -`back` and `color` options for Panel preview images now support shorthands for core CSS color variables as well as HEX codes or other native CSS color properties (e.g. even gradients): - -#### CSS color property shorthands - -```yaml -image: - back: "purple-400" -``` -Check out the (link: docs/reference/plugins/ui#colors text: list of our color properties) for available options. - -#### Hex codes - -```yaml -image: - back: "#ff0000" -``` - -#### CSS rules - -```yaml -image: - back: "linear-gradient(90deg, rgba(2,0,36,1) 0%, rgba(9,9,121,1) 35%, rgba(0,212,255,1) 100%);" -``` - -## Permissions - -The `permissions` option can be used to restrict access to certain actions for the particular role. By default, all actions are allowed and you can deny them by passing `false`. - -### `access` - -| Option | Value | -|---- | ---- | -| `account` | `true`/`false` | -| `panel` | `true`/`false` | -| `users` | `true`/`false`| -| `site` | `true`/`false` | -| `system`| `true`/`false` | -| `languages` | `true`/`false` | - -#### Example: Prevent accessing user management and settings - -```yaml -permissions: - access: - settings: false - users: false -``` - - -### `files` - -| Option | Value | -|---- | ---- | -| `changeName` | `true`/`false` | -| `create` | `true`/`false` | -| `delete` | `true`/`false` | -| `replace` | `true`/`false` | -| `update` | `true`/`false` | - -#### Example: Prevent deleting files - -```yaml -permissions: - files: - delete: false -``` - -### `pages` - -| Option | Value | -|---- | ---- | -| `changeSlug` | `true`/`false` | -| `changeStatus` | `true`/`false` | -| `changeTemplate` | `true`/`false` | -| `changeTitle` | `true`/`false` | -| `create` | `true`/`false` | -| `delete` | `true`/`false` | -| `duplicate` | `true`/`false` | -| `move` | `true`/`false` | -| `preview` | `true`/`false` | -| `read` | `true`/`false` | -| `sort` | `true`/`false` | -| `update` | `true`/`false` | - -#### Example: Prevent deleting and creating pages and changing their template - -```yaml -permissions: - pages: - delete: false - create: false - changeTemplate: false -``` - -### `site` - -| Option | Value | -|---- | ---- | -| `update` | `true`/`false` | - -### `users` - -The `users` setting can be set generally to `false` to prevent the user from editing, adding or deleting other users. - -```yaml -users: false -``` - -It is also possible to set the `users` options individually. - - - -| Option | Value | -|---- | ---- | -| `changeEmail` | `true`/`false` | -| `changeLanguage` | `true`/`false` | -| `changeName` | `true`/`false` | -| `changePassword` | `true`/`false` | -| `create` | `true`/`false` | -| `delete` | `true`/`false` | -| `update` | `true`/`false` | - -#### Example: - -```yaml -permissions: - access: - users: true - users: - delete: false - create: false - changeRole: false -``` - -### `user` - -This option refers to each user with this role. - -| Option | Value | -|---- | ---- | -| `changeEmail` | `true`/`false` | -| `changeLanguage` | `true`/`false` | -| `changeName` | `true`/`false` | -| `changePassword` | `true`/`false` | -| `changeRole` | `true`/`false` | -| `create` | `true`/`false` | -| `delete` | `true`/`false` | -| `update` | `true`/`false` | - - -#### Example - -This user can access the user management, but not edit other users. The user cannot change their own role or delete themselves. - -```yaml -permissions: - access: - users: true - users: false - user: - delete: false - changeRole: false -``` - -### Using wildcards -It's also possible to restrict access to entire blocks by just passing `false` to the block: - -```yaml -permissions: - pages: false -``` - -## Examples - -You can find examples of user blueprints in the (link: docs/reference/panel/samples/user text: samples section). +Title: User blueprint + +---- + +Intro: User blueprints are located in `/site/blueprints/users` and control the Panel setup, form fields and permissions for a user role. + +---- + +Guide: blueprints/introduction + +---- + +Text: + +## Blueprint location + +```filesystem +/site/blueprints/users/ +``` + +## Default user blueprint + +To create the same set of fields for all roles, you can setup a `default.yml` that is used whenever no custom role blueprint is configured. + +```filesystem +/site/blueprints/users/default.yml +``` + +## Title and description + +The title is required and will appear in the list of selectable roles when a new user is created. An optional description can be displayed as well: + +```yaml +title: Client +description: The client can edit all pages +``` + +### Translated titles + +Title and description can be translated by passing an array of translations with the matching language code as key: + +```yaml +title: + en: Client + de: Kunde +description: + en: The client can edit all pages + de: Der Kunde kann alle Seiten bearbeiten +``` + +## Home option + +When a user logs in to the Panel, they normally get redirected to the last view they were on before they were logged out or the Site view. When you work with permissions, you might want to block the Site view or redirect the user to a completely different view instead. This is now possible with the new `home` option for user blueprints. This way you can define the redirect for each role individually. Redirects can be simple paths or dynamic locations via string queries. + + +### Simple paths + +```yaml "/site/blueprints/users/editor.yml" +title: Editor +home: /panel/account +``` + +### Queries to panel views + +```yaml "/site/blueprints/users/editor.yml" +title: Editor +home: "{{ site.find('blog').children.first.panel.url }}" +``` + +### Queries to pages + +```yaml "/site/blueprints/users/editor.yml" +title: Editor +home: "{{ site.find('blog').children.first.url }}" +``` + + +## Image options + +The image options for users can now be defined directly in their own blueprint. This significantly simplifies the setup of sections as they all inherit the image settings. You can still set image settings in sections the good old way if needed. + +```yaml "site/blueprints/user/editor.yml" +image: + back: blue-200 + icon: 📝 +``` + +### Support for queries + +Panel preview image options now all support our powerful queries: + +```yaml "site/blueprints/users/editor.yml" +image: + back: "{{ user.myCustomBackColor }}" +``` + +### Custom colors +`back` and `color` options for Panel preview images now support shorthands for core CSS color variables as well as HEX codes or other native CSS color properties (e.g. even gradients): + +#### CSS color property shorthands + +```yaml +image: + back: "purple-400" +``` +Check out the (link: https://lab.getkirby.com/public/lab/basics/design/colors text: list of our color properties) for available options. + +#### Hex codes + +```yaml +image: + back: "#ff0000" +``` + +#### CSS rules + +```yaml +image: + back: "linear-gradient(90deg, rgba(2,0,36,1) 0%, rgba(9,9,121,1) 35%, rgba(0,212,255,1) 100%);" +``` + +## Permissions + +The `permissions` option can be used to restrict access to certain actions for the particular role. By default, all actions are allowed and you can deny them by passing `false`. + +### `access` + +| Option | Value | +|---- | ---- | +| `account` | `true`/`false` | +| `panel` | `true`/`false` | +| `users` | `true`/`false`| +| `site` | `true`/`false` | +| `system`| `true`/`false` | +| `languages` | `true`/`false` | + +#### Example: Prevent accessing user management and settings + +```yaml +permissions: + access: + settings: false + users: false +``` + + +### `files` + +| Option | Value | +|---- | ---- | +| `changeName` | `true`/`false` | +| `create` | `true`/`false` | +| `delete` | `true`/`false` | +| `replace` | `true`/`false` | +| `update` | `true`/`false` | + +#### Example: Prevent deleting files + +```yaml +permissions: + files: + delete: false +``` + +### `pages` + +| Option | Value | +|---- | ---- | +| `changeSlug` | `true`/`false` | +| `changeStatus` | `true`/`false` | +| `changeTemplate` | `true`/`false` | +| `changeTitle` | `true`/`false` | +| `create` | `true`/`false` | +| `delete` | `true`/`false` | +| `duplicate` | `true`/`false` | +| `move` | `true`/`false` | +| `preview` | `true`/`false` | +| `read` | `true`/`false` | +| `sort` | `true`/`false` | +| `update` | `true`/`false` | + +#### Example: Prevent deleting and creating pages and changing their template + +```yaml +permissions: + pages: + delete: false + create: false + changeTemplate: false +``` + +### `site` + +| Option | Value | +|---- | ---- | +| `update` | `true`/`false` | + +### `users` + +The `users` setting can be set generally to `false` to prevent the user from editing, adding or deleting other users. + +```yaml +users: false +``` + +It is also possible to set the `users` options individually. + + + +| Option | Value | +|---- | ---- | +| `changeEmail` | `true`/`false` | +| `changeLanguage` | `true`/`false` | +| `changeName` | `true`/`false` | +| `changePassword` | `true`/`false` | +| `create` | `true`/`false` | +| `delete` | `true`/`false` | +| `update` | `true`/`false` | + +#### Example: + +```yaml +permissions: + access: + users: true + users: + delete: false + create: false + changeRole: false +``` + +### `user` + +This option refers to each user with this role. + +| Option | Value | +|---- | ---- | +| `changeEmail` | `true`/`false` | +| `changeLanguage` | `true`/`false` | +| `changeName` | `true`/`false` | +| `changePassword` | `true`/`false` | +| `changeRole` | `true`/`false` | +| `create` | `true`/`false` | +| `delete` | `true`/`false` | +| `update` | `true`/`false` | + + +#### Example + +This user can access the user management, but not edit other users. The user cannot change their own role or delete themselves. + +```yaml +permissions: + access: + users: true + users: false + user: + delete: false + changeRole: false +``` + +### Using wildcards +It's also possible to restrict access to entire blocks by just passing `false` to the block: + +```yaml +permissions: + pages: false +``` + +## Examples + +You can find examples of user blueprints in the (link: docs/reference/panel/samples/user text: samples section). diff --git a/content/docs/2_reference/3_panel/7_styling/reference-article.txt b/content/docs/2_reference/3_panel/7_styling/reference-article.txt index 8f798acf0b..7cd5f764ba 100644 --- a/content/docs/2_reference/3_panel/7_styling/reference-article.txt +++ b/content/docs/2_reference/3_panel/7_styling/reference-article.txt @@ -1,68 +1,68 @@ - -Title: Styling - ----- - -Intro: Learn how you can customise the Panel look via CSS. - ----- - -Guide: ../cookbook/panel/customizing-panel - ----- - -Text: - -## Options - -The (link: docs/reference/system/options/panel text: `panel` config option) allows you to customise parts of the Panel look. Besides setting a (link: docs/reference/system/options/panel#custom-panel-favicon text: custom favicon), you can add a (link: docs/reference/system/options/panel#custom-panel-css text: custom CSS file) to the Panel in which you can utilize the following CSS selectors and variables. - -## CSS selectors - -Throughout the Panel we are using class-based CSS selectors which you can target in your custom `panel.css` to modify the look of the Panel: - -```css "assets/panel.css" -.k-topbar { - background: lightslategray; -} -``` - -Besides adding more CSS selectors, we are also using data attributes to allow for much more powerful and tailored Panel customizations: - -| Selector | Description | -| -------- | ----------- | -| `.k-panel[data-language]` | for the current content translation language | -| `.k-panel[data-default-language]` | for the default content translation language | -| `.k-panel[data-translation]` | for the current Panel UI/user language | -| `.k-panel[data-role]` | for current user role | -| `.k-panel[data-user]` | for current user ID | -| `.k-page-view[data-id]` | for page ID | -| `.k-page-view[data-template]` | for page's intended template | -| `.k-file-view[data-id]` | for file ID | -| `.k-file-view[data-template]` | for file's template | -| `.k-user-view[data-id]` | for user ID | -| `.k-user-view[data-role]` | for user's role | -| `.k-site-view[data-id]` | for site ID (/) | -| `.k-site-view[data-template]` | for site's template (site) | -| `.k-languages-dropdown` | for content translation language dropdown | -| `.k-page-view-options`, `.k-file-view-options` and `.k-user-view-options` | for options dropdown on model views | -| `.k-page-view-preview`, `.k-file-view-preview`, `.k-site-view-preview` and `.k-user-view-preview` | for preview button on model views | -| `.k-pages-section .k-item[data-id]`, `.k-pages-section .k-item[data-status]` and `.k-pages-section .k-item[data-template]` | | -| `.k-files-section .k-item[data-id]` and `.k-files-section .k-item[data-template]` | | -| `.k-status-icon .k-status-icon-{status}` | for the page's status button | - - - -## CSS properties - -We use CSS properties for the most important parameters in the Panel. This is useful for customising the look of the Panel but als for plugin developers to create UIs that seamlessly integrate with the rest of the Panel. - -You can overwrite our default properties in your custom `panel.css`: - -```css "assets/panel.css" -:root { - --color-backdrop: rgba(255, 255, 255, 0.6); -} -``` - -(link: docs/reference/plugins/ui#colors text: Get to know all CSS properties ›) + +Title: Styling + +---- + +Intro: Learn how you can customise the Panel look via CSS. + +---- + +Guide: ../cookbook/panel/customizing-panel + +---- + +Text: + +## Options + +The (link: docs/reference/system/options/panel text: `panel` config option) allows you to customise parts of the Panel look. Besides setting a (link: docs/reference/system/options/panel#custom-panel-favicon text: custom favicon), you can add a (link: docs/reference/system/options/panel#custom-panel-css text: custom CSS file) to the Panel in which you can utilize the following CSS selectors and variables. + +## CSS selectors + +Throughout the Panel we are using class-based CSS selectors which you can target in your custom `panel.css` to modify the look of the Panel: + +```css "assets/panel.css" +.k-topbar { + background: lightslategray; +} +``` + +Besides adding more CSS selectors, we are also using data attributes to allow for much more powerful and tailored Panel customizations: + +| Selector | Description | +| -------- | ----------- | +| `.k-panel[data-language]` | for the current content translation language | +| `.k-panel[data-default-language]` | for the default content translation language | +| `.k-panel[data-translation]` | for the current Panel UI/user language | +| `.k-panel[data-role]` | for current user role | +| `.k-panel[data-user]` | for current user ID | +| `.k-page-view[data-id]` | for page ID | +| `.k-page-view[data-template]` | for page's intended template | +| `.k-file-view[data-id]` | for file ID | +| `.k-file-view[data-template]` | for file's template | +| `.k-user-view[data-id]` | for user ID | +| `.k-user-view[data-role]` | for user's role | +| `.k-site-view[data-id]` | for site ID (/) | +| `.k-site-view[data-template]` | for site's template (site) | +| `.k-languages-dropdown` | for content translation language dropdown | +| `.k-page-view-options`, `.k-file-view-options` and `.k-user-view-options` | for options dropdown on model views | +| `.k-page-view-preview`, `.k-file-view-preview`, `.k-site-view-preview` and `.k-user-view-preview` | for preview button on model views | +| `.k-pages-section .k-item[data-id]`, `.k-pages-section .k-item[data-status]` and `.k-pages-section .k-item[data-template]` | | +| `.k-files-section .k-item[data-id]` and `.k-files-section .k-item[data-template]` | | +| `.k-status-icon .k-status-icon-{status}` | for the page's status button | + + + +## CSS properties + +We use CSS properties for the most important parameters in the Panel. This is useful for customising the look of the Panel but als for plugin developers to create UIs that seamlessly integrate with the rest of the Panel. + +You can overwrite our default properties in your custom `panel.css`: + +```css "assets/panel.css" +:root { + --color-backdrop: rgba(255, 255, 255, 0.6); +} +``` + +(link: https://lab.getkirby.com/public/lab/basics/design/colors text: Get to know all CSS properties ›) diff --git a/content/docs/2_reference/6_system/1_options/0_panel/reference-article.txt b/content/docs/2_reference/6_system/1_options/0_panel/reference-article.txt index f03df9d87d..7da68a0bed 100644 --- a/content/docs/2_reference/6_system/1_options/0_panel/reference-article.txt +++ b/content/docs/2_reference/6_system/1_options/0_panel/reference-article.txt @@ -130,7 +130,7 @@ If you have multiple environments like staging, production etc., you can use dif More information: - (link: docs/reference/panel/styling text: Styling the Panel) -- (link: docs/reference/plugins/ui#colors text: All CSS properties) +- (link: https://lab.getkirby.com/public/lab/basics/design/colors text: All CSS properties) - (link: docs/quicktips/customizing-panel text: Examples for customizing the Panel) Instead of adding it to your `config.php`, CSS to be applied globally in the Panel can also be added via a plugin: if an `index.css` file is present in the root folder of a plugin, it will be automatically loaded into the Panel. diff --git a/content/docs/2_reference/7_plugins/1_extensions/0_panel-dialogs/reference-extension.txt b/content/docs/2_reference/7_plugins/1_extensions/0_panel-dialogs/reference-extension.txt index 66ecac8432..4429546064 100644 --- a/content/docs/2_reference/7_plugins/1_extensions/0_panel-dialogs/reference-extension.txt +++ b/content/docs/2_reference/7_plugins/1_extensions/0_panel-dialogs/reference-extension.txt @@ -12,12 +12,10 @@ All reuse the same dialog components: | Component name | Usage | | --- | --- | -| (link: docs/reference/plugins/ui/error-dialog text: `k-error-dialog`) | For detailed error warnings (i.e. form validation) | -| (link: docs/reference/plugins/ui/form-dialog text: `k-form-dialog`) | For dialogs with form fields and submit buttons | -| (link: docs/reference/plugins/ui/remove-dialog text: `k-remove-dialog`) | To confirm deleting items | -| (link: docs/reference/plugins/ui/text-dialog text: `k-text-dialog`) | For dialogs with a custom text message | - -More components will be supported in future releases. +| (link: https://lab.getkirby.com/public/lab/docs/k-error-dialog text: `k-error-dialog`) | For detailed error warnings (i.e. form validation) | +| (link: https://lab.getkirby.com/public/lab/docs/k-form-dialog text: `k-form-dialog`) | For dialogs with form fields and submit buttons | +| (link: https://lab.getkirby.com/public/lab/docs/k-remove-dialog text: `k-remove-dialog`) | To confirm deleting items | +| (link: https://lab.getkirby.com/public/lab/docs/k-text-dialog text: `k-text-dialog`) | For dialogs with a custom text message | ## Dialog definition diff --git a/content/docs/3_cookbook/0_panel/0_advanced-panel-area/cookbook-recipe.txt b/content/docs/3_cookbook/0_panel/0_advanced-panel-area/cookbook-recipe.txt index 769e24eeb7..ea6f07b379 100644 --- a/content/docs/3_cookbook/0_panel/0_advanced-panel-area/cookbook-recipe.txt +++ b/content/docs/3_cookbook/0_panel/0_advanced-panel-area/cookbook-recipe.txt @@ -267,7 +267,7 @@ export default { Maybe worth mentioning is the `price` method which converts the price into a nicely formatted currency. -The last table column contains the (link: docs/reference/plugins/ui/options-dropdown text: options dropdown) for the edit and delete buttons). +The last table column contains the (link: https://lab.getkirby.com/public/lab/docs/k-options-dropdown text: options dropdown) for the edit and delete buttons). ```html @@ -322,7 +322,7 @@ Each dialog has a `load` callback and a `submit` callback. You can read more abo ### Delete -The `delete` dialog reuses Kirby's (link: docs/reference/plugins/ui/remove-dialog text: `k-remove-dialog` component), asks for confirmation, and on submit removes the product with the given `id` from the array and writes the remaining new array to file. +The `delete` dialog reuses Kirby's (link: https://lab.getkirby.com/public/lab/docs/k-remove-dialog text: `k-remove-dialog` component), asks for confirmation, and on submit removes the product with the given `id` from the array and writes the remaining new array to file. ```php "/site/plugins/products/dialogs/delete.php" }" | `k-browser-view` | - | | `k-custom-view` | - | -- Removed `icon` prop from `k-card` and `k-list-item`. Pass data as part of the `image` prop instead to new (link: docs/reference/plugins/ui/item text: `k-item` component). +- Removed `icon` prop from `k-card` and `k-list-item`. Pass data as part of the `image` prop instead to new (link: https://lab.getkirby.com/public/lab/docs/k-item text: `k-item` component). - If the `cover` option is not defined for a section, it is disabled by default. - The `` property is now rendered as plain text by default instead of as HTML code. For the previous behavior use ``. diff --git a/site/snippets/templates/features-for-developers/techstack.php b/site/snippets/templates/features-for-developers/techstack.php index e1600fcff0..a14e65baff 100644 --- a/site/snippets/templates/features-for-developers/techstack.php +++ b/site/snippets/templates/features-for-developers/techstack.php @@ -27,7 +27,7 @@
-

Admin interface framework →

+

Admin interface framework →

Our admin interface is built on Vue.js. It's a playground for your ideas. Extend it with plugins and make it your own with the full power of Vue and an incredibly powerful backend.

diff --git a/site/snippets/templates/release-36/panel.php b/site/snippets/templates/release-36/panel.php index 070be25574..2ab53f678f 100644 --- a/site/snippets/templates/release-36/panel.php +++ b/site/snippets/templates/release-36/panel.php @@ -20,7 +20,7 @@ [ 'title' => 'CSS variables', 'text' => 'Every little detail of the Panel is now defined as a CSS variable. What’s great about that? You can overwrite our variables in your panel.css. Custom Panel themes just got so much easier.', - 'link' => '/docs/reference/plugins/ui#css-properties' + 'link' => 'https://lab.getkirby.com/public/lab/basics/design' ], [ 'title' => 'It’s all in the details',