Sync with Kendo UI Professional

telerik · Nov 1, 2024 · 6e5e241 · 6e5e241
1 parent 5e7ecd5
commit 6e5e241
Show file tree

Hide file tree

Showing 29 changed files with 663 additions and 1,168 deletions.
diff --git a/docs-aspnet/_contentTemplates/icons-list-section.md b/docs-aspnet/_contentTemplates/icons-list-section.md
@@ -0,0 +1,16 @@
+#icons-list-section
+
+## Icons List
+
+The <a href="https://www.telerik.com/design-system/docs/" target="_blank">Progress Design System</a> website provides a list of all <a href="https://www.telerik.com/design-system/docs/foundation/iconography/icon-list/" target="_blank">built-in icons in {{ site.product }}</a>.
+
+Each icon box in the icon list is clickable and reveals the following details:
+
+* CSS class aliases, if such exist. For example, `k-i-plus` is equivalent to `k-i-add`.
+* Unicode representation of the font icon glyph. For example, `\e11e` corresponds to the `plus` icon.
+* Ability to copy the glyph symbol of the font icon.
+* Ability to copy the HTML markup (`<svg>` tag) of the SVG icon.
+
+The icon list may contain icons which are not available in older versions of {{ site.product }} or even in the latest one. Such icons will be added in the next product version.
+
+#end
diff --git a/docs-aspnet/getting-started-core/first-steps-cli.md b/docs-aspnet/getting-started-core/first-steps-cli.md
@@ -112,7 +112,7 @@ Install the appropriate [.Net Core SDK 2.0 or later](https://www.microsoft.com/n
 	> * The Kendo UI scripts have to be placed after `jQuery`.
 	> * As of R3 2023 the Kendo UI bundles do not include the jQuery library in their `js` directories and you can use any available jQuery source you prefer (https://jquery.com/download/).
 
-	5.1 Go to `~\Views\Shared\_Layout.cshtml` and add the theme of your choice to the `<head>` of the document. Since the Microsoft project uses Bootstrap, you can use the Kendo UI SASS Bootstrap theme to match it.
+	5.1 Go to `~\Views\Shared\_Layout.cshtml` and add the theme of your choice to the `<head>` of the document. Since the Microsoft project uses Bootstrap, you can use the [Telerik UI Bootstrap theme]({% slug sassbasedthemes_overview%}#built-in-themes) to match it.
 
   5.2 The Microsoft template comes with a jQuery script reference in the body. Find it and move it to the head.
 

diff --git a/docs-aspnet/getting-started-core/first-steps-vs-extensions.md b/docs-aspnet/getting-started-core/first-steps-vs-extensions.md
@@ -282,11 +282,11 @@ Next, you can [change the look and feel](#changing-the-app-theme) of your applic
 
 ## Changing the App Theme
 
-The UI for ASP.NET Core suite comes with a set of 20+ built-in LESS-based and Sass-based themes that allow you to alter the visual appearance of the Telerik components. The most prominent themes are Default (our own styling), Material (based on the Material Design guidelines), and Bootstrap (a theme that matches Bootstrap guidelines).
+The UI for ASP.NET Core suite comes with a set of 20+ built-in [LESS-based]({% slug less_themes_overview_aspnetmvc6_aspnetmvc%}) and [Sass-based themes]({% slug sassbasedthemes_overview%}) that allow you to alter the visual appearance of the Telerik components. The most prominent themes are Default (our own styling), Material (based on the Material Design guidelines), and Bootstrap (a theme that matches Bootstrap guidelines).
 
-The themes are usually referenced in the _Layout file of the application. To change the theme, substitute the existing CSS reference in the _Layout with the new theme.
+The themes are usually referenced in the `_Layout` file of the application. To change the theme, substitute the existing CSS reference in the `_Layout` with the new theme.
 
-If during the creation the project you've chosen the Bootstrap theme, the `_Layout.cshtml` file should contain the following CSS link:
+If during the creation the project you've chosen the Bootstrap theme, the `_Layout.cshtml` file must contain the following CSS link:
 
 ```
 	<link href="https://kendo.cdn.telerik.com/themes/{{ site.themesCdnVersion }}/bootstrap/bootstrap-main.css" rel="stylesheet" type="text/css" />

diff --git a/docs-aspnet/getting-started-core/first-steps-vs-mac.md b/docs-aspnet/getting-started-core/first-steps-vs-mac.md
@@ -72,13 +72,13 @@ To get up and running with the project:
         @using Kendo.Mvc.UI
 
 
-7. Include the client-side resources in `~\Views\Shared\_Layout.cshtml`.
+7. Include the [client-side resources]({% slug copyclientresources_aspnetmvc6_aspnetmvc %}) in `~\Views\Shared\_Layout.cshtml`.
 
 	> * The CDN links and/or package versions have to point to the same UI for ASP.NET Core version which your project references.
 	> * The Kendo UI scripts have to be placed after `jQuery`.
 	> * As of R3 2023 the Kendo UI bundles do not include the jQuery library in their `js` directories and you can use any available jQuery source you prefer (https://jquery.com/download/).
 
-  7.1 Since the Microsoft template project uses Bootstrap, you can use the Kendo UI SASS Bootstrap theme to match it.
+  7.1 Since the Microsoft template project uses Bootstrap, you can use the [Telerik UI Bootstrap theme]({% slug sassbasedthemes_overview%}#built-in-themes) to match it.
 
 	7.2 The Microsoft template comes with a jQuery script reference in the body. Find it and move it to the head.
 

diff --git a/docs-aspnet/getting-started-core/first-steps.md b/docs-aspnet/getting-started-core/first-steps.md
@@ -153,14 +153,14 @@ The easiest way to add the Telerik NuGet feed to Visual Studio if you have purch
 
 ## Including the Telerik UI for ASP.NET Core Client-Side Resources
 
-To implement Telerik UI for ASP.NET Core in an application, you must provide not only the NuGet package with the components, but also the [client-side resources]({% slug copyclientresources_aspnetmvc6_aspnetmvc %}) like scripts and CSS files.
+To implement Telerik UI for ASP.NET Core in an application, you must provide not only the NuGet package with the components, but also the [client-side resources]({% slug copyclientresources_aspnetmvc6_aspnetmvc %}) like scripts and [theme files]({% slug sassbasedthemes_overview%}).
 
 >* The CDN links and/or package versions must point to the same UI for ASP.NET Core version that your project references.
 >* The Kendo UI scripts must be placed after the `jQuery` script.
 
 Before you can use a Telerik UI component, you must include the theme, the jQuery script, and the Kendo UI scripts:
 
-1. Go to `~\Views\Shared\_Layout.cshtml` and add the theme of your choice to the `<head>` of the document. Since the Microsoft project uses Bootstrap, you can use the Kendo UI SASS Bootstrap theme to match it:
+1. Go to `~\Views\Shared\_Layout.cshtml` and add the theme of your choice to the `<head>` of the document. Since the Microsoft project uses Bootstrap, you can use the [Telerik UI Bootstrap theme]({% slug sassbasedthemes_overview%}#built-in-themes) to match it:
 
 		<head>
 		...

diff --git a/docs-aspnet/html-helpers/layout/gridlayout/overview.md b/docs-aspnet/html-helpers/layout/gridlayout/overview.md
@@ -10,7 +10,7 @@ position: 1
 
 The {{ site.framework }} GridLayout component allows you to arrange the contents of the component in rows and columns in a grid structure. The arrangement of content relies on the CSS Grid functionality. For more information on the CSS Grid, refer to [the official CSS Grid documentation](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Grid_Layout).
 
-> The GridLayout is supported only when you use [Kendo UI Sass themes]({% slug sassbasedthemes_overview%}).
+> The GridLayout is supported only when you use [Kendo UI themes]({% slug sassbasedthemes_overview%}).
 
 ## Initializing the GridLayout
 

diff --git a/docs-aspnet/html-helpers/layout/stacklayout/overview.md b/docs-aspnet/html-helpers/layout/stacklayout/overview.md
@@ -10,7 +10,7 @@ position: 1
 
 The {{ site.framework }} StackLayout is a component that easily aligns multiple elements in a vertical or horizontal order.
 
-> The StackLayout is supported only when you use [Kendo UI Sass themes]({% slug sassbasedthemes_overview%}).
+> The StackLayout is supported only when you use [Kendo UI themes]({% slug sassbasedthemes_overview%}).
 
 ## Initializing the StackLayout
 

diff --git a/docs-aspnet/styles-and-layout/components-rendering-overview.md b/docs-aspnet/styles-and-layout/components-rendering-overview.md
@@ -20,7 +20,7 @@ The R1 2022 release introduces new rendering for several components. In the long
 - [List of Updated Components](#updated-components)
 - [Migrating from LESS Themes](#less-themes-migration)
 - [CSS Classes Migration](#css-classes-migration)
-- [JQuery Selectors Migration](#jquery-selectors-migration)
+- [jQuery Selectors Migration](#jquery-selectors-migration)
 
 
 ## What is the Reason Behind These Changes?
@@ -287,7 +287,7 @@ The following example shows a CSS rule that uses the `k-button` class as a selec
 
 Examples of the old rendering, old classes, new rendering, and new classes are available in the [appearance documentation](#updated-components) of each component.
 
-## JQuery Selectors Migration
+## jQuery Selectors Migration
 
 This section concerns developers who use the `k-{classname}` class selectors in custom JavaScript logic.
 

diff --git a/docs-aspnet/styles-and-layout/less-themes/less-themes-migration.md b/docs-aspnet/styles-and-layout/less-themes/less-themes-migration.md
@@ -21,7 +21,7 @@ For additional information about the SASS themes, visit the [`SASS-Based Themes`
 
 The LESS-based themes will receive the new [styling options]({% slug components_rendering_overview %}#styling-options) just like the SASS themes, however after 2022 the LESS themes will be officially deprecated. Customers who continue to use LESS themes after their deprecation will not be able to take advantage of the newest visual updates, features and bug fixes. This also means that Telerik UI for {{ site.framework }} versions starting from 2023 will be incompatible with the LESS themes and you won't be able to use the new versions with the LESS themes.
 
-The SASS-based themes provide unique swatches that are based on the main theme and can be updated at once. This allows us to change the design and color scheme of our components in a more timely manner which in turn leaves more time for new themes and swatches to be developed.
+The SASS-based themes provide unique [swatches]({% slug sassbasedthemes_overview %}#swatch) that are based on the main theme and can be updated at once. This allows us to change the design and color scheme of our components in a more timely manner which in turn leaves more time for new themes and swatches to be developed.
 
 With the LESS-based themes, each individual theme has its own code base. When a new component is introduced, or an existing one is updated, we must recreate each LESS theme to ensure that the new addition is rendered without problems. As a result, keeping the LESS-based themes updated takes a tremendous amount of time and resources.
 

diff --git a/docs-aspnet/styles-and-layout/sass-themes/browser-support.md b/docs-aspnet/styles-and-layout/sass-themes/browser-support.md
diff --git a/docs-aspnet/styles-and-layout/sass-themes/compatibility.md b/docs-aspnet/styles-and-layout/sass-themes/compatibility.md