` which contains both the component and the overlay. To allow the user to interact with the page while the Window or Dialog is hidden, you also need to hide the overlay.
+The [modal Window](slug://components/window/modal) and [Dialog](slug://dialog-overview) components have a different rendering. They are wrapped in a `
` which contains both the component and the overlay. To allow the user to interact with the page while the Window or Dialog is hidden, you also need to hide the overlay.
To customize the closing of a modal Window or Dialog:
diff --git a/knowledge-base/window-modal-minimize-popup.md b/knowledge-base/window-modal-minimize-popup.md
index b9e3b99f03..d50ca83f7b 100644
--- a/knowledge-base/window-modal-minimize-popup.md
+++ b/knowledge-base/window-modal-minimize-popup.md
@@ -29,7 +29,7 @@ To implement a responsible popup that can be minimized to the bottom of the page
1. Set the `Top` and `Left` parameters to control the position of the modal.
2. Use boolean flags to show and hide the popup.
-3. Use the [MediaQuery]({%slug mediaquery-overview%}) component to make the modal window responsive.
+3. Use the [MediaQuery](slug://mediaquery-overview) component to make the modal window responsive.
>caption The result from the code snippet below on a big screen.
diff --git a/knowledge-base/window-responsive.md b/knowledge-base/window-responsive.md
index 47fb383f26..2d8d77ba4e 100644
--- a/knowledge-base/window-responsive.md
+++ b/knowledge-base/window-responsive.md
@@ -117,4 +117,4 @@ If you want to use the CSS media queries, you have to create a separate CSS file
## See also:
- * [Documentation Window for Blazor | Size]({%slug components/window/size%})
+ * [Documentation Window for Blazor | Size](slug://components/window/size)
diff --git a/knowledge-base/wizard-confirm-step-change.md b/knowledge-base/wizard-confirm-step-change.md
index a7bda21aac..5598a1333e 100644
--- a/knowledge-base/wizard-confirm-step-change.md
+++ b/knowledge-base/wizard-confirm-step-change.md
@@ -25,7 +25,7 @@ res_type: kb
When a user wants to move to the next step, I need to confirm the move and show them a popup warning for some situations. If they choose to "continue", take them to the next step as normal, otherwise back to the current step.
## Solution
-Use the [`OnChange` event]({%slug wizard-events%}#onchange) of the originating step to show a [confirm Dialog]({%slug dialog-predefined%}#confirm). Cancel the event if the user does not confirm. It is also possible to use a Window component, but a confirmation Dialog is likely more suitable.
+Use the [`OnChange` event](slug://wizard-events#onchange) of the originating step to show a [confirm Dialog](slug://dialog-predefined#confirm). Cancel the event if the user does not confirm. It is also possible to use a Window component, but a confirmation Dialog is likely more suitable.
This example shows confirmation when moving away from step 1. You can extend it for other steps. You can also add a lambda expression in the handler on each step to provide more data to the method - for example, to form a more meaningful message for the step or to distinguish steps more easily.
diff --git a/knowledge-base/wizard-skip-step.md b/knowledge-base/wizard-skip-step.md
index cec40696cb..39abcd0915 100644
--- a/knowledge-base/wizard-skip-step.md
+++ b/knowledge-base/wizard-skip-step.md
@@ -25,11 +25,11 @@ res_type: kb
How to skip one or more Wizard steps, based on the results of another step?
-The [Wizard flow is set to linear]({%slug wizard-structure-stepper%}#linear-flow), so I can't disable steps, but I need to skip an unneeded step programmatically, based on a custom condition in a previous step.
+The [Wizard flow is set to linear](slug://wizard-structure-stepper#linear-flow), so I can't disable steps, but I need to skip an unneeded step programmatically, based on a custom condition in a previous step.
## Solution
-1. Subscribe to the [`OnChange`]({%slug wizard-events%}#onchange) event of the originating step.
+1. Subscribe to the [`OnChange`](slug://wizard-events#onchange) event of the originating step.
1. Check `args.TargetIndex` to find out if the user is navigating in the desired direction.
1. Set `args.IsCancelled` to `true` to cancel navigation to the next step.
1. Set the Wizard `Value` to the desired step.
diff --git a/knowledge-base/wizard-wrap-step-label-text.md b/knowledge-base/wizard-wrap-step-label-text.md
index 37e8599c11..4ea4f81aae 100644
--- a/knowledge-base/wizard-wrap-step-label-text.md
+++ b/knowledge-base/wizard-wrap-step-label-text.md
@@ -68,4 +68,4 @@ To wrap the Wizard step labels and display the full text, apply custom CSS style
## See Also
- [Wizard Overview](https://docs.telerik.com/blazor-ui/components/wizard/overview)
-- [Override the Theme or Apply Custom CSS Styles]({%slug themes-override%})
+- [Override the Theme or Apply Custom CSS Styles](slug://themes-override)
diff --git a/security/overview.md b/security/overview.md
index 6a8d412147..e1af6fd91d 100644
--- a/security/overview.md
+++ b/security/overview.md
@@ -78,7 +78,7 @@ We leverage leading commercial tools to automatically monitor and update third-p
Content Security Policy (CSP) is a critical security measure that helps detect and mitigate the risks of content injection vulnerabilities, such as cross-site scripting (XSS) and data injection attacks. Telerik UI for Blazor components are designed to be CSP-compliant, ensuring secure integration into customer projects.
-For more detailed information on CSP compliance, refer to the [Telerik UI for Blazor Content Security Policy]({%slug troubleshooting-csp%}) article.
+For more detailed information on CSP compliance, refer to the [Telerik UI for Blazor Content Security Policy](slug://troubleshooting-csp) article.
This resource provides guidelines on how to configure your Blazor application to comply with CSP requirements when using the Telerik UI for Blazor components.
@@ -90,8 +90,8 @@ We closely monitor the [OWASP Top 10](https://owasp.org/www-project-top-ten/) li
The following resources outline best practices and recommendations for securing the corresponding component and mitigating potential risks:
-* [Editor - Security Guidelines]({%slug editor-overview%}#security)
-* [Upload - Security Guidelines]({%slug upload-overview%}#security)
+* [Editor - Security Guidelines](slug://editor-overview#security)
+* [Upload - Security Guidelines](slug://upload-overview#security)
-For more detailed answers to common security-related questions, please refer to our [Security FAQ page]({%slug security-faq%}).
+For more detailed answers to common security-related questions, please refer to our [Security FAQ page](slug://security-faq).
\ No newline at end of file
diff --git a/src-a11y/configs/aiprompt.aria.yml b/src-a11y/configs/aiprompt.aria.yml
index 5ae4b78577..d2e020b623 100644
--- a/src-a11y/configs/aiprompt.aria.yml
+++ b/src-a11y/configs/aiprompt.aria.yml
@@ -7,9 +7,9 @@ position: 50
after: |
## Keyboard Navigation
- For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview]({%slug accessibility-overview%}#keyboard-navigation) article.
+ For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview](slug://accessibility-overview#keyboard-navigation) article.
## See Also
* [Blazor AIPrompt Demos](https://demos.telerik.com/blazor-ui/aiprompt/overview)
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/autocomplete.aria.yml b/src-a11y/configs/autocomplete.aria.yml
index 5623372183..0dd6e1e581 100644
--- a/src-a11y/configs/autocomplete.aria.yml
+++ b/src-a11y/configs/autocomplete.aria.yml
@@ -11,4 +11,4 @@ after: |
## See Also
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/breadcrumb.aria.yml b/src-a11y/configs/breadcrumb.aria.yml
index 7ed43fec45..75a25d608d 100644
--- a/src-a11y/configs/breadcrumb.aria.yml
+++ b/src-a11y/configs/breadcrumb.aria.yml
@@ -11,4 +11,4 @@ after: |
## See Also
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/button.aria.yml b/src-a11y/configs/button.aria.yml
index d9a7827ff0..b2b4362665 100644
--- a/src-a11y/configs/button.aria.yml
+++ b/src-a11y/configs/button.aria.yml
@@ -11,4 +11,4 @@ after: |
## See Also
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/buttongroup.aria.yml b/src-a11y/configs/buttongroup.aria.yml
index afc8fe9f9f..4c098a8e5a 100644
--- a/src-a11y/configs/buttongroup.aria.yml
+++ b/src-a11y/configs/buttongroup.aria.yml
@@ -11,4 +11,4 @@ after: |
## See Also
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/calendar.aria.yml b/src-a11y/configs/calendar.aria.yml
index 7d722a111d..a6a0b05943 100644
--- a/src-a11y/configs/calendar.aria.yml
+++ b/src-a11y/configs/calendar.aria.yml
@@ -11,4 +11,4 @@ after: |
## See Also
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/card.aria.yml b/src-a11y/configs/card.aria.yml
index 318900f1c2..8268a22469 100644
--- a/src-a11y/configs/card.aria.yml
+++ b/src-a11y/configs/card.aria.yml
@@ -7,9 +7,9 @@ position: 50
after: |
## Keyboard Navigation
- For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview]({%slug accessibility-overview%}#keyboard-navigation) article.
+ For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview](slug://accessibility-overview#keyboard-navigation) article.
## See Also
* [Blazor Card Demos](https://demos.telerik.com/blazor-ui/card/overview)
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/carousel.aria.yml b/src-a11y/configs/carousel.aria.yml
index d3080a71b6..7deaead74d 100644
--- a/src-a11y/configs/carousel.aria.yml
+++ b/src-a11y/configs/carousel.aria.yml
@@ -11,4 +11,4 @@ after: |
## See Also
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/chart.aria.yml b/src-a11y/configs/chart.aria.yml
index 7a2715ef08..134b4d6f21 100644
--- a/src-a11y/configs/chart.aria.yml
+++ b/src-a11y/configs/chart.aria.yml
@@ -11,4 +11,4 @@ after: |
## See Also
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/checkbox.aria.yml b/src-a11y/configs/checkbox.aria.yml
index d3ac6d9cf9..d9ddd9e067 100644
--- a/src-a11y/configs/checkbox.aria.yml
+++ b/src-a11y/configs/checkbox.aria.yml
@@ -7,9 +7,9 @@ position: 50
after: |
## Keyboard Navigation
- For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview]({%slug accessibility-overview%}#keyboard-navigation) article.
+ For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview](slug://accessibility-overview#keyboard-navigation) article.
## See Also
* [Blazor CheckBox Demos](https://demos.telerik.com/blazor-ui/checkbox/overview)
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/chip.aria.yml b/src-a11y/configs/chip.aria.yml
index e64f92a97d..b68efad1de 100644
--- a/src-a11y/configs/chip.aria.yml
+++ b/src-a11y/configs/chip.aria.yml
@@ -11,4 +11,4 @@ after: |
## See Also
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/chiplist.aria.yml b/src-a11y/configs/chiplist.aria.yml
index f0e28baad0..589bb940c0 100644
--- a/src-a11y/configs/chiplist.aria.yml
+++ b/src-a11y/configs/chiplist.aria.yml
@@ -11,4 +11,4 @@ after: |
## See Also
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/chunkprogressbar.aria.yml b/src-a11y/configs/chunkprogressbar.aria.yml
index 78c367607d..a1f8d93138 100644
--- a/src-a11y/configs/chunkprogressbar.aria.yml
+++ b/src-a11y/configs/chunkprogressbar.aria.yml
@@ -7,9 +7,9 @@ position: 50
after: |
## Keyboard Navigation
- For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview]({%slug accessibility-overview%}#keyboard-navigation) article.
+ For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview](slug://accessibility-overview#keyboard-navigation) article.
## See Also
* [Blazor ChunkProgressBar Demos](https://demos.telerik.com/blazor-ui/chunkprogressbar/overview)
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/colorgradient.aria.yml b/src-a11y/configs/colorgradient.aria.yml
index 6461b735a7..31b6b4da48 100644
--- a/src-a11y/configs/colorgradient.aria.yml
+++ b/src-a11y/configs/colorgradient.aria.yml
@@ -11,4 +11,4 @@ after: |
## See Also
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/colorpalette.aria.yml b/src-a11y/configs/colorpalette.aria.yml
index ea7ce5c20a..bdc3a1580c 100644
--- a/src-a11y/configs/colorpalette.aria.yml
+++ b/src-a11y/configs/colorpalette.aria.yml
@@ -11,4 +11,4 @@ after: |
## See Also
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/colorpicker.aria.yml b/src-a11y/configs/colorpicker.aria.yml
index d0d2758d0b..77fecf75aa 100644
--- a/src-a11y/configs/colorpicker.aria.yml
+++ b/src-a11y/configs/colorpicker.aria.yml
@@ -15,4 +15,4 @@ after: |
## See Also
* [Blazor ColorPicker Demos](https://demos.telerik.com/blazor-ui/colorpicker/overview)
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/combobox.aria.yml b/src-a11y/configs/combobox.aria.yml
index 333745dc45..283f49e73d 100644
--- a/src-a11y/configs/combobox.aria.yml
+++ b/src-a11y/configs/combobox.aria.yml
@@ -11,4 +11,4 @@ after: |
## See Also
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/contextmenu.aria.yml b/src-a11y/configs/contextmenu.aria.yml
index 497c6a5c8a..31919144a3 100644
--- a/src-a11y/configs/contextmenu.aria.yml
+++ b/src-a11y/configs/contextmenu.aria.yml
@@ -11,4 +11,4 @@ after: |
## See Also
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/dateinput.aria.yml b/src-a11y/configs/dateinput.aria.yml
index 2efac6f90d..7b8559bbc2 100644
--- a/src-a11y/configs/dateinput.aria.yml
+++ b/src-a11y/configs/dateinput.aria.yml
@@ -11,4 +11,4 @@ after: |
## See Also
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/datepicker.aria.yml b/src-a11y/configs/datepicker.aria.yml
index 51fcea6e75..34236c4ddf 100644
--- a/src-a11y/configs/datepicker.aria.yml
+++ b/src-a11y/configs/datepicker.aria.yml
@@ -11,4 +11,4 @@ after: |
## See Also
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/daterangepicker.aria.yml b/src-a11y/configs/daterangepicker.aria.yml
index 272ff573fd..8904a70044 100644
--- a/src-a11y/configs/daterangepicker.aria.yml
+++ b/src-a11y/configs/daterangepicker.aria.yml
@@ -11,4 +11,4 @@ after: |
## See Also
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/datetimepicker.aria.yml b/src-a11y/configs/datetimepicker.aria.yml
index 3fb0b1067d..3c5dcb7103 100644
--- a/src-a11y/configs/datetimepicker.aria.yml
+++ b/src-a11y/configs/datetimepicker.aria.yml
@@ -11,4 +11,4 @@ after: |
## See Also
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/dialog.aria.yml b/src-a11y/configs/dialog.aria.yml
index 57a475c905..343cd76075 100644
--- a/src-a11y/configs/dialog.aria.yml
+++ b/src-a11y/configs/dialog.aria.yml
@@ -7,9 +7,9 @@ position: 50
after: |
## Keyboard Navigation
- For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview]({%slug accessibility-overview%}#keyboard-navigation) article.
+ For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview](slug://accessibility-overview#keyboard-navigation) article.
## See Also
* [Blazor Dialog Demos](https://demos.telerik.com/blazor-ui/dialog/overview)
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/drawer.aria.yml b/src-a11y/configs/drawer.aria.yml
index e8cd9101f0..3cf6aa3f53 100644
--- a/src-a11y/configs/drawer.aria.yml
+++ b/src-a11y/configs/drawer.aria.yml
@@ -11,4 +11,4 @@ after: |
## See Also
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/dropdownbutton.aria.yml b/src-a11y/configs/dropdownbutton.aria.yml
index 83ad69dc7d..d95cf3b70f 100644
--- a/src-a11y/configs/dropdownbutton.aria.yml
+++ b/src-a11y/configs/dropdownbutton.aria.yml
@@ -11,4 +11,4 @@ after: |
## See Also
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/dropdownlist.aria.yml b/src-a11y/configs/dropdownlist.aria.yml
index 487cf8a1a6..c122633dfd 100644
--- a/src-a11y/configs/dropdownlist.aria.yml
+++ b/src-a11y/configs/dropdownlist.aria.yml
@@ -11,4 +11,4 @@ after: |
## See Also
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/editor.aria.yml b/src-a11y/configs/editor.aria.yml
index 1453335596..40e9e224db 100644
--- a/src-a11y/configs/editor.aria.yml
+++ b/src-a11y/configs/editor.aria.yml
@@ -11,4 +11,4 @@ after: |
## See Also
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/filemanager.aria.yml b/src-a11y/configs/filemanager.aria.yml
index 1bce630b6c..b5f4839206 100644
--- a/src-a11y/configs/filemanager.aria.yml
+++ b/src-a11y/configs/filemanager.aria.yml
@@ -7,9 +7,9 @@ position: 50
after: |
## Keyboard Navigation
- For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview]({%slug accessibility-overview%}#keyboard-navigation) article.
+ For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview](slug://accessibility-overview#keyboard-navigation) article.
## See Also
* [Blazor FileManager Demos](https://demos.telerik.com/blazor-ui/filemanager/overview)
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/filter.aria.yml b/src-a11y/configs/filter.aria.yml
index d91d7689bf..4055e197db 100644
--- a/src-a11y/configs/filter.aria.yml
+++ b/src-a11y/configs/filter.aria.yml
@@ -11,4 +11,4 @@ after: |
## See Also
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/flatcolorpicker.aria.yml b/src-a11y/configs/flatcolorpicker.aria.yml
index 97990e9c2a..7b0395c22b 100644
--- a/src-a11y/configs/flatcolorpicker.aria.yml
+++ b/src-a11y/configs/flatcolorpicker.aria.yml
@@ -15,4 +15,4 @@ after: |
## See Also
* [Blazor FlatColorPicker Demos](https://demos.telerik.com/blazor-ui/flatcolorpicker/overview)
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/form.aria.yml b/src-a11y/configs/form.aria.yml
index 1754025fe7..3afc23c216 100644
--- a/src-a11y/configs/form.aria.yml
+++ b/src-a11y/configs/form.aria.yml
@@ -7,9 +7,9 @@ position: 50
after: |
## Keyboard Navigation
- For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview]({%slug accessibility-overview%}#keyboard-navigation) article.
+ For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview](slug://accessibility-overview#keyboard-navigation) article.
## See Also
* [Blazor Form Demos](https://demos.telerik.com/blazor-ui/form/overview)
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/gantt.aria.yml b/src-a11y/configs/gantt.aria.yml
index b19ff9ca61..aecad86248 100644
--- a/src-a11y/configs/gantt.aria.yml
+++ b/src-a11y/configs/gantt.aria.yml
@@ -7,9 +7,9 @@ position: 50
after: |
## Keyboard Navigation
- For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview]({%slug accessibility-overview%}#keyboard-navigation) article.
+ For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview](slug://accessibility-overview#keyboard-navigation) article.
## See Also
* [Blazor Gantt Demos](https://demos.telerik.com/blazor-ui/gantt/overview)
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/grid.aria.yml b/src-a11y/configs/grid.aria.yml
index 0df4cca6e2..fbfc8780d9 100644
--- a/src-a11y/configs/grid.aria.yml
+++ b/src-a11y/configs/grid.aria.yml
@@ -11,4 +11,4 @@ after: |
## See Also
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/listbox.aria.yml b/src-a11y/configs/listbox.aria.yml
index e950df8d20..fc4ae88cbe 100644
--- a/src-a11y/configs/listbox.aria.yml
+++ b/src-a11y/configs/listbox.aria.yml
@@ -11,4 +11,4 @@ after: |
## See Also
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/listview.aria.yml b/src-a11y/configs/listview.aria.yml
index a31eab010b..4f571e4a9d 100644
--- a/src-a11y/configs/listview.aria.yml
+++ b/src-a11y/configs/listview.aria.yml
@@ -7,9 +7,9 @@ position: 50
after: |
## Keyboard Navigation
- For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview]({%slug accessibility-overview%}#keyboard-navigation) article.
+ For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview](slug://accessibility-overview#keyboard-navigation) article.
## See Also
* [Blazor ListView Demos](https://demos.telerik.com/blazor-ui/listview/overview)
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/maskedtextbox.aria.yml b/src-a11y/configs/maskedtextbox.aria.yml
index 6ce97263f9..7ba5c1a6e9 100644
--- a/src-a11y/configs/maskedtextbox.aria.yml
+++ b/src-a11y/configs/maskedtextbox.aria.yml
@@ -7,9 +7,9 @@ position: 50
after: |
## Keyboard Navigation
- For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview]({%slug accessibility-overview%}#keyboard-navigation) article.
+ For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview](slug://accessibility-overview#keyboard-navigation) article.
## See Also
* [Blazor MaskedTextbox Demos](https://demos.telerik.com/blazor-ui/maskedtextbox/overview)
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/menu.aria.yml b/src-a11y/configs/menu.aria.yml
index 3b84ea9f77..41c99009d1 100644
--- a/src-a11y/configs/menu.aria.yml
+++ b/src-a11y/configs/menu.aria.yml
@@ -11,4 +11,4 @@ after: |
## See Also
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/multicolumncombobox.aria.yml b/src-a11y/configs/multicolumncombobox.aria.yml
index 83afcc5db6..337365717c 100644
--- a/src-a11y/configs/multicolumncombobox.aria.yml
+++ b/src-a11y/configs/multicolumncombobox.aria.yml
@@ -11,4 +11,4 @@ after: |
## See Also
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/multiselect.aria.yml b/src-a11y/configs/multiselect.aria.yml
index 3fd8797889..a3783546f3 100644
--- a/src-a11y/configs/multiselect.aria.yml
+++ b/src-a11y/configs/multiselect.aria.yml
@@ -11,4 +11,4 @@ after: |
## See Also
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/notification.aria.yml b/src-a11y/configs/notification.aria.yml
index 1148442281..cf0e241381 100644
--- a/src-a11y/configs/notification.aria.yml
+++ b/src-a11y/configs/notification.aria.yml
@@ -7,9 +7,9 @@ position: 50
after: |
## Keyboard Navigation
- For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview]({%slug accessibility-overview%}#keyboard-navigation) article.
+ For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview](slug://accessibility-overview#keyboard-navigation) article.
## See Also
* [Blazor Notification Demos](https://demos.telerik.com/blazor-ui/notification/overview)
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/numerictextbox.aria.yml b/src-a11y/configs/numerictextbox.aria.yml
index 1a79c61590..bb658a2c99 100644
--- a/src-a11y/configs/numerictextbox.aria.yml
+++ b/src-a11y/configs/numerictextbox.aria.yml
@@ -11,4 +11,4 @@ after: |
## See Also
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/pager.aria.yml b/src-a11y/configs/pager.aria.yml
index 1c3b6443a4..27449e2ad6 100644
--- a/src-a11y/configs/pager.aria.yml
+++ b/src-a11y/configs/pager.aria.yml
@@ -11,4 +11,4 @@ after: |
## See Also
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/panelbar.aria.yml b/src-a11y/configs/panelbar.aria.yml
index 05559e725c..fafef048cc 100644
--- a/src-a11y/configs/panelbar.aria.yml
+++ b/src-a11y/configs/panelbar.aria.yml
@@ -11,4 +11,4 @@ after: |
## See Also
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/pdfviewer.aria.yml b/src-a11y/configs/pdfviewer.aria.yml
index b3d3937cef..464541114b 100644
--- a/src-a11y/configs/pdfviewer.aria.yml
+++ b/src-a11y/configs/pdfviewer.aria.yml
@@ -7,9 +7,9 @@ position: 50
after: |
## Keyboard Navigation
- For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview]({%slug accessibility-overview%}#keyboard-navigation) article.
+ For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview](slug://accessibility-overview#keyboard-navigation) article.
## See Also
* [Blazor PDFViewer Demos](https://demos.telerik.com/blazor-ui/pdfviewer/overview)
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/pivotgrid.aria.yml b/src-a11y/configs/pivotgrid.aria.yml
index aa585d8105..25ac97c004 100644
--- a/src-a11y/configs/pivotgrid.aria.yml
+++ b/src-a11y/configs/pivotgrid.aria.yml
@@ -7,9 +7,9 @@ position: 50
after: |
## Keyboard Navigation
- For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview]({%slug accessibility-overview%}#keyboard-navigation) article.
+ For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview](slug://accessibility-overview#keyboard-navigation) article.
## See Also
* [Blazor PivotGrid Demos](https://demos.telerik.com/blazor-ui/pivotgrid/overview)
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/popover.aria.yml b/src-a11y/configs/popover.aria.yml
index 9c38430d22..4f8e9bf055 100644
--- a/src-a11y/configs/popover.aria.yml
+++ b/src-a11y/configs/popover.aria.yml
@@ -7,9 +7,9 @@ position: 50
after: |
## Keyboard Navigation
- For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview]({%slug accessibility-overview%}#keyboard-navigation) article.
+ For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview](slug://accessibility-overview#keyboard-navigation) article.
## See Also
* [Blazor Popover Demos](https://demos.telerik.com/blazor-ui/popover/overview)
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/progressbar.aria.yml b/src-a11y/configs/progressbar.aria.yml
index bde60d14a6..b311e15d58 100644
--- a/src-a11y/configs/progressbar.aria.yml
+++ b/src-a11y/configs/progressbar.aria.yml
@@ -7,9 +7,9 @@ position: 50
after: |
## Keyboard Navigation
- For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview]({%slug accessibility-overview%}#keyboard-navigation) article.
+ For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview](slug://accessibility-overview#keyboard-navigation) article.
## See Also
* [Blazor ProgressBar Demos](https://demos.telerik.com/blazor-ui/progressbar/overview)
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/radiogroup.aria.yml b/src-a11y/configs/radiogroup.aria.yml
index efa35513b3..33f0b0964c 100644
--- a/src-a11y/configs/radiogroup.aria.yml
+++ b/src-a11y/configs/radiogroup.aria.yml
@@ -11,4 +11,4 @@ after: |
## See Also
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/rangeslider.aria.yml b/src-a11y/configs/rangeslider.aria.yml
index 59a7733084..5847c1694d 100644
--- a/src-a11y/configs/rangeslider.aria.yml
+++ b/src-a11y/configs/rangeslider.aria.yml
@@ -11,4 +11,4 @@ after: |
## See Also
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/rating.aria.yml b/src-a11y/configs/rating.aria.yml
index f3fb28a282..a00e85b493 100644
--- a/src-a11y/configs/rating.aria.yml
+++ b/src-a11y/configs/rating.aria.yml
@@ -11,4 +11,4 @@ after: |
## See Also
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/sankey.aria.yml b/src-a11y/configs/sankey.aria.yml
index ddfdc0a019..7681520410 100644
--- a/src-a11y/configs/sankey.aria.yml
+++ b/src-a11y/configs/sankey.aria.yml
@@ -7,9 +7,9 @@ position: 50
after: |
## Keyboard Navigation
- For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview]({%slug accessibility-overview%}#keyboard-navigation) article.
+ For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview](slug://accessibility-overview#keyboard-navigation) article.
## See Also
* [Blazor Sankey Demos](https://demos.telerik.com/blazor-ui/sankey/overview)
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/scheduler.aria.yml b/src-a11y/configs/scheduler.aria.yml
index cb3e1a1289..f3ef9db3ec 100644
--- a/src-a11y/configs/scheduler.aria.yml
+++ b/src-a11y/configs/scheduler.aria.yml
@@ -11,4 +11,4 @@ after: |
## See Also
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/signature.aria.yml b/src-a11y/configs/signature.aria.yml
index fa9e9aa53a..3fd6ff40a9 100644
--- a/src-a11y/configs/signature.aria.yml
+++ b/src-a11y/configs/signature.aria.yml
@@ -7,9 +7,9 @@ position: 50
after: |
## Keyboard Navigation
- For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview]({%slug accessibility-overview%}#keyboard-navigation) article.
+ For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview](slug://accessibility-overview#keyboard-navigation) article.
## See Also
* [Blazor Signature Demos](https://demos.telerik.com/blazor-ui/signature/overview)
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/skeleton.aria.yml b/src-a11y/configs/skeleton.aria.yml
index 35b17539ef..9f8d2b5889 100644
--- a/src-a11y/configs/skeleton.aria.yml
+++ b/src-a11y/configs/skeleton.aria.yml
@@ -7,9 +7,9 @@ position: 50
after: |
## Keyboard Navigation
- For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview]({%slug accessibility-overview%}#keyboard-navigation) article.
+ For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview](slug://accessibility-overview#keyboard-navigation) article.
## See Also
* [Blazor Skeleton Demos](https://demos.telerik.com/blazor-ui/skeleton/overview)
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/slider.aria.yml b/src-a11y/configs/slider.aria.yml
index aceac5c1da..5b2967fd87 100644
--- a/src-a11y/configs/slider.aria.yml
+++ b/src-a11y/configs/slider.aria.yml
@@ -11,4 +11,4 @@ after: |
## See Also
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/splitbutton.aria.yml b/src-a11y/configs/splitbutton.aria.yml
index ccabbc68bd..543088dc41 100644
--- a/src-a11y/configs/splitbutton.aria.yml
+++ b/src-a11y/configs/splitbutton.aria.yml
@@ -11,4 +11,4 @@ after: |
## See Also
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/splitter.aria.yml b/src-a11y/configs/splitter.aria.yml
index 7e5fa3a684..1e75dcbfea 100644
--- a/src-a11y/configs/splitter.aria.yml
+++ b/src-a11y/configs/splitter.aria.yml
@@ -11,4 +11,4 @@ after: |
## See Also
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/spreadsheet.aria.yml b/src-a11y/configs/spreadsheet.aria.yml
index cde845f890..3b52a979fc 100644
--- a/src-a11y/configs/spreadsheet.aria.yml
+++ b/src-a11y/configs/spreadsheet.aria.yml
@@ -12,4 +12,4 @@ after: |
## See Also
* [Blazor Spreadsheet Demos](https://demos.telerik.com/blazor-ui/spreadsheet/overview)
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/stepper.aria.yml b/src-a11y/configs/stepper.aria.yml
index fa6253d51f..80b5f4194b 100644
--- a/src-a11y/configs/stepper.aria.yml
+++ b/src-a11y/configs/stepper.aria.yml
@@ -11,4 +11,4 @@ after: |
## See Also
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/switch.aria.yml b/src-a11y/configs/switch.aria.yml
index fb30e3e54f..0f7f3d7e40 100644
--- a/src-a11y/configs/switch.aria.yml
+++ b/src-a11y/configs/switch.aria.yml
@@ -11,4 +11,4 @@ after: |
## See Also
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/tabstrip.aria.yml b/src-a11y/configs/tabstrip.aria.yml
index 844ffb7bb4..e4f22b5a97 100644
--- a/src-a11y/configs/tabstrip.aria.yml
+++ b/src-a11y/configs/tabstrip.aria.yml
@@ -11,4 +11,4 @@ after: |
## See Also
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/textarea.aria.yml b/src-a11y/configs/textarea.aria.yml
index 9e714f1061..4928276faa 100644
--- a/src-a11y/configs/textarea.aria.yml
+++ b/src-a11y/configs/textarea.aria.yml
@@ -7,9 +7,9 @@ position: 50
after: |
## Keyboard Navigation
- For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview]({%slug accessibility-overview%}#keyboard-navigation) article.
+ For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview](slug://accessibility-overview#keyboard-navigation) article.
## See Also
* [Blazor TextArea Demos](https://demos.telerik.com/blazor-ui/textarea/overview)
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/textbox.aria.yml b/src-a11y/configs/textbox.aria.yml
index 4709e60654..dcf08d10a4 100644
--- a/src-a11y/configs/textbox.aria.yml
+++ b/src-a11y/configs/textbox.aria.yml
@@ -7,9 +7,9 @@ position: 50
after: |
## Keyboard Navigation
- For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview]({%slug accessibility-overview%}#keyboard-navigation) article.
+ For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview](slug://accessibility-overview#keyboard-navigation) article.
## See Also
* [Blazor TextBox Demos](https://demos.telerik.com/blazor-ui/textbox/overview)
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/tilelayout.aria.yml b/src-a11y/configs/tilelayout.aria.yml
index 2b23f0ccad..411477ddb3 100644
--- a/src-a11y/configs/tilelayout.aria.yml
+++ b/src-a11y/configs/tilelayout.aria.yml
@@ -7,9 +7,9 @@ position: 50
after: |
## Keyboard Navigation
- For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview]({%slug accessibility-overview%}#keyboard-navigation) article.
+ For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview](slug://accessibility-overview#keyboard-navigation) article.
## See Also
* [Blazor TileLayout Demos](https://demos.telerik.com/blazor-ui/tilelayout/overview)
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/timepicker.aria.yml b/src-a11y/configs/timepicker.aria.yml
index 1f1cc073f4..e613cc5c55 100644
--- a/src-a11y/configs/timepicker.aria.yml
+++ b/src-a11y/configs/timepicker.aria.yml
@@ -11,4 +11,4 @@ after: |
## See Also
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/togglebutton.aria.yml b/src-a11y/configs/togglebutton.aria.yml
index 0179451033..81689927c4 100644
--- a/src-a11y/configs/togglebutton.aria.yml
+++ b/src-a11y/configs/togglebutton.aria.yml
@@ -11,4 +11,4 @@ after: |
## See Also
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/toolbar.aria.yml b/src-a11y/configs/toolbar.aria.yml
index d6cd968578..b83d8b5757 100644
--- a/src-a11y/configs/toolbar.aria.yml
+++ b/src-a11y/configs/toolbar.aria.yml
@@ -11,4 +11,4 @@ after: |
## See Also
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/tooltip.aria.yml b/src-a11y/configs/tooltip.aria.yml
index 7c9c78032c..1d5ddf69f3 100644
--- a/src-a11y/configs/tooltip.aria.yml
+++ b/src-a11y/configs/tooltip.aria.yml
@@ -7,9 +7,9 @@ position: 50
after: |
## Keyboard Navigation
- For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview]({%slug accessibility-overview%}#keyboard-navigation) article.
+ For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview](slug://accessibility-overview#keyboard-navigation) article.
## See Also
* [Blazor Tooltip Demos](https://demos.telerik.com/blazor-ui/tooltip/overview)
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/treelist.aria.yml b/src-a11y/configs/treelist.aria.yml
index f589768e00..7ee45abbb6 100644
--- a/src-a11y/configs/treelist.aria.yml
+++ b/src-a11y/configs/treelist.aria.yml
@@ -11,5 +11,5 @@ after: |
## See Also
- * [Blazor TreeList Accessibility Example]({%slug treelist-accessibility-overview%}#blazor-treelist-accessibility-example)
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Blazor TreeList Accessibility Example](slug://treelist-accessibility-overview#blazor-treelist-accessibility-example)
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/treeview.aria.yml b/src-a11y/configs/treeview.aria.yml
index 85a0c88c37..4e682d58cf 100644
--- a/src-a11y/configs/treeview.aria.yml
+++ b/src-a11y/configs/treeview.aria.yml
@@ -11,4 +11,4 @@ after: |
## See Also
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/upload.aria.yml b/src-a11y/configs/upload.aria.yml
index bb36e61b03..4162a5cc83 100644
--- a/src-a11y/configs/upload.aria.yml
+++ b/src-a11y/configs/upload.aria.yml
@@ -11,4 +11,4 @@ after: |
## See Also
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/window.aria.yml b/src-a11y/configs/window.aria.yml
index 3286d68a43..50f06ab8d8 100644
--- a/src-a11y/configs/window.aria.yml
+++ b/src-a11y/configs/window.aria.yml
@@ -11,4 +11,4 @@ after: |
## See Also
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/src-a11y/configs/wizard.aria.yml b/src-a11y/configs/wizard.aria.yml
index f4b73ae437..877d5254a8 100644
--- a/src-a11y/configs/wizard.aria.yml
+++ b/src-a11y/configs/wizard.aria.yml
@@ -11,4 +11,4 @@ after: |
## See Also
- * [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
+ * [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
diff --git a/styling-and-themes/custom-theme.md b/styling-and-themes/custom-theme.md
index 8d7b44d01f..31dc15aa2e 100644
--- a/styling-and-themes/custom-theme.md
+++ b/styling-and-themes/custom-theme.md
@@ -77,7 +77,7 @@ The example below shows how to customize some of the theme variables.
## Overriding Theme Styles
-You can [override theme styles with custom CSS]({%slug themes-override%}), no matter if the app is using a built-in or custom theme. This approach makes sense only for a relatively small number of customizations. Beyond that, choose some of the other alternatives on this page.
+You can [override theme styles with custom CSS](slug://themes-override), no matter if the app is using a built-in or custom theme. This approach makes sense only for a relatively small number of customizations. Beyond that, choose some of the other alternatives on this page.
Upgrading may require changes to the additional custom CSS code, but only if there are breaking changes in the HTML output and styling.
@@ -91,10 +91,10 @@ Each
` of the web page. The exact project file that contains the `` tag depends on the .NET version and the Blazor application type. See our [Getting Started guides]({%slug blazor-overview%}#getting-started) for more information.
+To register a theme, you must reference its stylesheet in the `` of the web page. The exact project file that contains the `` tag depends on the .NET version and the Blazor application type. See our [Getting Started guides](slug://blazor-overview#getting-started) for more information.
There are three ways to load a Telerik theme, in terms of physical CSS file location. Note that each option provides access to a different number of theme swatches.
-* [Load a CSS theme as a static asset from the `Telerik.UI.for.Blazor` NuGet package](#loading-themes-from-the-nuget-package). This is the easiest option and it doesn't require maintenance during [Telerik UI for Blazor version upgrades]({%slug upgrade-tutorial%}). However, you can use only the *Main* swatch of each theme and the *Ocean Blue* swatch of the *Default* theme.
+* [Load a CSS theme as a static asset from the `Telerik.UI.for.Blazor` NuGet package](#loading-themes-from-the-nuget-package). This is the easiest option and it doesn't require maintenance during [Telerik UI for Blazor version upgrades](slug://upgrade-tutorial). However, you can use only the *Main* swatch of each theme and the *Ocean Blue* swatch of the *Default* theme.
* Load a CSS theme from a remote URL, for example, CDN. The dedicated documentation of each theme provides a list of swatches and their URLs.
* Load a CSS theme as a local file in the `wwwroot` folder in the Blazor app. This option is relevant to the following cases:
- * When using [custom themes]({%slug themes-customize%}).
- * When [creating]({%slug getting-started-vs-integration-new-project%}) or [converting]({%slug getting-started-vs-integration-convert-project%}) Telerik Blazor apps with the [Telerik UI for Blazor Visual Studio extension]({%slug getting-started-vs-integration-overview%}).
- * When using themes from the Telerik UI for Blazor [MSI installer]({%slug installation/msi%}) or [ZIP archive]({%slug installation/zip%}). The CSS files are in the `swatches` folder.
- * When using [LibMan]({%slug common-kb-telerik-themes-libman%}) or
npm to obtain a specific Telerik theme version. In this case, you can use all built-in theme swatches.
+ * When using [custom themes](slug://themes-customize).
+ * When [creating](slug://getting-started-vs-integration-new-project) or [converting](slug://getting-started-vs-integration-convert-project) Telerik Blazor apps with the [Telerik UI for Blazor Visual Studio extension](slug://getting-started-vs-integration-overview).
+ * When using themes from the Telerik UI for Blazor [MSI installer](slug://installation/msi) or [ZIP archive](slug://installation/zip). The CSS files are in the `swatches` folder.
+ * When using [LibMan](slug://common-kb-telerik-themes-libman) or
npm to obtain a specific Telerik theme version. In this case, you can use all built-in theme swatches.
> The Blazor app must load only one Telerik theme file at a time. Upgrade the theme with every Telerik UI for Blazor version upgrade, unless you are loading the theme as a static NuGet asset.
@@ -73,7 +73,7 @@ There are three ways to load a Telerik theme, in terms of physical CSS file loca
The easiest way to load a Telerik theme in a Blazor app is to reference a static asset from the NuGet package. The .NET SDK will copy the CSS file to the output folder during build automatically. Static assets provide the following benefits:
* The application relies on available local resources, instead of third parties and remote URLs.
-* The theme URL does not change across component versions, which makes product updates easier. [Add a cache buster to avoid possible browser caching issues]({%slug common-kb-browser-cache-buster%}).
+* The theme URL does not change across component versions, which makes product updates easier. [Add a cache buster to avoid possible browser caching issues](slug://common-kb-browser-cache-buster).
The `Telerik.UI.for.Blazor` NuGet package includes only the *Main* swatch of each theme and the *Ocean Blue* swatch of the *Default* theme. The code snippet below shows all available CSS files in the NuGet package and their correct URLs. To use another swatch, see the section [Using a Theme](#using-a-theme) above.
@@ -104,17 +104,17 @@ The `Telerik.UI.for.Blazor` NuGet package includes only the *Main* swatch of eac
The Telerik themes are decoupled from the Telerik Blazor components, which leads to the following usage requirements:
-* When using a CSS theme as local file in `wwwroot`, [replace the file every time you change the Telerik UI for Blazor version]({%slug upgrade-tutorial%}). This includes apps [created with the Telerik Blazor Visual Studio extension without CDN support]({%slug getting-started-vs-integration-new-project%}#step-3-select-theme).
+* When using a CSS theme as local file in `wwwroot`, [replace the file every time you change the Telerik UI for Blazor version](slug://upgrade-tutorial). This includes apps [created with the Telerik Blazor Visual Studio extension without CDN support](slug://getting-started-vs-integration-new-project#step-3-select-theme).
* When loading
theme swatches from a CDN, make sure that the theme version is compatible with the Telerik UI for Blazor version. Our [release notes](https://www.telerik.com/support/whats-new/blazor-ui/release-history) provide theme compatibility information for each components version. You can also use a
newer minor theme version, which doesn't contain breaking changes. In other words, the latest major theme version may be still incompatible with the latest version of Telerik UI for Blazor.
## Next Steps
-* [Modify a built-in theme or create a custom theme]({%slug themes-customize%})
+* [Modify a built-in theme or create a custom theme](slug://themes-customize)
* [Explore the Telerik and Kendo UI Kits for Figma](https://www.telerik.com/design-system/docs/resources/figma-ui-kits/)
## See Also
-* [Change the Theme at Runtime]({%slug common-kb-change-theme-runtime%})
+* [Change the Theme at Runtime](slug://common-kb-change-theme-runtime)
*
Default Ocean Blue Accessibility Swatch
* [Live UI for Blazor Demos](https://demos.telerik.com/blazor-ui)
diff --git a/styling-and-themes/themebuilder.md b/styling-and-themes/themebuilder.md
index 759f485bf4..b9f456ce60 100644
--- a/styling-and-themes/themebuilder.md
+++ b/styling-and-themes/themebuilder.md
@@ -10,7 +10,7 @@ position: 20
# Progress ThemeBuilder
-[ThemeBuilder](https://themebuilderapp.telerik.com) is a SaaS tool that enables you to create custom themes and instantly preview how they affect the appearance of the components. The tool generates a [CSS file that you can use in your Blazor app]({%slug themes-customize%}#loading-custom-themes) instead of a built-in theme.
+[ThemeBuilder](https://themebuilderapp.telerik.com) is a SaaS tool that enables you to create custom themes and instantly preview how they affect the appearance of the components. The tool generates a [CSS file that you can use in your Blazor app](slug://themes-customize#loading-custom-themes) instead of a built-in theme.
## Key Procedures
diff --git a/system-requirements.md b/system-requirements.md
index a191b58f58..ccecb7b2b4 100644
--- a/system-requirements.md
+++ b/system-requirements.md
@@ -80,4 +80,4 @@ Use the following browsers to access web applications with Telerik UI for Blazor
## See Also
-* [Old Versions Support Policy]({%slug old_versions_support_policy%})
+* [Old Versions Support Policy](slug://old_versions_support_policy)
diff --git a/testing/unit-testing-with-bunit.md b/testing/unit-testing-with-bunit.md
index 976775c8a3..ede1347936 100644
--- a/testing/unit-testing-with-bunit.md
+++ b/testing/unit-testing-with-bunit.md
@@ -103,7 +103,7 @@ Considering the above-listed JS limitation, you may experience some issues when
| --- | --- |
| Issue | In test environment, `OnRead` is not raised after invoking `Rebind`. |
| Cause | When `Rebind` is called, the Grid shows a loader. This loader is invoked with JS Interop, so the test fails silently. |
-| Workaround | Disable the [built-in loader]({%slug grid-loading%}). |
+| Workaround | Disable the [built-in loader](slug://grid-loading). |
## Resources
diff --git a/troubleshooting/csp.md b/troubleshooting/csp.md
index 5f2e1bc162..f99ff12eb3 100644
--- a/troubleshooting/csp.md
+++ b/troubleshooting/csp.md
@@ -27,17 +27,17 @@ In general, a strict CSP can disable web app features, such as:
Telerik UI for Blazor components need the following exceptions to strict CSP. Some of them depend on the product version or product usage.
* Allow inline styles (`'unsafe-inline'`) to use component parameters such as `Width`, `Height`, `RowHeight`, `ItemHeight`, `Top`, `Left`, etc. In addition, some components rely on inline styles for their rich functionality and UX.
-* Allow data URIs (`data:`) for images that are embedded in the [CSS themes]({%slug themes-overview%}). These images are used for styled checkboxes and radio buttons, Slider ticks, and others.
-* (optional) Allow `https://blazor.cdn.telerik.com` as a source when using [the Telerik CDN]({%slug common-features-cdn%}) for styles or scripts.
+* Allow data URIs (`data:`) for images that are embedded in the [CSS themes](slug://themes-overview). These images are used for styled checkboxes and radio buttons, Slider ticks, and others.
+* (optional) Allow `https://blazor.cdn.telerik.com` as a source when using [the Telerik CDN](slug://common-features-cdn) for styles or scripts.
* (optional) Allow `https://unpkg.com` as a source when using it as a
CDN for styles.
### Legacy Settings
The following items concern older product versions:
-* *(for versions 6.x)* Allow script evaluation (`'unsafe-eval'`), which is required by the [Spreadsheet]({%slug spreadsheet-overview%}) for cell validation and formula compilation. If you don't use the Spreadsheet component in your Blazor app, you can [build a CSP compliant `telerik-blazor.js` file without the Spreadsheet]({%slug common-kb-remove-components-from-telerik-blazor-js%}).
-* *(up to version 4.6.0)* Allow `data:` URIs for `font-src` to use [font icons]({%slug common-features-icons%}). Later versions use a separate file for the `WebComponentsIcons` icon font. This font file is referenced by the [font icon stylesheet]({%slug common-features-icons%}#font-icon-stylesheet).
-* *(up to version 4.4.0)* Allow `unsafe-eval` to use [Chart label templates]({%slug components/chart/label-template-format%}) and [Map templates]({%slug components/map/overview%}#content-security-policy). These templates used to rely on `eval()`. Starting with version 4.5.0, the Chart and Map templates support a different template mechanism, which doesn't require `unsafe-eval`.
+* *(for versions 6.x)* Allow script evaluation (`'unsafe-eval'`), which is required by the [Spreadsheet](slug://spreadsheet-overview) for cell validation and formula compilation. If you don't use the Spreadsheet component in your Blazor app, you can [build a CSP compliant `telerik-blazor.js` file without the Spreadsheet](slug://common-kb-remove-components-from-telerik-blazor-js).
+* *(up to version 4.6.0)* Allow `data:` URIs for `font-src` to use [font icons](slug://common-features-icons). Later versions use a separate file for the `WebComponentsIcons` icon font. This font file is referenced by the [font icon stylesheet](slug://common-features-icons#font-icon-stylesheet).
+* *(up to version 4.4.0)* Allow `unsafe-eval` to use [Chart label templates](slug://components/chart/label-template-format) and [Map templates](slug://components/map/overview#content-security-policy). These templates used to rely on `eval()`. Starting with version 4.5.0, the Chart and Map templates support a different template mechanism, which doesn't require `unsafe-eval`.
## Examples
diff --git a/troubleshooting/general-issues.md b/troubleshooting/general-issues.md
index deeaf4762c..5ffdac9fc9 100644
--- a/troubleshooting/general-issues.md
+++ b/troubleshooting/general-issues.md
@@ -12,25 +12,25 @@ position: 1
This page provides solutions for common issues you may encounter while working with Telerik UI for Blazor components.
-* [TelerikRootComponent is missing]({%slug common-kb-component-requires-telerikrootcomponent%})
+* [TelerikRootComponent is missing](slug://common-kb-component-requires-telerikrootcomponent)
* [Popups do not work](#popups-do-not-work)
* [Wrong popup position](#wrong-popup-position)
* [Unable to find package Telerik.Documents.SpreadsheetStreaming](#unable-to-find-package-telerik-documents-spreadsheetstreaming)
* [Cannot provide a value for property 'Localizer'](#cannot-provide-a-value-for-property-localizer)
* [Slow Performance](#slow-performance)
* [Failed to find a valid digest in the 'integrity' attribute for resource ... with computed SHA-256 integrity ...](#failed-to-find-a-valid-digest-in-the-integrity-attribute-for-resource-with-computed-sha-256-integrity)
-* [JavaScript errors]({%slug troubleshooting-js-errors%})
-* [Issues after deployment]({%slug deployment-troubleshooting%})
-* [Content Security Policy]({%slug troubleshooting-csp%})
-* [NuGet feed troubleshooting]({%slug troubleshooting-nuget%})
-* [Upload troubleshooting]({%slug upload-troubleshooting%})
+* [JavaScript errors](slug://troubleshooting-js-errors)
+* [Issues after deployment](slug://deployment-troubleshooting)
+* [Content Security Policy](slug://troubleshooting-csp)
+* [NuGet feed troubleshooting](slug://troubleshooting-nuget)
+* [Upload troubleshooting](slug://upload-troubleshooting)
## Popups Do Not Work
There are three common reasons for this
-* Missing [`
`]({%slug getting-started/what-you-need%}#telerikrootcomponent) from the app.
-* [Missing `telerik-blazor.js` file]({%slug troubleshooting-js-errors%}#telerikblazor-was-undefined)
+* Missing [``](slug://getting-started/what-you-need#telerikrootcomponent) from the app.
+* [Missing `telerik-blazor.js` file](slug://troubleshooting-js-errors#telerikblazor-was-undefined)
* Special positioning on the `` element or any other parent of the `TelerikRootComponent`.
The `` element is the topmost component that a developer can access in Blazor. This means that we cannot place our popups higher than that in the DOM. Thus, their position and visibility depend on the position of the `` element matching the position of the `` element.
@@ -56,7 +56,7 @@ app {
The position of popups (Window, various dropdowns such as DropDownList, ComboBox, DatePicker) can be wrong or offset.
-The most common reason for such a problem is that the [``]({%slug rootcomponent-overview%}) does not match the `` and the browser viewport - this is required because that component is the topmost element our components can access in order to render popups/dropdowns.
+The most common reason for such a problem is that the [``](slug://rootcomponent-overview) does not match the `` and the browser viewport - this is required because that component is the topmost element our components can access in order to render popups/dropdowns.
There are several common cases when such a mismatch occurs:
@@ -87,9 +87,9 @@ The most common reasons and solutions for seeing this error (being unable to res
* An offline package source is being used that does not contain it. Make sure that you add the packages from both the `packages` and `dpl` folders to such a custom local feed.
-* There is an issue with connecting to our online feed. For example, a firewall, network downtime or wrong credentials are used. Check the [Troubleshooting NuGet Feed Issues]({%slug installation/nuget%}#troubleshooting) section of the documentation to see how to handle that.
+* There is an issue with connecting to our online feed. For example, a firewall, network downtime or wrong credentials are used. Check the [Troubleshooting NuGet Feed Issues](slug://installation/nuget#troubleshooting) section of the documentation to see how to handle that.
-* There is a mismatch between the versions available for restore and the referenced versions, while the Visual Studio "treat warnings as errors" setting is turned on. This can happen if one version is referenced, but another is available (for example, only certain versions are available in a custom local feed for the [Document Processing]({%slug dpl-in-blazor%}) packages, but the main package references an older version). In such cases, the tooling would usually resolve the newest version, but it will show a warning and VS can treat it as an error and not let you build. The solution is to check the version that is referenced by `Telerik.UI.for.Blazor` and ensure you can access that. Cleaning the solution, manually restoring the packages and re-building can also help.
+* There is a mismatch between the versions available for restore and the referenced versions, while the Visual Studio "treat warnings as errors" setting is turned on. This can happen if one version is referenced, but another is available (for example, only certain versions are available in a custom local feed for the [Document Processing](slug://dpl-in-blazor) packages, but the main package references an older version). In such cases, the tooling would usually resolve the newest version, but it will show a warning and VS can treat it as an error and not let you build. The solution is to check the version that is referenced by `Telerik.UI.for.Blazor` and ensure you can access that. Cleaning the solution, manually restoring the packages and re-building can also help.
@@ -101,9 +101,9 @@ If you get an error similar to this one:
There can be two common causes for the problem:
-* The [Telerik services are not registered]({%slug getting-started/what-you-need%}#service) in the app, a line similar to `builder.Services.AddTelerikBlazor();` is missing.
+* The [Telerik services are not registered](slug://getting-started/what-you-need#service) in the app, a line similar to `builder.Services.AddTelerikBlazor();` is missing.
-* The application uses localization, or there is a code snippet that does (e.g., a grid with custom buttons that are localized, copied over from another place), but the current app does not provide the necessary project-specific service. You can read more about implementing one in the [Localization]({%slug globalization-localization%}) article.
+* The application uses localization, or there is a code snippet that does (e.g., a grid with custom buttons that are localized, copied over from another place), but the current app does not provide the necessary project-specific service. You can read more about implementing one in the [Localization](slug://globalization-localization) article.
## Slow Performance
@@ -119,9 +119,9 @@ When building a Blazor app, especially on the WebAssembly flavor, it is likely t
There are also certain measures a web app should take to improve its performance in general. For example:
-* Enable [Paging]({%slug components/grid/features/paging%}) or [Virtual Scrolling]({%slug components/grid/virtual-scrolling%}) in the grid, and use a reasonable page size (for example, 10 to 20 or 40, as more than 20 items can rarely fit on a screen anyway). Also, if you have many columns, enable [Column Virtualization]({%slug grid-columns-virtual%}).
+* Enable [Paging](slug://components/grid/features/paging) or [Virtual Scrolling](slug://components/grid/virtual-scrolling) in the grid, and use a reasonable page size (for example, 10 to 20 or 40, as more than 20 items can rarely fit on a screen anyway). Also, if you have many columns, enable [Column Virtualization](slug://grid-columns-virtual).
-* Avoid loading all the data at once, only load and render relevant chunks. For example, use the [OnRead event of the Grid]({%slug components/grid/manual-operations%}) for the grid to perform all operations, and use [custom filtering in the ComboBox through its own OnRead event]({%slug components/combobox/events%}#onread). This also applies to creating lists of a lot of components in your own `foreach` loops - consider implementing your own virtual scrolling or use the [Telerik Pager]({%slug pager-overview%}) to help you separate them into smaller sets.
+* Avoid loading all the data at once, only load and render relevant chunks. For example, use the [OnRead event of the Grid](slug://components/grid/manual-operations) for the grid to perform all operations, and use [custom filtering in the ComboBox through its own OnRead event](slug://components/combobox/events#onread). This also applies to creating lists of a lot of components in your own `foreach` loops - consider implementing your own virtual scrolling or use the [Telerik Pager](slug://pager-overview) to help you separate them into smaller sets.
* When using a series of your own components on the page, consider overriding their `ShouldRender` methods so they render only when needed. For example, an `EventCallback` whose handler is an `async Task` will render its own component, its parent and siblings twice, and you can reduce that to once.
@@ -131,10 +131,10 @@ There are also certain measures a web app should take to improve its performance
## Failed to find a valid digest in the 'integrity' attribute for resource ... with computed SHA-256 integrity ...
-The error is a general Blazor WebAssembly issue, which can result from the build process, publishing process, or browser cache. Our [knowledge base article about the `Failed to find a valid digest in the 'integrity' attribute` exception]({%slug common-kb-failed-to-find%}) contains discussions and documentation with possible solutions.
+The error is a general Blazor WebAssembly issue, which can result from the build process, publishing process, or browser cache. Our [knowledge base article about the `Failed to find a valid digest in the 'integrity' attribute` exception](slug://common-kb-failed-to-find) contains discussions and documentation with possible solutions.
## See Also
-* [JavaScript Errors Troubleshooting]({%slug troubleshooting-js-errors%})
-* [Content Security Policy]({%slug troubleshooting-csp%})
+* [JavaScript Errors Troubleshooting](slug://troubleshooting-js-errors)
+* [Content Security Policy](slug://troubleshooting-csp)
diff --git a/troubleshooting/js-errors.md b/troubleshooting/js-errors.md
index 5693ed9c35..aa5d7969fb 100644
--- a/troubleshooting/js-errors.md
+++ b/troubleshooting/js-errors.md
@@ -39,24 +39,24 @@ If you get such errors, the reason may be:
You can check if this is the case by inspecting the Network tab of your browser console to see if `telerik-blazor.js` is served successfully. Some common causes for the missing JS Interop file are:
-* The application is missing references to the needed [assets]({%slug getting-started/what-you-need%}#css-theme-and-javascript-files).
+* The application is missing references to the needed [assets](slug://getting-started/what-you-need#css-theme-and-javascript-files).
* Network setup blocks access to the cloud, and thus, to our CDN. If this is the case, you have two options:
* Discuss the case with your network administrators to have our CDN allowed.
- * Use [static assets]({%slug getting-started/what-you-need%}#css-theme-and-javascript-files) from the app folder to avoid going to the cloud.
+ * Use [static assets](slug://getting-started/what-you-need#css-theme-and-javascript-files) from the app folder to avoid going to the cloud.
-* The application was upgraded from a trial to a commercial license, but the path to the file was not. See the [Upgrade from Trial to Commercial]({%slug upgrade-tutorial%}#upgrade-from-trial-to-commercial) section for details.
+* The application was upgraded from a trial to a commercial license, but the path to the file was not. See the [Upgrade from Trial to Commercial](slug://upgrade-tutorial#upgrade-from-trial-to-commercial) section for details.
* Static assets are not enabled on the server project, or the hosting environment does not work well with them. You need to ensure that the static assets are available after the build and on the deployment server - they are in the local NuGet cache, under a path similar to `C:\Users\\.nuget\packages\telerik.ui.for.blazor\\staticwebassets`. It is also possible that the hosting server does not support static assets or has issues with them and you may need to confirm this with the hosting provider or by testing with a simple package having a static asset to see whether it gets returned.
* [Clearing the NuGet cache](https://docs.microsoft.com/en-us/nuget/consume-packages/managing-the-global-packages-and-cache-folders#clearing-local-folders), then running a `Clean` and `Rebuild` on the solution may fix the problem in case something went wrong with fetching the NuGet package. In case `Clean` does not clean up the `bin` and `obj` folders, you can also delete them manually before `Rebuild`.
-* A problem occurs during the deployment. See the [Deployment Troubleshooting]({%slug deployment-troubleshooting%}) article for more details.
+* A problem occurs during the deployment. See the [Deployment Troubleshooting](slug://deployment-troubleshooting) article for more details.
### Defer Attribute
Sometimes, the JS Interop file is referenced correctly and returns successfully, but occasionally you get the error. This indicates a timing issue (for example, low machine performance or slow network) that causes the script to load and be parsed too late, after it is needed.
-One solution is to remove the `defer` attribute of the `
````
-> When using the `telerik-blazor.js` file from CDN and with a `defer` attribute, [start the client-side Blazor framework manually](slug://getting-started/what-you-need#javascript-file).
+> When using the `telerik-blazor.js` file from CDN and with a `defer` attribute, [start the client-side Blazor framework manually](slug:getting-started/what-you-need#javascript-file).
## Pros and Cons of Using CDN
@@ -102,19 +102,19 @@ The CDN hosts the [JavaScript (JSInterop) file of Telerik UI for Blazor](slug://
The benefits of using a CDN in Blazor apps are:
* Possible performance gains in the application loading time. Blazor apps are single page applications and browsers rely on cache by default, so this benefit is marginal and relates only to users that open the application for the first time.
-* Avoidance of [browser caching issues after component version upgrades](slug://common-kb-browser-cache-buster). The CSS and JS files change with every component version, and so do the CDN URLs. This URL change guarantees that browsers will reload the static assets.
+* Avoidance of [browser caching issues after component version upgrades](slug:common-kb-browser-cache-buster). The CSS and JS files change with every component version, and so do the CDN URLs. This URL change guarantees that browsers will reload the static assets.
The drawbacks of using a CDN are:
-* Additional [component version upgrade steps](slug://upgrade-tutorial). You must change the version number in the URL, otherwise the application can display broken UI or throw [JavaScript errors](slug://troubleshooting-js-errors).
-* A CDN is a critical external dependency for your app. Regardless of the claimed uptime, you must [implement a CDN fallback](slug://common-kb-cdn-fallback) for cases when the CDN is not accessible to your users due to geographical, networking or system issues.
+* Additional [component version upgrade steps](slug:upgrade-tutorial). You must change the version number in the URL, otherwise the application can display broken UI or throw [JavaScript errors](slug:troubleshooting-js-errors).
+* A CDN is a critical external dependency for your app. Regardless of the claimed uptime, you must [implement a CDN fallback](slug:common-kb-cdn-fallback) for cases when the CDN is not accessible to your users due to geographical, networking or system issues.
## Next Steps
-* [Implement CDN Fallback](slug://common-kb-cdn-fallback)
+* [Implement CDN Fallback](slug:common-kb-cdn-fallback)
## See also
-* [Implement CDN Fallback](slug://common-kb-cdn-fallback)
+* [Implement CDN Fallback](slug:common-kb-cdn-fallback)
diff --git a/common-features/data-binding/cloud-services.md b/common-features/data-binding/cloud-services.md
index 76a425f058..a00a8cd2ab 100644
--- a/common-features/data-binding/cloud-services.md
+++ b/common-features/data-binding/cloud-services.md
@@ -12,7 +12,7 @@ position: 30
This article suggests options for data binding the Telerik Blazor components to cloud data services. Applicable scenarios may include serverless Blazor apps, or any web apps that use cloud data. The article provides an overview of a series of posts on the [Telerik Blazor blog](https://www.telerik.com/blogs/web-blazor) and links to specific points of interest.
->tip [Telerik Blazor components are datasource-agnostic](slug://common-features-data-binding-overview#how-to-provide-data). The data-binding integrations below are not subject to technical support.
+>tip [Telerik Blazor components are datasource-agnostic](slug:common-features-data-binding-overview#how-to-provide-data). The data-binding integrations below are not subject to technical support.
This article contains the following sections, which map to blog posts from the series:
diff --git a/common-features/data-binding/descriptors.md b/common-features/data-binding/descriptors.md
index e6876ca782..d2dd439905 100644
--- a/common-features/data-binding/descriptors.md
+++ b/common-features/data-binding/descriptors.md
@@ -13,10 +13,10 @@ position: 10
This article explains how to retrieve the applied filtering, searching, sorting, and grouping criteria in Blazor components. The article applies to components that support these features. The components that offer one or all of the functionalities are:
-* Components that [expose an `OnRead` event](slug://common-features-data-binding-onread#components-with-onread-event), excluding the [ListView](slug://listview-overview), because the ListView doesn't support built-in filtering, searching, sorting, and grouping.
-* [Filter](slug://filter-overview)
-* [Gantt](slug://gantt-overview)
-* [TreeList](slug://treelist-overview)
+* Components that [expose an `OnRead` event](slug:common-features-data-binding-onread#components-with-onread-event), excluding the [ListView](slug:listview-overview), because the ListView doesn't support built-in filtering, searching, sorting, and grouping.
+* [Filter](slug:filter-overview)
+* [Gantt](slug:gantt-overview)
+* [TreeList](slug:treelist-overview)
## Get Sort, Filter, Group, and Search Descriptors
@@ -27,7 +27,7 @@ You can obtain the applied filtering, searching, sorting, and grouping criteria
### Through the OnRead Event
-Use the [`Request` property](slug://common-features-data-binding-onread#event-argument) of the [`OnRead` event argument object](slug://Telerik.Blazor.Components.ReadEventArgs):
+Use the [`Request` property](slug:common-features-data-binding-onread#event-argument) of the [`OnRead` event argument object](slug:Telerik.Blazor.Components.ReadEventArgs):
@@ -83,17 +83,17 @@ See the [complete example](#example-with-component-state) at the bottom of the a
## Filtering
-The `args.Request.Filters` and the `args....State.FilterDescriptors` are collections of [`IFilterDescriptor`](slug://Telerik.DataSource.IFilterDescriptor). To access the filtering criteria, such as the user input to filter by, cast each `IFilterDescriptor` from the respective collection:
+The `args.Request.Filters` and the `args....State.FilterDescriptors` are collections of [`IFilterDescriptor`](slug:Telerik.DataSource.IFilterDescriptor). To access the filtering criteria, such as the user input to filter by, cast each `IFilterDescriptor` from the respective collection:
-* If the component is of type input or select, such as the AutoComplete, ComboBox, DropDownList, MultiColumnComboBox, MultiSelect, cast the first `IFilterDescriptor` from the collection to [`FilterDescriptor`](slug://telerik.datasource.filterdescriptor).
-* Otherwise, cast each `IFilterDescriptor` from the `args.Request.Filters` collection, respectively from the `args....State.FilterDescriptors` collection, to [`CompositeFilterDescriptor`](slug://Telerik.DataSource.CompositeFilterDescriptor).
+* If the component is of type input or select, such as the AutoComplete, ComboBox, DropDownList, MultiColumnComboBox, MultiSelect, cast the first `IFilterDescriptor` from the collection to [`FilterDescriptor`](slug:telerik.datasource.filterdescriptor).
+* Otherwise, cast each `IFilterDescriptor` from the `args.Request.Filters` collection, respectively from the `args....State.FilterDescriptors` collection, to [`CompositeFilterDescriptor`](slug:Telerik.DataSource.CompositeFilterDescriptor).
### CompositeFilterDescriptor
The `CompositeFilterDescriptor` exposes:
-* The [`FilterDescriptors`](slug://telerik.datasource.compositefilterdescriptor#Telerik_DataSource_CompositeFilterDescriptor_FilterDescriptors) property. This property represents another collection of `IFilterDescriptor`. To access the filtering criteria, cast each `IFilterDescriptor` to a `FilterDescriptor`. When the Filter component gets groupable filtering, cast each `IFilterDescriptor` to another `CompositeFilterDescriptor`.
-* The [`LogicalOperator`](slug://telerik.datasource.compositefilterdescriptor#Telerik_DataSource_CompositeFilterDescriptor_LogicalOperator) property. This property can be either `AND` or `OR`. This property represents the logical operator applied between the instances in the `FilterDescriptors` collection.
+* The [`FilterDescriptors`](slug:telerik.datasource.compositefilterdescriptor#Telerik_DataSource_CompositeFilterDescriptor_FilterDescriptors) property. This property represents another collection of `IFilterDescriptor`. To access the filtering criteria, cast each `IFilterDescriptor` to a `FilterDescriptor`. When the Filter component gets groupable filtering, cast each `IFilterDescriptor` to another `CompositeFilterDescriptor`.
+* The [`LogicalOperator`](slug:telerik.datasource.compositefilterdescriptor#Telerik_DataSource_CompositeFilterDescriptor_LogicalOperator) property. This property can be either `AND` or `OR`. This property represents the logical operator applied between the instances in the `FilterDescriptors` collection.
When the filtering is initiated, the `CompositeFilterDescriptor` properties get different values depending on the filter mode:
@@ -112,16 +112,16 @@ The searching criteria in a Grid or TreeList are stored in an individual `IFilte
## Sorting
-The sorting criteria in a Grid, TreeList or Gantt are stored in a collection of [`SortDescriptor`](slug://telerik.datasource.sortdescriptor) objects. Each `SortDescriptor` instance gives access to:
+The sorting criteria in a Grid, TreeList or Gantt are stored in a collection of [`SortDescriptor`](slug:telerik.datasource.sortdescriptor) objects. Each `SortDescriptor` instance gives access to:
* The `Member`—The field where the user sorts.
* The `SortDirection`—The sort direction for this sort descriptor.
-When the [`SortMode`](slug://Telerik.Blazor.SortMode) is `Multiple`, you may need to consider the order of the `SortDescriptor` instances. The first applied sorting criteria take precedence over all others. If there are equal values in the first sorted items, then those items are sorted by the following sorting criteria.
+When the [`SortMode`](slug:Telerik.Blazor.SortMode) is `Multiple`, you may need to consider the order of the `SortDescriptor` instances. The first applied sorting criteria take precedence over all others. If there are equal values in the first sorted items, then those items are sorted by the following sorting criteria.
## Grouping
-Тhe grouping criteria for each group are stored in an individual collection of [`GroupDescriptor`](slug://telerik.datasource.groupdescriptor) objects. The `GroupDescriptor` class inherits the `SortDescriptor` class and gives access to the same properties as the `SortDescriptor` class.
+Тhe grouping criteria for each group are stored in an individual collection of [`GroupDescriptor`](slug:telerik.datasource.groupdescriptor) objects. The `GroupDescriptor` class inherits the `SortDescriptor` class and gives access to the same properties as the `SortDescriptor` class.
The user may group by multiple fields. The groups for subsequent fields will be nested within their parent groups. The grouping criteria from the parent group are stored in the first `GroupDescriptor` instance from the collection.
@@ -335,13 +335,13 @@ You can obtain the FilterDescriptor, SearchFilter, SortDescriptor, and GroupDesc
## See Also
-* [AutoComplete OnRead Event](slug://autocomplete-events#onread)
-* [ComboBox OnRead Event](slug://components/combobox/events#onread)
-* [DropDownList OnRead Event](slug://components/dropdownlist/events#onread)
-* [Filter Overview](slug://filter-overview)
-* [Gantt State](slug://gantt-state)
-* [Grid OnRead Event](slug://components/grid/manual-operations)
-* [Grid State](slug://grid-state)
-* [MultiColumnComboBox OnRead Event](slug://multicolumncombobox-events#onread)
-* [MultiSelect OnRead Event](slug://multiselect-events#onread)
-* [TreeList State](slug://treelist-state)
\ No newline at end of file
+* [AutoComplete OnRead Event](slug:autocomplete-events#onread)
+* [ComboBox OnRead Event](slug:components/combobox/events#onread)
+* [DropDownList OnRead Event](slug:components/dropdownlist/events#onread)
+* [Filter Overview](slug:filter-overview)
+* [Gantt State](slug:gantt-state)
+* [Grid OnRead Event](slug:components/grid/manual-operations)
+* [Grid State](slug:grid-state)
+* [MultiColumnComboBox OnRead Event](slug:multicolumncombobox-events#onread)
+* [MultiSelect OnRead Event](slug:multiselect-events#onread)
+* [TreeList State](slug:treelist-state)
\ No newline at end of file
diff --git a/common-features/data-binding/observable-data.md b/common-features/data-binding/observable-data.md
index 420a9c4e95..c8c59f2098 100644
--- a/common-features/data-binding/observable-data.md
+++ b/common-features/data-binding/observable-data.md
@@ -32,34 +32,34 @@ In this article:
The following components support observable data for their `Data` parameter. Note that observable data is not supported with manual data binding via the `OnRead` event.
-* [AutoComplete](slug://autocomplete-refresh-data)
+* [AutoComplete](slug:autocomplete-refresh-data)
-* [Carousel](slug://carousel-refresh-data)
+* [Carousel](slug:carousel-refresh-data)
-* [ComboBox](slug://combobox-refresh-data)
+* [ComboBox](slug:combobox-refresh-data)
-* [DropDownList](slug://dropdownlist-refresh-data)
+* [DropDownList](slug:dropdownlist-refresh-data)
-* [Grid documentation](slug://grid-refresh-data), [live demo](https://demos.telerik.com/blazor-ui/grid/observable-data)
+* [Grid documentation](slug:grid-refresh-data), [live demo](https://demos.telerik.com/blazor-ui/grid/observable-data)
-* [ListView](slug://listview-refresh-data)
+* [ListView](slug:listview-refresh-data)
-* [MultiSelect](slug://multiselect-refresh-data)
+* [MultiSelect](slug:multiselect-refresh-data)
-* [TreeList](slug://treelist-refresh-data)
+* [TreeList](slug:treelist-refresh-data)
-* [TreeView](slug://treeview-refresh-data)
+* [TreeView](slug:treeview-refresh-data)
You can refresh other components that do not support observable data by creating a [New collection reference](#refresh-data).
-* [Scheduler](slug://scheduler-refresh-data)
+* [Scheduler](slug:scheduler-refresh-data)
-* [Menu](slug://menu-refresh-data)
+* [Menu](slug:menu-refresh-data)
-* [Drawer](slug://drawer-refresh-data)
+* [Drawer](slug:drawer-refresh-data)
-* [ContextMenu](slug://context-menu-refresh-data)
+* [ContextMenu](slug:context-menu-refresh-data)
## See Also
diff --git a/common-features/data-binding/onread.md b/common-features/data-binding/onread.md
index 21070199f8..266de66b87 100644
--- a/common-features/data-binding/onread.md
+++ b/common-features/data-binding/onread.md
@@ -36,12 +36,12 @@ Large amounts of data require loading in chunks and on demand. This improves the
`OnRead` allows full control over the data operations. For example, it is possible to use custom sorting and filtering algorithms, if the built-in ones do not fit a given scenario. Here are just a few examples, but there are many more possible scenarios:
-* [Search by multiple data fields in ComboBox and DropDownList](slug://dropdowns-kb-search-in-multiple-fields)
-* [Search in hidden Grid columns](slug://grid-kb-search-in-hidden-fields)
-* [Debounce Grid data requests](slug://grid-kb-debounce-operations)
-* [Debounce ComboBox filter requests](slug://combo-kb-debounce-onread)
+* [Search by multiple data fields in ComboBox and DropDownList](slug:dropdowns-kb-search-in-multiple-fields)
+* [Search in hidden Grid columns](slug:grid-kb-search-in-hidden-fields)
+* [Debounce Grid data requests](slug:grid-kb-debounce-operations)
+* [Debounce ComboBox filter requests](slug:combo-kb-debounce-onread)
-`OnRead` enables [data binding to **OData** services](slug://common-kb-odata).
+`OnRead` enables [data binding to **OData** services](slug:common-kb-odata).
`OnRead` also allows the application to know the exact data items, which the user is currently seeing.
@@ -54,20 +54,20 @@ Each component name points to component-specific `OnRead` documentation and exam
| Component | Supports Paging | Supports Virtualization |
| --- | --- | --- |
-| [AutoComplete](slug://autocomplete-events#onread) | - | [AutoComplete virtualization](slug://autocomplete-virtualization) |
-| [ComboBox](slug://components/combobox/events#onread) | - | [ComboBox virtualization](slug://combobox-virtualization) |
-| [DropDownList](slug://components/dropdownlist/events#onread) | - | [DropDownList virtualization](slug://dropdownlist-virtualization) |
-| [Grid](slug://components/grid/manual-operations) | [Grid paging](slug://components/grid/features/paging) | [Grid row virtualization](slug://components/grid/virtual-scrolling) |
-| [ListView](slug://listview-manual-operations) | [ListView paging](slug://listview-paging) | - |
-| [MultiColumnComboBox](slug://multicolumncombobox-events#onread) | - | [MultiColumnComboBox virtualization](slug://multicolumncombobox-virtualization) |
-| [MultiSelect](slug://multiselect-events#onread) | - | [MultiSelect virtualization](slug://multiselect-virtualization) |
+| [AutoComplete](slug:autocomplete-events#onread) | - | [AutoComplete virtualization](slug:autocomplete-virtualization) |
+| [ComboBox](slug:components/combobox/events#onread) | - | [ComboBox virtualization](slug:combobox-virtualization) |
+| [DropDownList](slug:components/dropdownlist/events#onread) | - | [DropDownList virtualization](slug:dropdownlist-virtualization) |
+| [Grid](slug:components/grid/manual-operations) | [Grid paging](slug:components/grid/features/paging) | [Grid row virtualization](slug:components/grid/virtual-scrolling) |
+| [ListView](slug:listview-manual-operations) | [ListView paging](slug:listview-paging) | - |
+| [MultiColumnComboBox](slug:multicolumncombobox-events#onread) | - | [MultiColumnComboBox virtualization](slug:multicolumncombobox-virtualization) |
+| [MultiSelect](slug:multiselect-events#onread) | - | [MultiSelect virtualization](slug:multiselect-virtualization) |
-Components like the [**TreeList**](slug://treelist-data-binding-load-on-demand) and the [**TreeView**](slug://components/treeview/data-binding/load-on-demand) don't have an `OnRead` event. Instead, they load data on demand via `OnExpand` events.
+Components like the [**TreeList**](slug:treelist-data-binding-load-on-demand) and the [**TreeView**](slug:components/treeview/data-binding/load-on-demand) don't have an `OnRead` event. Instead, they load data on demand via `OnExpand` events.
## Event Argument
-The `OnRead` event handler receives an argument, which inherits from [`ReadEventArgs`](slug://Telerik.Blazor.Components.ReadEventArgs). The exact type depends on the component. For example, the Grid handler receives `GridReadEventArgs`. The ComboBox handler receives `ComboBoxReadEventArgs`, and so on.
+The `OnRead` event handler receives an argument, which inherits from [`ReadEventArgs`](slug:Telerik.Blazor.Components.ReadEventArgs). The exact type depends on the component. For example, the Grid handler receives `GridReadEventArgs`. The ComboBox handler receives `ComboBoxReadEventArgs`, and so on.
The following properties of the event argument object are common for all [components with an `OnRead` event](#components-with-onread-event). Other properties are discussed in component-specific articles.
@@ -75,7 +75,7 @@ The following properties of the event argument object are common for all [compon
| Property | Type | Description |
| --- | --- | --- |
-| `Request` | [`DataSourceRequest`](slug://Telerik.DataSource.DataSourceRequest) | This object carries information about the requested data items. It will reveal the page index or virtual scroll offset, the sorting and filtering state, etc. |
+| `Request` | [`DataSourceRequest`](slug:Telerik.DataSource.DataSourceRequest) | This object carries information about the requested data items. It will reveal the page index or virtual scroll offset, the sorting and filtering state, etc. |
| `Data` | `IEnumerable` | Set it to the **chunk** of data items, which the component will **render**. |
| `Total` | `int` | Set it to the **total number** of items. This value will help the component generate its **pager** or **virtual scrollbar** correctly. |
@@ -102,11 +102,11 @@ async Task GridReadHandler(GridReadEventArgs args)
## ToDataSourceResult Method
-The [`DataSourceRequest` object](slug://Telerik.DataSource.DataSourceRequest) provides information about the needed data. The question is how to retrieve this data most easily. Sometimes `OnRead` data binding is called "manual", but in most cases it doesn't have to be manual at all. The solution is **`ToDataSourceResult`**.
+The [`DataSourceRequest` object](slug:Telerik.DataSource.DataSourceRequest) provides information about the needed data. The question is how to retrieve this data most easily. Sometimes `OnRead` data binding is called "manual", but in most cases it doesn't have to be manual at all. The solution is **`ToDataSourceResult`**.
-The `ToDataSourceResult` extension method is able to extract the requested data items from `IEnumerable`, `IQueryable` and `DataTable`. The method is part of the [Telerik.DataSource.Extensions](slug://Telerik.DataSource.Extensions) namespace. It expects a `DataSourceRequest` argument.
+The `ToDataSourceResult` extension method is able to extract the requested data items from `IEnumerable`, `IQueryable` and `DataTable`. The method is part of the [Telerik.DataSource.Extensions](slug:Telerik.DataSource.Extensions) namespace. It expects a `DataSourceRequest` argument.
-`ToDataSourceResult` returns a [`DataSourceResult` object](slug://Telerik.DataSource.DataSourceResult). Its most important properties are:
+`ToDataSourceResult` returns a [`DataSourceResult` object](slug:Telerik.DataSource.DataSourceResult). Its most important properties are:
| Property | Type | Description |
| --- | --- | --- |
@@ -213,7 +213,7 @@ The components fire an `OnRead` event when the user performs an action, such as
All components with an `OnRead` event have a `Rebind` method as well. To refresh the component data programmatically, call this method. It will force the component to fire `OnRead` and receive new data.
-Also check [how to rebind and refresh a component with a `Timer`](slug://common-kb-rebind-timer).
+Also check [how to rebind and refresh a component with a `Timer`](slug:common-kb-rebind-timer).
>caption Rebind DropDownList and Grid when using OnRead
@@ -317,5 +317,5 @@ Also check [how to rebind and refresh a component with a `Timer`](slug://common-
## See Also
-* [Using the Grid with OnRead](slug://components/grid/manual-operations)
-* [Data Binding to cloud services](slug://common-features-data-binding-cloud)
+* [Using the Grid with OnRead](slug:components/grid/manual-operations)
+* [Data Binding to cloud services](slug:common-features-data-binding-cloud)
diff --git a/common-features/data-binding/overview.md b/common-features/data-binding/overview.md
index 7f4c4048b3..0296050fd5 100644
--- a/common-features/data-binding/overview.md
+++ b/common-features/data-binding/overview.md
@@ -10,7 +10,7 @@ position: 0
# Data Binding Overview
-This article describes the fundamentals of data binding the Telerik Blazor components. For the sake of clarity, also check article [Value Binding vs Data Binding](slug://get-started-value-vs-data-binding).
+This article describes the fundamentals of data binding the Telerik Blazor components. For the sake of clarity, also check article [Value Binding vs Data Binding](slug:get-started-value-vs-data-binding).
* [Data binding options](#how-to-provide-data)
* [Supported data types](#data-type)
@@ -25,7 +25,7 @@ The Telerik Blazor components are detached from the application's data layer. Th
There are two main ways to provide data to the components:
* `Data` parameter - use it to provide all the data at once.
-* [`OnRead` event](slug://common-features-data-binding-onread) - use it to load data on demand in chunks.
+* [`OnRead` event](slug:common-features-data-binding-onread) - use it to load data on demand in chunks.
Hierarchy components like the TreeList and the TreeView don't have an `OnRead` event. Instead, they load data on demand via `OnExpand` events.
@@ -95,11 +95,11 @@ Some components handle properties with specific names in a predefined way. For e
There are three ways to refresh the component data:
-* [Bind the component to Observable data](slug://common-features-observable-data). **This option applies only** if the `Data` parameter is set. The component will refresh automatically when items are **added or removed**.
-* Call the component's `Rebind()` method. UI for Blazor version **3.3.0** exposed `Rebind()` for all databound components. Until then, the method was available only for the [components that have an `OnRead` event](slug://common-features-data-binding-onread#components-with-onread-event). If the component is databound via `OnRead`, the [`Rebind()` method will fire the `OnRead` event](slug://common-features-data-binding-onread#refresh-data).
+* [Bind the component to Observable data](slug:common-features-observable-data). **This option applies only** if the `Data` parameter is set. The component will refresh automatically when items are **added or removed**.
+* Call the component's `Rebind()` method. UI for Blazor version **3.3.0** exposed `Rebind()` for all databound components. Until then, the method was available only for the [components that have an `OnRead` event](slug:common-features-data-binding-onread#components-with-onread-event). If the component is databound via `OnRead`, the [`Rebind()` method will fire the `OnRead` event](slug:common-features-data-binding-onread#refresh-data).
* Reset the `Data` parameter reference. Sometimes, you may also need to call `StateHasChanged()` - for example, if the refreshing occurs in `OnAfterRenderAsync`.
-The [example below](#example) demonstrates the second and third option. Also check [how to rebind and refresh a component with a `Timer`](slug://common-kb-rebind-timer).
+The [example below](#example) demonstrates the second and third option. Also check [how to rebind and refresh a component with a `Timer`](slug:common-kb-rebind-timer).
### Reset the Collection Reference
@@ -180,6 +180,6 @@ Thus, you will usually need to create a new reference for `Data` value in order
## Next Steps
-* [Data Binding with the OnRead event](slug://common-features-data-binding-onread)
-* [Data Binding to Observable Data](slug://common-features-observable-data)
-* [Data Binding to cloud data services](slug://common-features-data-binding-cloud)
+* [Data Binding with the OnRead event](slug:common-features-data-binding-onread)
+* [Data Binding to Observable Data](slug:common-features-observable-data)
+* [Data Binding to cloud data services](slug:common-features-data-binding-cloud)
diff --git a/common-features/data-binding/telerik-datasource-package.md b/common-features/data-binding/telerik-datasource-package.md
index abae519131..6d0e5cb3f9 100644
--- a/common-features/data-binding/telerik-datasource-package.md
+++ b/common-features/data-binding/telerik-datasource-package.md
@@ -25,7 +25,7 @@ In this article:
## Basics
-The `Telerik.DataSource` package is distributed through the [Telerik NuGet package source](slug://installation/nuget) and is available to both trial and commercial licenses. It is also available as a resource in the [offline installer](slug://installation-msi) and [resources archive](slug://installation-zip) of Telerik UI for Blazor and some other Telerik suites, such as UI for ASP.NET Core.
+The `Telerik.DataSource` package is distributed through the [Telerik NuGet package source](slug:installation/nuget) and is available to both trial and commercial licenses. It is also available as a resource in the [offline installer](slug:installation-msi) and [resources archive](slug:installation-zip) of Telerik UI for Blazor and some other Telerik suites, such as UI for ASP.NET Core.
The `Telerik.DataSource` package targets `netstandard2.1`.
@@ -37,15 +37,15 @@ If you are using an EntityFramework backend that provides an `IQueryable` collec
The following classes and extension methods are the key components to the package:
-* The `ToDataSourceResult(DataSourceRequest request)` [extension method](slug://Telerik.DataSource.Extensions.QueryableExtensions) - this method is in the `Telerik.DataSource.Extensions` namespace, and is available for `IQueryable`, `IEnumerable` and `DataTable`. It receives a `DataSourceRequest` argument and returns a `DataSourceResult` object. It also has an async version (with the standard `Async` suffix to the method name). This is the method that facilitates the data operations itself so you don't have to implement them. These methods are in the `Telerik.DataSource.Extensions` namespace.
+* The `ToDataSourceResult(DataSourceRequest request)` [extension method](slug:Telerik.DataSource.Extensions.QueryableExtensions) - this method is in the `Telerik.DataSource.Extensions` namespace, and is available for `IQueryable`, `IEnumerable` and `DataTable`. It receives a `DataSourceRequest` argument and returns a `DataSourceResult` object. It also has an async version (with the standard `Async` suffix to the method name). This is the method that facilitates the data operations itself so you don't have to implement them. These methods are in the `Telerik.DataSource.Extensions` namespace.
* The `ToDataSourceResult` method generates a LINQ expressions based on the `DataSourceRequest` and passes them to the `IQueryable.Provider`. It is up to the provider (collection) to resolve it and execute it against the database (for example, an `IQueryable` coming from an EntityFrameworkCore context will create and run an SQL query for you).
-* [`DataSourceRequest`](slug://Telerik.DataSource.DataSourceRequest) - the class that describes the request for data - what page index, page size, filters and sorts, groups and aggregates are required by the client. You can receive it from Telerik components (such as the [Blazor grid in its manual data operations mode](slug://components/grid/manual-operations)), or over the wire and deserialize it (such as for requests coming from widgets like the [UI for ASP.NET Core Grid with remote data](https://demos.telerik.com/aspnet-core/grid/remote-data-binding)). You can even create a `new` instance of the object and populate its fields according to some other business logic (like an OData query string or some other case). This object is in the `Telerik.DataSource` namespace.
+* [`DataSourceRequest`](slug:Telerik.DataSource.DataSourceRequest) - the class that describes the request for data - what page index, page size, filters and sorts, groups and aggregates are required by the client. You can receive it from Telerik components (such as the [Blazor grid in its manual data operations mode](slug:components/grid/manual-operations)), or over the wire and deserialize it (such as for requests coming from widgets like the [UI for ASP.NET Core Grid with remote data](https://demos.telerik.com/aspnet-core/grid/remote-data-binding)). You can even create a `new` instance of the object and populate its fields according to some other business logic (like an OData query string or some other case). This object is in the `Telerik.DataSource` namespace.
* When you receive such an object from a Telerik component, you can iterate over the information it provides and implement you own data source operations, you are not obliged to use the `ToDataSourceResult` method (but it helps shape the data accordingly, so you may want to examine its `DataSourceResult` from a simple run to see what it contains).
-* [`DataSourceResult`](slug://Telerik.DataSource.DataSourceResult) - the resulting data set from the operations on the data source. It will contain the current page of data, for its appropriate index, according to the designated filters, sorts, groups; and it will also contain the total number of items in the data source. It will also contain aggregate data. This is what you would normally serialize over the wire to send back to the client (or pass by reference in case of C#-only services). This object is in the `Telerik.DataSource` namespace.
+* [`DataSourceResult`](slug:Telerik.DataSource.DataSourceResult) - the resulting data set from the operations on the data source. It will contain the current page of data, for its appropriate index, according to the designated filters, sorts, groups; and it will also contain the total number of items in the data source. It will also contain aggregate data. This is what you would normally serialize over the wire to send back to the client (or pass by reference in case of C#-only services). This object is in the `Telerik.DataSource` namespace.
diff --git a/common-features/dimensions.md b/common-features/dimensions.md
index 9762d134eb..69ae34afa6 100644
--- a/common-features/dimensions.md
+++ b/common-features/dimensions.md
@@ -28,7 +28,7 @@ When setting percentage dimensions to elements with special positioning (such as
## Position
-When using positioning parameters, for example `Top` or `Left`, the component placement may be affected by CSS styles on the component's parent. If you experience issues, [inspect the rendered HTML to see what elements are present and what their CSS styles are](slug://themes-override#tools).
+When using positioning parameters, for example `Top` or `Left`, the component placement may be affected by CSS styles on the component's parent. If you experience issues, [inspect the rendered HTML to see what elements are present and what their CSS styles are](slug:themes-override#tools).
>tip You can set dimensions in percentage (such as `Width="100%"`) to make the components responsive and let them resize according to the app layout and browser viewport. A lot of components expand to 100% width by default, for example, the Grid, Form, Scheduler, Spreadsheet, all input components, and others.
@@ -95,5 +95,5 @@ The examples here showcase different units and examples of using them to set dim
## See Also
-* [Themes](slug://themes-overview)
-* [Override Theme Styles](slug://themes-override)
+* [Themes](slug:themes-overview)
+* [Override Theme Styles](slug:themes-override)
diff --git a/common-features/icons.md b/common-features/icons.md
index d89646be5e..0576f674c7 100644
--- a/common-features/icons.md
+++ b/common-features/icons.md
@@ -49,7 +49,7 @@ The Telerik Blazor components use built-in icons with the help of two NuGet pack
* `Telerik.FontIcons` - defines the `FontIcon` `enum` for easier usage of built-in **font** icons
* `Telerik.SvgIcons` - defines the `ISvgIcon` interface and the `SvgIcon` static class for built-in **SVG** icons
->tip Unlike the `Telerik.UI.for.Blazor` package, the icon packages are available on the `nuget.org` source. Keep this in mind when using [`packageSourceMapping`](slug://installation/nuget#package-source-mapping).
+>tip Unlike the `Telerik.UI.for.Blazor` package, the icon packages are available on the `nuget.org` source. Keep this in mind when using [`packageSourceMapping`](slug:installation/nuget#package-source-mapping).
### Icon Namespaces
@@ -105,8 +105,8 @@ The `TelerikFontIcon` component can show a [built-in Telerik Blazor font icon](#
| `Flip` | `IconFlip` `enum`
(`None`) | The icon's flip direction, which allows to mirror (turn over) the image horizontally, vertically, or in both directions. |
| `Icon` | `FontIcon` `enum` | Any of the [built-in Telerik Blazor font icons](#icons-list). This parameter takes precedence over `IconClass`, if both are set. |
| `IconClass` | `string` | Custom CSS class for a custom third-party icon. Do not use together with the `Icon` parameter. |
-| `Size` | `string`
(`"md"`) | Any of the predefined icon sizes (from `"xs"` to `"xxxl"`). It is possible to set the parameter value to raw strings such as `"lg"`, `"md"`, or `"sm"`. However, the recommended practice is to use the properties of the static [`ThemeConstants.FontIcon.Size` class](slug://telerik.blazor.themeconstants.fonticon.size). |
-| `ThemeColor` | `string` | Any of the predefined icon colors. Use the static [`ThemeConstants.FontIcon.ThemeColor` class](slug://telerik.blazor.themeconstants.fonticon.themecolor) properties. By default, the icon color will inherit the current CSS text color. |
+| `Size` | `string`
(`"md"`) | Any of the predefined icon sizes (from `"xs"` to `"xxxl"`). It is possible to set the parameter value to raw strings such as `"lg"`, `"md"`, or `"sm"`. However, the recommended practice is to use the properties of the static [`ThemeConstants.FontIcon.Size` class](slug:telerik.blazor.themeconstants.fonticon.size). |
+| `ThemeColor` | `string` | Any of the predefined icon colors. Use the static [`ThemeConstants.FontIcon.ThemeColor` class](slug:telerik.blazor.themeconstants.fonticon.themecolor) properties. By default, the icon color will inherit the current CSS text color. |
>caption Using TelerikFontIcon
@@ -172,7 +172,7 @@ Our font icons are designed on a 16px grid base. For better display quality, use
### Render Font Icons with HTML
-Telerik UI for Blazor shares the same [themes](slug://themes-overview) with several other Telerik and Kendo UI web component suites. All these products use the same font icons.
+Telerik UI for Blazor shares the same [themes](slug:themes-overview) with several other Telerik and Kendo UI web component suites. All these products use the same font icons.
You can use the built-in font icons directly with HTML tags, without the `` component. Such direct HTML usage may provide more flexibility, but if you don't really need it, we recommend using `FontIcon` objects and the `` component instead.
@@ -200,9 +200,9 @@ The `TelerikSvgIcon` component can show a [built-in Telerik Blazor SVG icon](#ic
|---|---|---|
| `Flip` | `IconFlip` `enum`
(`None`) | The icon's flip direction, which allows to mirror (turn over) the image horizontally, vertically, or in both directions. |
| `Icon` | `ISvgIcon` | Assign a property of the `SvgIcon` static class to use any of the [built-in Telerik Blazor font icons](#icons-list). Alternatively, [implement your own custom SVG Icon class](#use-custom-svg-icon-collection). |
-| `Size` | `string`
(`"md"`) | Any of the predefined icon sizes (from `"xs"` to `"xxxl"`). It is possible to set the parameter value to raw strings such as `"lg"`, `"md"`, or `"sm"`. However, the recommended practice is to use the properties of the static [`ThemeConstants.SvgIcon.Size` class](slug://telerik.blazor.themeconstants.svgicon.size). |
+| `Size` | `string`
(`"md"`) | Any of the predefined icon sizes (from `"xs"` to `"xxxl"`). It is possible to set the parameter value to raw strings such as `"lg"`, `"md"`, or `"sm"`. However, the recommended practice is to use the properties of the static [`ThemeConstants.SvgIcon.Size` class](slug:telerik.blazor.themeconstants.svgicon.size). |
| `ChildContent` | `RenderFragment` | The HTML markup of a custom SVG icon. Do not use together with `Icon`. |
-| `ThemeColor` | `string` | Any of the predefined icon colors. Use the static [`ThemeConstants.SvgIcon.ThemeColor` class](slug://telerik.blazor.themeconstants.svgicon.themecolor) properties. |
+| `ThemeColor` | `string` | Any of the predefined icon colors. Use the static [`ThemeConstants.SvgIcon.ThemeColor` class](slug:telerik.blazor.themeconstants.svgicon.themecolor) properties. |
>caption Using TelerikSvgIcon
@@ -293,8 +293,8 @@ The `ISvgIcon` interface members are:
It is possible to configure the icon type for the whole application:
-1. Locate the [``](slug://rootcomponent-overview) tag in the Blazor app. Normally, it's in a layout file such as `MainLayout.razor` or `TelerikLayout.razor`.
-2. Set the RootComponent `IconType` parameter to an [`IconType` enum](slug://telerik.blazor.icontype) value (`Svg` or `Font`). The default icon type is `Svg`.
+1. Locate the [``](slug:rootcomponent-overview) tag in the Blazor app. Normally, it's in a layout file such as `MainLayout.razor` or `TelerikLayout.razor`.
+2. Set the RootComponent `IconType` parameter to an [`IconType` enum](slug:telerik.blazor.icontype) value (`Svg` or `Font`). The default icon type is `Svg`.
>caption Define global icon type via TelerikRootComponent
@@ -334,7 +334,7 @@ Telerik UI for Blazor supports using custom (third-party) icons:
* [In the `SvgIcon` component](#use-custom-svg-icon-collection).
* [In the `FontIcon` component](#fonticon-component).
-* In [Buttons](slug://button-icons), [Menu items](slug://menu-icons), [Drawer items](slug://drawer-icons) and other [navigation components](slug://blazor-overview#list-of-components).
+* In [Buttons](slug:button-icons), [Menu items](slug:menu-icons), [Drawer items](slug:drawer-icons) and other [navigation components](slug:blazor-overview#list-of-components).
[Using custom icons for the automatically rendered icons is not supported yet](https://feedback.telerik.com/blazor/1641361-ability-to-change-the-built-in-icons). For example, the sort and filter icons in the Grid header cells, or the open arrow in the DropDownList.
@@ -343,4 +343,4 @@ Telerik UI for Blazor supports using custom (third-party) icons:
* Built-in Icon List
* [Blazor Live Demos](https://demos.telerik.com/blazor-ui)
-* [CSS Themes](slug://themes-overview)
+* [CSS Themes](slug:themes-overview)
diff --git a/common-features/input-adornments.md b/common-features/input-adornments.md
index f3487388f3..f812cb07e5 100644
--- a/common-features/input-adornments.md
+++ b/common-features/input-adornments.md
@@ -29,14 +29,14 @@ A prefix input adornment refers to an element placed before the user input field
The following input components support prefix and suffix adornments:
-* [AutoComplete](slug://autocomplete-overview)
-* [ComboBox](slug://components/combobox/overview)
-* [MaskedTextbox](slug://maskedtextbox-overview)
-* [MultiColumnComboBox](slug://multicolumncombobox-overview)
-* [MultiSelect](slug://multiselect-overview)
-* [NumericTextBox](slug://components/numerictextbox/overview)
-* [TextArea](slug://textarea-overview)
-* [TextBox](slug://components/textbox/overview)
+* [AutoComplete](slug:autocomplete-overview)
+* [ComboBox](slug:components/combobox/overview)
+* [MaskedTextbox](slug:maskedtextbox-overview)
+* [MultiColumnComboBox](slug:multicolumncombobox-overview)
+* [MultiSelect](slug:multiselect-overview)
+* [NumericTextBox](slug:components/numerictextbox/overview)
+* [TextArea](slug:textarea-overview)
+* [TextBox](slug:components/textbox/overview)
## Adding a Prefix Adornment
@@ -357,10 +357,10 @@ In addition to the common configuration settings listed in this article, the Tex
This section applies to the components that incorporate popup element:
-* [AutoComplete](slug://autocomplete-overview)
-* [ComboBox](slug://components/combobox/overview)
-* [MultiColumnComboBox](slug://multicolumncombobox-overview)
-* [MultiSelect](slug://multiselect-overview)
+* [AutoComplete](slug:autocomplete-overview)
+* [ComboBox](slug:components/combobox/overview)
+* [MultiColumnComboBox](slug:multicolumncombobox-overview)
+* [MultiSelect](slug:multiselect-overview)
By design, `Alt` + `Down` key combination opens the popup element when the component is focused. If you have added another dropdown component as a prefix or suffix adornment, focusing that component and pressing `Alt` + `Down` keys will open both popup elements - the one that belongs to the main component and the other associated with the dropdown in the prefix/suffix template.
diff --git a/common-features/input-validation.md b/common-features/input-validation.md
index 8f18bc7811..f92eb67350 100644
--- a/common-features/input-validation.md
+++ b/common-features/input-validation.md
@@ -40,7 +40,7 @@ This article provides examples of validating the Telerik Blazor components. The
* [Sliders](#sliders)
->tip Telerik offers the [Form Component](slug://form-overview) that lets you generate and manage forms with predefined layouts and less code.
+>tip Telerik offers the [Form Component](slug:form-overview) that lets you generate and manage forms with predefined layouts and less code.
### Simple Inputs
@@ -514,11 +514,11 @@ Unlike other components, the editor does not trigger form validation on every ke
### MaskedTextbox
-The Masked Textbox prompts the user for their input and restricts it according to its [Mask](slug://maskedtextbox-mask-prompt).
+The Masked Textbox prompts the user for their input and restricts it according to its [Mask](slug:maskedtextbox-mask-prompt).
The Blazor validation is, however, controlled by data annotation attributes on the model and so the application must have the appropriate rules set that match the desired input and masks. The RegularExpression annotation is commonly used to require a specific input format and values, or you can implement custom data annotation attributes too.
-You may want to set the [`IncludeLiterals`](slug://maskedtextbox-mask-prompt#include-literals-in-the-value) parameter to `true` and/or set the [`PromptPlaceholder`](slug://maskedtextbox-mask-prompt#prompt) parameter accordingly to keep the prompt characters in the `Value` so you can validate the content more easily.
+You may want to set the [`IncludeLiterals`](slug:maskedtextbox-mask-prompt#include-literals-in-the-value) parameter to `true` and/or set the [`PromptPlaceholder`](slug:maskedtextbox-mask-prompt#prompt) parameter accordingly to keep the prompt characters in the `Value` so you can validate the content more easily.
>caption Sample DataAnnotation rules that match masks to validate user input
@@ -920,8 +920,8 @@ The feature is supported by the following components treated as simple textbox-l
## See Also
* [Data annotation attributes](https://docs.microsoft.com/en-us/aspnet/core/mvc/models/validation)
-* [Conditional validation](slug://form-kb-conditional-validation)
-* [ValueChanged and validation](slug://value-changed-validation-model)
-* [Validate on blur or change](slug://textbox-validate-on-change)
-* [Error: Requires a value for ValueExpression](slug://common-kb-requires-valueexpression)
-* [Form component](slug://form-overview)
+* [Conditional validation](slug:form-kb-conditional-validation)
+* [ValueChanged and validation](slug:value-changed-validation-model)
+* [Validate on blur or change](slug:textbox-validate-on-change)
+* [Error: Requires a value for ValueExpression](slug:common-kb-requires-valueexpression)
+* [Form component](slug:form-overview)
diff --git a/common-features/loading-sign.md b/common-features/loading-sign.md
index e4d64f138c..fbc708fcdb 100644
--- a/common-features/loading-sign.md
+++ b/common-features/loading-sign.md
@@ -12,7 +12,7 @@ position: 5
Many times a component loads or saves data and that can take some time. To show your users the app is working, and to prevent them from performing the same action multiple times, the Telerik Blazor components can show a busy indicator while such an operation is under way.
-The Telerik components use the Telerik [Loader](slug://loader-overview) and [LoaderContainer](slug://loadercontainer-overview) components internally to match the theme and design.
+The Telerik components use the Telerik [Loader](slug:loader-overview) and [LoaderContainer](slug:loadercontainer-overview) components internally to match the theme and design.
There are three patterns for showing a loading indicator:
@@ -342,7 +342,7 @@ Another example could be a slow calculation (for example, grouping a large amoun
A fourth example could be a dropdown that has far too many items in it - expanding the dropdown will take some time to render because the DOM operation itself takes time. This would affect server-side Blazor apps too.
-To combat such performance issues, see the [Slow Performance](slug://troubleshooting-general-issues#slow-performance) section of the documentation.
+To combat such performance issues, see the [Slow Performance](slug:troubleshooting-general-issues#slow-performance) section of the documentation.
Truly asynchronous operations will still allow for a loading sign - such as the grid's `OnRead` event that is really `async` (for example, calls some WebAPI) will let the framework release the UI thread and re-render the component with a loading sign until the data response comes back.
diff --git a/components/aiprompt/accessibility/wai-aria-support.md b/components/aiprompt/accessibility/wai-aria-support.md
index 011a51c0af..986efb8bb5 100644
--- a/components/aiprompt/accessibility/wai-aria-support.md
+++ b/components/aiprompt/accessibility/wai-aria-support.md
@@ -88,9 +88,9 @@ The AI Prompt has been tested with the following screen readers and browsers com
## Keyboard Navigation
-For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview](slug://accessibility-overview#keyboard-navigation) article.
+For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview](slug:accessibility-overview#keyboard-navigation) article.
## See Also
* [Blazor AIPrompt Demos](https://demos.telerik.com/blazor-ui/aiprompt/overview)
-* [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
\ No newline at end of file
+* [Accessibility in Telerik UI for Blazor](slug:accessibility-overview)
\ No newline at end of file
diff --git a/components/aiprompt/events.md b/components/aiprompt/events.md
index 4bdd942a95..9105e4c80e 100644
--- a/components/aiprompt/events.md
+++ b/components/aiprompt/events.md
@@ -21,7 +21,7 @@ This article explains the events available in the Telerik AIPrompt for Blazor:
The `OnPromptRequest` event fires when the user clicks on the **Generate** button within the Prompt view or retries a prompt from the Output view.
-The event handler receives an argument of type [`AIPromptPromptRequestEventArgs`](slug://Telerik.Blazor.Components.AIPromptPromptRequestEventArgs). See the [example below](#example).
+The event handler receives an argument of type [`AIPromptPromptRequestEventArgs`](slug:Telerik.Blazor.Components.AIPromptPromptRequestEventArgs). See the [example below](#example).
@[template](/_contentTemplates/common/parameters-table-styles.md#table-layout)
@@ -30,14 +30,14 @@ The event handler receives an argument of type [`AIPromptPromptRequestEventArgs`
| `Prompt` | `string` | The prompt text of the request. |
| `Output` | `string` | The output of the request. The output is based on the prompt text. |
| `IsCancelled` | `bool` | Whether the event is cancelled and the built-in action is prevented. |
-| `OutputItem` | `AIPromptOutputItemDescriptor` | The output item. This property will be populated only when the user retries an existing output. See [`AIPromptOutputItemDescriptor`](slug://Telerik.Blazor.Components.AIPromptOutputItemDescriptor). |
+| `OutputItem` | `AIPromptOutputItemDescriptor` | The output item. This property will be populated only when the user retries an existing output. See [`AIPromptOutputItemDescriptor`](slug:Telerik.Blazor.Components.AIPromptOutputItemDescriptor). |
## OnCommandExecute
The `OnCommandExecute` event fires when the user clicks on a command within the Commands view.
-The event handler receives an argument of type [`AIPromptCommandExecuteEventArgs`](slug://Telerik.Blazor.Components.AIPromptCommandExecuteEventArgs). See the [example below](#example).
+The event handler receives an argument of type [`AIPromptCommandExecuteEventArgs`](slug:Telerik.Blazor.Components.AIPromptCommandExecuteEventArgs). See the [example below](#example).
@[template](/_contentTemplates/common/parameters-table-styles.md#table-layout)
@@ -46,20 +46,20 @@ The event handler receives an argument of type [`AIPromptCommandExecuteEventArgs
| `Command` | `AIPromptCommandDescriptor` | The executed command. |
| `Output` | `string` | The output based on the executed command. |
| `IsCancelled` | `bool` | Whether the event is cancelled and the built-in action is prevented. |
-| `OutputItem` | `AIPromptOutputItemDescriptor` | The output item. This property will be populated only when the user retries an existing output. See [`AIPromptOutputItemDescriptor`](slug://Telerik.Blazor.Components.AIPromptOutputItemDescriptor). |
+| `OutputItem` | `AIPromptOutputItemDescriptor` | The output item. This property will be populated only when the user retries an existing output. See [`AIPromptOutputItemDescriptor`](slug:Telerik.Blazor.Components.AIPromptOutputItemDescriptor). |
## OnOutputRate
The `OnOutputRate` event fires when the user rates an output.
-The event handler receives an argument of type [`AIPromptOutputRateEventArgs`](slug://Telerik.Blazor.Components.AIPromptOutputRateEventArgs). See the [example below](#example).
+The event handler receives an argument of type [`AIPromptOutputRateEventArgs`](slug:Telerik.Blazor.Components.AIPromptOutputRateEventArgs). See the [example below](#example).
@[template](/_contentTemplates/common/parameters-table-styles.md#table-layout)
| Property | Type | Description |
| --- | --- | --- |
-| `OutputItem` | `AIPromptOutputItemDescriptor` | Specifies the output item that is being rated. See [`AIPromptOutputItemDescriptor`](slug://Telerik.Blazor.Components.AIPromptOutputItemDescriptor). |
+| `OutputItem` | `AIPromptOutputItemDescriptor` | Specifies the output item that is being rated. See [`AIPromptOutputItemDescriptor`](slug:Telerik.Blazor.Components.AIPromptOutputItemDescriptor). |
## PromptTextChanged
diff --git a/components/aiprompt/overview.md b/components/aiprompt/overview.md
index 6e56be74a5..5cfbc9ccf0 100644
--- a/components/aiprompt/overview.md
+++ b/components/aiprompt/overview.md
@@ -63,31 +63,31 @@ The component allows you to interact with the output from the AI and execute a s
## Integration with Microsoft.Extensions.AI
-The AIPrompt supports using the [Microsoft.Extensions.AI library](https://learn.microsoft.com/en-us/dotnet/api/microsoft.extensions.ai?view=net-9.0-pp) to provide seamless integration with various AI models and boost your workflow when connecting the AIPrompt with AI models. [Learn how to integrate Microsoft.Extensions.AI with your AIPrompt component...](slug://common-features-microsoft-extensions-ai-integration)
+The AIPrompt supports using the [Microsoft.Extensions.AI library](https://learn.microsoft.com/en-us/dotnet/api/microsoft.extensions.ai?view=net-9.0-pp) to provide seamless integration with various AI models and boost your workflow when connecting the AIPrompt with AI models. [Learn how to integrate Microsoft.Extensions.AI with your AIPrompt component...](slug:common-features-microsoft-extensions-ai-integration)
## ToolBar
-The AIPrompt includes a toolbar with built-in buttons that activate the view they are related to. The component also exposes the option to add custom tools, which may be associated with arbitrary handlers. [Read more about the AIPrompt's ToolBar...](slug://aiprompt-toolbar)
+The AIPrompt includes a toolbar with built-in buttons that activate the view they are related to. The component also exposes the option to add custom tools, which may be associated with arbitrary handlers. [Read more about the AIPrompt's ToolBar...](slug:aiprompt-toolbar)
## Views
-The AIPrompt component offers the Prompt, Output, and Commands views that relate to the current state of the prompt-response lifecycle. You can also customize the component through custom views. [Read more about the AIPrompt views...](slug://aiprompt-views-overview)
+The AIPrompt component offers the Prompt, Output, and Commands views that relate to the current state of the prompt-response lifecycle. You can also customize the component through custom views. [Read more about the AIPrompt views...](slug:aiprompt-views-overview)
## Templates
-The AIPrompt component provides templates that enable developers to customize the rendering and appearance of the component. [Read more about the AIPrompt templates...](slug://aiprompt-templates)
+The AIPrompt component provides templates that enable developers to customize the rendering and appearance of the component. [Read more about the AIPrompt templates...](slug:aiprompt-templates)
## Events
-The various AIPrompt events allow you to implement custom functionality and handle user interactions with the component's ToolBar. [Read more about the AIPrompt events...](slug://aiprompt-events)
+The various AIPrompt events allow you to implement custom functionality and handle user interactions with the component's ToolBar. [Read more about the AIPrompt events...](slug:aiprompt-events)
## AIPrompt Parameters
-The table below lists the AIPrompt parameters. For a full list of the AIPrompt API members (parameters, methods, and events), check the [AIPrompt API Reference](slug://Telerik.Blazor.Components.TelerikAIPrompt).
+The table below lists the AIPrompt parameters. For a full list of the AIPrompt API members (parameters, methods, and events), check the [AIPrompt API Reference](slug:Telerik.Blazor.Components.TelerikAIPrompt).
@[template](/_contentTemplates/common/parameters-table-styles.md#table-layout)
@@ -95,16 +95,16 @@ The table below lists the AIPrompt parameters. For a full list of the AIPrompt A
| --- | --- | --- |
| `AIPromptViews` | `RenderFragment` | Allows control over the views of the content. Use it to set the visibility of a predefined view or to create custom views. If a render fragment is not provided, the AIPrompt will display its default views. |
| `AIPromptToolBar` | `RenderFragment` | Any additional buttons that will be rendered within the ToolBar. This parameter will append the new items, rather than override buttons related to existing views. |
-| `Class` | `string` | The `class` attribute of the `` element. Use it to apply custom styles or [override the theme](slug://themes-override). |
+| `Class` | `string` | The `class` attribute of the `
` element. Use it to apply custom styles or [override the theme](slug:themes-override). |
| `Commands` | `List
` | The predefined commands displayed within the Commands view. |
-| `Height` | `string` | The `height` style of the component in any [supported CSS unit](slug://common-features/dimensions). The default AIPrompt dimensions depend on the CSS theme. |
+| `Height` | `string` | The `height` style of the component in any [supported CSS unit](slug:common-features/dimensions). The default AIPrompt dimensions depend on the CSS theme. |
| `PromptText` | `string` | The value of the text within the prompt view. Use it when you need to add some form of transformation to the prompt. The parameter supports two-way binding. |
| `PromptTextChanged` | `EventCallback` | The handler called whenever the `PromptText` changes. |
| `PromptSuggestions` | `List` | The prompt suggestions displayed within the Prompt view. |
| `PromptSuggestionItemTemplate` | `RenderFragment` | The Prompt Suggestion Item template of the AIPrompt. |
| `ShowOutputRating` | `bool`
(`false`) | Controls the visibility of the rating buttons within the output card. |
| `SystemPrompt` | `string`
(See "Description" column) | Defines the system prompt that is passed to the [`IChatClient.CompleteAsync`](https://learn.microsoft.com/en-us/dotnet/api/microsoft.extensions.ai.ichatclient.completeasync?view=net-9.0-pp), when such is used. The default value is: `"You are a helpful assistant designed to assist users. Your goal is to provide helpful, accurate, and contextually appropriate information in a clear and concise manner. Avoid discussing harmful, illegal, or inappropriate topics"`.
-| `Width` | `string` | The `width` style of the component in any [supported CSS unit](slug://common-features/dimensions). The default AIPrompt dimensions depend on the CSS theme. |
+| `Width` | `string` | The `width` style of the component in any [supported CSS unit](slug:common-features/dimensions). The default AIPrompt dimensions depend on the CSS theme. |
## AIPrompt Reference and Methods
@@ -151,14 +151,14 @@ The AIPrompt exposes methods for programmatic operation. To use them, define a r
## Next Steps
-* [Configure the AIPrompt ToolBar](slug://aiprompt-toolbar)
-* [Customize the AIPrompt Views](slug://aiprompt-views-overview)
-* [Make the AIPrompt Your Own through Custom Commands](slug://aiprompt-views-commands)
-* [Implement AIPrompt Views Templates](slug://aiprompt-views-templates)
-* [Implement AIPrompt Templates](slug://aiprompt-templates)
-* [Handle the AIPrompt Events](slug://aiprompt-events)
+* [Configure the AIPrompt ToolBar](slug:aiprompt-toolbar)
+* [Customize the AIPrompt Views](slug:aiprompt-views-overview)
+* [Make the AIPrompt Your Own through Custom Commands](slug:aiprompt-views-commands)
+* [Implement AIPrompt Views Templates](slug:aiprompt-views-templates)
+* [Implement AIPrompt Templates](slug:aiprompt-templates)
+* [Handle the AIPrompt Events](slug:aiprompt-events)
## See Also
* [Live Demo: AIPrompt](https://demos.telerik.com/blazor-ui/aiprompt/overview)
-* [AIPrompt API Reference](slug://Telerik.Blazor.Components.TelerikAIPrompt)
+* [AIPrompt API Reference](slug:Telerik.Blazor.Components.TelerikAIPrompt)
diff --git a/components/aiprompt/templates.md b/components/aiprompt/templates.md
index 03c84794d4..79b274e14b 100644
--- a/components/aiprompt/templates.md
+++ b/components/aiprompt/templates.md
@@ -12,11 +12,11 @@ position: 30
The AIPrompt component provides the `PromptSuggestionItemTemplate` that allows you to change the appearance of the prompt suggestions made by the component.
->tip The AIPrompt component also implements [View templates](slug://aiprompt-templates) that control the rendering of the Prompt, Output, and Command views.
+>tip The AIPrompt component also implements [View templates](slug:aiprompt-templates) that control the rendering of the Prompt, Output, and Command views.
The Prompt view of the AIPrompt renders any suggestions passed to the `PromptSuggestions` parameter in the form of elevated bubbles within a collapsible section. The `PromptSuggestionItemTemplate` allows you to control the rendering of individual suggestions.
->note By default, clicking on a suggestion will populate the prompt's input with the suggestion's value and also trigger a `PromptTextChanged` event. If you use the `PromptSuggestionItemTemplate`, you should also handle [any event](slug://aiprompt-events) you deem necessary (such as `onclick`).
+>note By default, clicking on a suggestion will populate the prompt's input with the suggestion's value and also trigger a `PromptTextChanged` event. If you use the `PromptSuggestionItemTemplate`, you should also handle [any event](slug:aiprompt-events) you deem necessary (such as `onclick`).
>caption Using the `PromptSuggestionItemTemplate` to alter the appearance of the suggestions
@@ -71,4 +71,4 @@ The Prompt view of the AIPrompt renders any suggestions passed to the `PromptSug
## See Also
-* [Views Templates](slug://aiprompt-views-templates)
+* [Views Templates](slug:aiprompt-views-templates)
diff --git a/components/aiprompt/toolbar.md b/components/aiprompt/toolbar.md
index d7bd1ab3d7..69a9ffb984 100644
--- a/components/aiprompt/toolbar.md
+++ b/components/aiprompt/toolbar.md
@@ -34,7 +34,7 @@ The `AIPromptToolBarButton` tag exposes parameters that allow you to customize t
| Parameter | Type and Default Value | Description |
| ----------- | ----------- | ----------- |
| `Class` | `string` | The CSS class that will be rendered on the main wrapping element of the AIPromptToolBarButton. You could use that class to cascade styles. |
-| `Icon` | `object` | Adds a font icon to the button. You can find more information on adding a font icon to a Telerik Component in [Telerik Font and Svg Icons article](slug://common-features-icons#icon-namespaces). |
+| `Icon` | `object` | Adds a font icon to the button. You can find more information on adding a font icon to a Telerik Component in [Telerik Font and Svg Icons article](slug:common-features-icons#icon-namespaces). |
| `OnClick` | `EventCallback` | The onclick event handler. |
| `ChildContent` | `RenderFragment` | The child content rendered within the button. |
@@ -88,11 +88,11 @@ The example below omits any event handlers for brevity. Custom buttons are to be
## Next Steps
-* [Customize the AIPrompt Views](slug://aiprompt-views-overview)
-* [Implement AIPrompt Templates](slug://aiprompt-templates)
-* [Handle AIPrompt Events](slug://aiprompt-events)
+* [Customize the AIPrompt Views](slug:aiprompt-views-overview)
+* [Implement AIPrompt Templates](slug:aiprompt-templates)
+* [Handle AIPrompt Events](slug:aiprompt-events)
## See Also
-* [Views Templates](slug://aiprompt-views-templates)
+* [Views Templates](slug:aiprompt-views-templates)
* [Live Demo: AIPrompt Overview](https://demos.telerik.com/blazor-ui/aiprompt/overview)
\ No newline at end of file
diff --git a/components/aiprompt/views/commands.md b/components/aiprompt/views/commands.md
index 9d126ba7c9..f7719351e2 100644
--- a/components/aiprompt/views/commands.md
+++ b/components/aiprompt/views/commands.md
@@ -24,7 +24,7 @@ The following properties enable you to customize each command:
| ----------- | ----------- | ----------- |
| `Id` | `string` | The `Id` of the command. |
| `Title` | `string` | The title of the command. Rendered as text within the Command view. |
-| `Icon` | `object` | The [Telerik Font or SVG icon](slug://common-features-icons) rendered before the title within the Command view. |
+| `Icon` | `object` | The [Telerik Font or SVG icon](slug:common-features-icons) rendered before the title within the Command view. |
| `Children` | `List` | The nested commands (if any) of the command. |
>caption Using the `Commands` parameter to pass a collection of predefined commands to the AIPrompt for Blazor
@@ -86,7 +86,7 @@ The following properties enable you to customize each command:
## See Also
* [Live Demo: AIPrompt](https://demos.telerik.com/blazor-ui/aiprompt/overview)
- * [Views Overview](slug://aiprompt-views-overview)
- * [Prompt View](slug://aiprompt-views-prompt)
- * [Output View](slug://aiprompt-views-output)
- * [Views Templates](slug://aiprompt-views-templates)
\ No newline at end of file
+ * [Views Overview](slug:aiprompt-views-overview)
+ * [Prompt View](slug:aiprompt-views-prompt)
+ * [Output View](slug:aiprompt-views-output)
+ * [Views Templates](slug:aiprompt-views-templates)
\ No newline at end of file
diff --git a/components/aiprompt/views/output.md b/components/aiprompt/views/output.md
index e738fa8a39..6c9740903b 100644
--- a/components/aiprompt/views/output.md
+++ b/components/aiprompt/views/output.md
@@ -12,7 +12,7 @@ position: 20
The Output view shows the responses generated by the underlying AI service. Each response renders in its dedicated output card and provides two options to the user—to copy the content of the response or to retry the request. The Output view is activated through interaction—once the user fills out a prompt within the Prompt view and requests a response, the Output view will become active.
-If the `ShowOutputRating` is enabled on the component level, the output card will also feature two additional options-to upvote or downvote the response. To handle this interaction, you can use the `OnOutputRate` event. For more information on how to handle the event, refer to the [AIPrompt events](slug://aiprompt-events) article.
+If the `ShowOutputRating` is enabled on the component level, the output card will also feature two additional options-to upvote or downvote the response. To handle this interaction, you can use the `OnOutputRate` event. For more information on how to handle the event, refer to the [AIPrompt events](slug:aiprompt-events) article.
By default, the Output view is rendered and is part of the predefined views. However, if you provide a render fragment of type `AIPromptViews` to the `TelerikAIPrompt` tag, you override the default rendering, meaning you must explicitly add `AIPromptOutputView` tag within it.
@@ -54,7 +54,7 @@ By default, the Output view is rendered and is part of the predefined views. How
## See Also
* [Live Demo: AIPrompt](https://demos.telerik.com/blazor-ui/aiprompt/overview)
- * [Views Overview](slug://aiprompt-views-overview)
- * [Prompt View](slug://aiprompt-views-prompt)
- * [Commands View](slug://aiprompt-views-commands)
- * [Views Templates](slug://aiprompt-views-templates)
\ No newline at end of file
+ * [Views Overview](slug:aiprompt-views-overview)
+ * [Prompt View](slug:aiprompt-views-prompt)
+ * [Commands View](slug:aiprompt-views-commands)
+ * [Views Templates](slug:aiprompt-views-templates)
\ No newline at end of file
diff --git a/components/aiprompt/views/overview.md b/components/aiprompt/views/overview.md
index a5a91b41eb..c2cd597eb2 100644
--- a/components/aiprompt/views/overview.md
+++ b/components/aiprompt/views/overview.md
@@ -14,9 +14,9 @@ The AIPrompt component provides three predefined views and also lets you create
The available built-in views are:
-* [Prompt View](slug://aiprompt-views-prompt)
-* [Output View](slug://aiprompt-views-output)
-* [Commands View](slug://aiprompt-views-commands)
+* [Prompt View](slug:aiprompt-views-prompt)
+* [Output View](slug:aiprompt-views-output)
+* [Commands View](slug:aiprompt-views-commands)
## Parameters
@@ -27,9 +27,9 @@ The AIPrompt views provide various parameters that allow you to configure the co
| Parameter | Type | Description |
| --- | --- | --- |
| `ButtonText` | `string` | The text rendered within the toolbar button associated with the view. |
-| `ButtonIcon` | `object` | The [Telerik Font or SVG icon](slug://common-features-icons) rendered within the toolbar button associated with the view. |
-| `ViewTemplate` | `RenderFragment` | The template controlling the rendering of the view's content. Read more in the [Templates](slug://aiprompt-views-templates#view-template) article. |
-| `FooterTemplate` | `RenderFragment` | The template controlling the rendering of the view's footer. Read more in the [Templates](slug://aiprompt-views-templates#footer-template) article. |
+| `ButtonIcon` | `object` | The [Telerik Font or SVG icon](slug:common-features-icons) rendered within the toolbar button associated with the view. |
+| `ViewTemplate` | `RenderFragment` | The template controlling the rendering of the view's content. Read more in the [Templates](slug:aiprompt-views-templates#view-template) article. |
+| `FooterTemplate` | `RenderFragment` | The template controlling the rendering of the view's footer. Read more in the [Templates](slug:aiprompt-views-templates#footer-template) article. |
By default, the AIPrompt will always render both the Prompt and the Output view. The Commands view will be rendered only if you pass a custom set of commands through the `Commands` parameter:
@@ -74,8 +74,8 @@ By default, the AIPrompt will always render both the Prompt and the Output view.
## See Also
* [Live Demo: AIPrompt](https://demos.telerik.com/blazor-ui/aiprompt/overview)
- * [Prompt View](slug://aiprompt-views-prompt)
- * [Output View](slug://aiprompt-views-output)
- * [Commands View](slug://aiprompt-views-commands)
- * [Views Templates](slug://aiprompt-views-templates)
+ * [Prompt View](slug:aiprompt-views-prompt)
+ * [Output View](slug:aiprompt-views-output)
+ * [Commands View](slug:aiprompt-views-commands)
+ * [Views Templates](slug:aiprompt-views-templates)
diff --git a/components/aiprompt/views/prompt.md b/components/aiprompt/views/prompt.md
index 7bae5d5b7c..8e6c9673f6 100644
--- a/components/aiprompt/views/prompt.md
+++ b/components/aiprompt/views/prompt.md
@@ -38,7 +38,7 @@ Additionally, the Prompt view can display prompt suggestions related to the prom
## See Also
* [Live Demo: AIPrompt](https://demos.telerik.com/blazor-ui/aiprompt/overview)
- * [Views Overview](slug://aiprompt-views-overview)
- * [Prompt View](slug://aiprompt-views-prompt)
- * [Output View](slug://aiprompt-views-output)
- * [Views Templates](slug://aiprompt-views-templates)
\ No newline at end of file
+ * [Views Overview](slug:aiprompt-views-overview)
+ * [Prompt View](slug:aiprompt-views-prompt)
+ * [Output View](slug:aiprompt-views-output)
+ * [Views Templates](slug:aiprompt-views-templates)
\ No newline at end of file
diff --git a/components/aiprompt/views/templates.md b/components/aiprompt/views/templates.md
index 32523a7c04..efc4db98d7 100644
--- a/components/aiprompt/views/templates.md
+++ b/components/aiprompt/views/templates.md
@@ -83,7 +83,7 @@ The `FooterTemplate` allows you to control the rendering of the footer within in
## See Also
* [Live Demo: AIPrompt](https://demos.telerik.com/blazor-ui/aiprompt/overview)
- * [Views Overview](slug://aiprompt-views-overview)
- * [Prompt View](slug://aiprompt-views-prompt)
- * [Output View](slug://aiprompt-views-output)
- * [Commands View](slug://aiprompt-views-commands)
\ No newline at end of file
+ * [Views Overview](slug:aiprompt-views-overview)
+ * [Prompt View](slug:aiprompt-views-prompt)
+ * [Output View](slug:aiprompt-views-output)
+ * [Commands View](slug:aiprompt-views-commands)
\ No newline at end of file
diff --git a/components/animationcontainer/overview.md b/components/animationcontainer/overview.md
index ffbd5056c3..2c72a6371b 100644
--- a/components/animationcontainer/overview.md
+++ b/components/animationcontainer/overview.md
@@ -12,7 +12,7 @@ position: 0
The Blazor Animation Container component enables you to create messages and popups or expandable containers. It lets you define its animation, size and position, and arbitrary content.
->tip If you are looking for an option to create [Notification](slug://notification-overview), [Tooltip](slug://tooltip-overview) or expandable container such as [Drawer](slug://drawer-overview), you may use the dedicated components.
+>tip If you are looking for an option to create [Notification](slug:notification-overview), [Tooltip](slug:tooltip-overview) or expandable container such as [Drawer](slug:drawer-overview), you may use the dedicated components.
## Creating Blazor AnimationContainer
@@ -51,7 +51,7 @@ The Blazor
## AppBar Sections
-Use the AppBar Sections to render arbitrary HTML content to match the UI and UX needs of your application. [Read more about the Blazor AppBar sections...](slug://appbar-sections)
+Use the AppBar Sections to render arbitrary HTML content to match the UI and UX needs of your application. [Read more about the Blazor AppBar sections...](slug:appbar-sections)
## Content Dividers
-The AppBar features separators and spacers that can visually divide the component items. [Read more about the Blazor AppBar separators and spacers.](slug://appbar-separators).
+The AppBar features separators and spacers that can visually divide the component items. [Read more about the Blazor AppBar separators and spacers.](slug:appbar-separators).
## Positioning
-You can control the position of the AppBar and how the component behaves according to the flow of the page. [Read more about the Blazor AppBar positioning.](slug://appbar-position).
+You can control the position of the AppBar and how the component behaves according to the flow of the page. [Read more about the Blazor AppBar positioning.](slug:appbar-position).
## AppBar Parameters
-The Blazor AppBar provides parameters to configure the component. Also check the [AppBar API Reference](slug://Telerik.Blazor.Components.TelerikAppBar) for a full list of properties.
+The Blazor AppBar provides parameters to configure the component. Also check the [AppBar API Reference](slug:Telerik.Blazor.Components.TelerikAppBar) for a full list of properties.
@[template](/_contentTemplates/common/parameters-table-styles.md#table-layout)
| Parameter | Type | Description |
| ----------- | ----------- | ----------- |
-| `Position` | `AppBarPosition`
(`None`) | The position of the AppBar on the page. [Read more about AppBar positioning.](slug://appbar-position) |
-| `PositionMode` | `AppBarPosition`
(`Static`) | Sets how the AppBar is positioned according to the flow of the document. [Read more about AppBar positioning.](slug://appbar-position) |
+| `Position` | `AppBarPosition`
(`None`) | The position of the AppBar on the page. [Read more about AppBar positioning.](slug:appbar-position) |
+| `PositionMode` | `AppBarPosition`
(`Static`) | Sets how the AppBar is positioned according to the flow of the document. [Read more about AppBar positioning.](slug:appbar-position) |
### Styling and Appearance
@@ -87,12 +87,12 @@ The following parameters enable you to customize the appearance of the Blazor Ap
| Parameter | Type | Description |
| --- | --- | --- |
-| `Class` | `string` | The CSS class to be rendered on the main wrapping element of the AppBar component, which is ``. Use for [styling customizations](slug://themes-override). |
+| `Class` | `string` | The CSS class to be rendered on the main wrapping element of the AppBar component, which is `
`. Use for [styling customizations](slug:themes-override). |
| `Height` | `string` | The height of the AppBar. |
| `ThemeColor` | `Telerik.Blazor.ThemeConstants.AppBar.ThemeColor` | Adjust the color of the AppBar |
| `Width` | `string` | The width of the AppBar. |
-You can find more information for customizing the AppBar appearance in the [Appearance article](slug://appbar-appearance).
+You can find more information for customizing the AppBar appearance in the [Appearance article](slug:appbar-appearance).
## AppBar Reference and Methods
@@ -121,11 +121,11 @@ To execute AppBar methods, obtain reference to the component instance with `@ref
## Next Steps
-* [Explore the AppBar Sections](slug://appbar-sections)
-* [Use the AppBar Sections](slug://appbar-separators)
-* [Customize the AppBar position](slug://appbar-position)
+* [Explore the AppBar Sections](slug:appbar-sections)
+* [Use the AppBar Sections](slug:appbar-separators)
+* [Customize the AppBar position](slug:appbar-position)
## See Also
* [Live AppBar Demos](https://demos.telerik.com/blazor-ui/appbar/overview)
-* [AppBar API Reference](slug://Telerik.Blazor.Components.TelerikAppBar)
+* [AppBar API Reference](slug:Telerik.Blazor.Components.TelerikAppBar)
diff --git a/components/appbar/sections.md b/components/appbar/sections.md
index bbf90fcbf5..e8117b843d 100644
--- a/components/appbar/sections.md
+++ b/components/appbar/sections.md
@@ -56,4 +56,4 @@ The nested `AppBarSection` tag exposes parameters:
## See Also
* [Live Demo: AppBar Overview](https://demos.telerik.com/blazor-ui/appbar/overview)
- * [AppBar Overview](slug://appbar-overview)
+ * [AppBar Overview](slug:appbar-overview)
diff --git a/components/appbar/separators.md b/components/appbar/separators.md
index 7c9d62d021..b185948ac9 100644
--- a/components/appbar/separators.md
+++ b/components/appbar/separators.md
@@ -38,7 +38,7 @@ The nested `AppBarSpacer` tag exposes the following parameters:
| Parameter | Type and Default Value | Description |
| ----------- | ----------- | ----------- |
| `Class` | `string` | The CSS class that will be rendered on the main wrapping element of the AppBar spacer. Use that class to cascade styles. |
-| `Size` | `string` | The width of the spacer. All `AppBarSpacer` tags without Size will take up the same amount of the remaining space between the [Sections](slug://appbar-sections). |
+| `Size` | `string` | The width of the spacer. All `AppBarSpacer` tags without Size will take up the same amount of the remaining space between the [Sections](slug:appbar-sections). |
| `Visible` | `bool`