Sync with Kendo UI Professional

Author: Kendo Bot

docs-aspnet-core/_config.yml

@@ -28,15 +28,9 @@ navigation:
      "vs-integration":
         title: "Visual Studio Integration"
         position: 5
-     "migration":
-        title: "Migration"
-        position: 6
-     "tutorials":
-        title: "Tutorials"
+     "backwards-compatibility":
+        title: "Breaking Changes"
         position: 7
-     "troubleshoot":
-        title: "Troubleshooting"
-        position: 8
 
 
 

docs-aspnet-core/backwards-compatibility/2018-backwards-compatibility.md

@@ -9,11 +9,17 @@ position: 1
 
 # 2018 Releases
 
+## Kendo UI R2 2018
+
+### Changes from 2018 R1 SP1
+
+As of the Kendo UI R2 2018 release, the sample application, which represents an offline version of the [Telerik UI for ASP.NET Core Demos](http://demos.telerik.com/aspnet-core), is only available for Visual Studio 2017. The Visual Studio 2015 version which contains the deprecated `project.json` base version is no longer distributed.
+
 ## Kendo UI R1 2018 SP1
 
 ### Changes from 2018 R1
 
-To enable more complex widget configuration scenarios and ensure the tag-naming consistency across the Telerik UI for ASP.NET Core suite, the Kendo UI R1 2018 release introduces changes in the tags of the following wrappers:
+To enable more complex scenarios for widget configuration and ensure the tag-naming consistency across the Telerik UI for ASP.NET Core suite, the Kendo UI R1 2018 release introduces changes in the tags of the following wrappers:
 
 * Dialog&mdash;Previously, it was possible to nest content directly in the `<kendo-dialog>` tag. Now the content must be nested within a `<content>` tag.
 * Window&mdash;Previously, it was possible to nest content directly in the `<kendo-window>` tag. Now the content must be nested within a `<content>` tag.

docs-aspnet-core/getting-started/getting-started-linux.md

@@ -56,7 +56,7 @@ Below are listed the steps for you to follow when creating an ASP.NET Core web s
 
 		Restore complete, 10070ms elapsed
 
-		kendo@kendo-docker:~/Projects/WebApplicationBasic$
+		kendo@kendo-docker:~/Projects$
 
 8. Start the application by running [`dotnet run`](https://docs.microsoft.com/en-us/dotnet/core/tools/dotnet-run). The following example demonstrates the response you are expected to receive.
 
@@ -74,16 +74,7 @@ Below are listed the steps for you to follow when creating an ASP.NET Core web s
 
 ### Add the Telerik.UI.for.AspNet.Core NuGet Package
 
-1. Open the `project.json` file by using a text editor, add the `Telerik.UI.for.AspNet.Core` dependency, and replace `productVersion` with an actual **Telerik UI for ASP.NET Core** version—for example, `{{site.cdnVersion}}`.
-
-    ###### Example
-
-		"dependencies": {
-			...
-			"Telerik.UI.for.AspNet.Core": "{{site.cdnVersion}}"
-		}
-
-2. Add the private Telerik NuGet feed. You could either:
+1. Add the private Telerik NuGet feed. You could either:
 
 	* Create the following two configuration files containing your `telerik.com` credentials on your machine: `~/.config/NuGet/NuGet.Config` and `~/.nuget/NuGet/NuGet.Config`; or
 	* Create a `NuGet.Config` file in the project folder.
@@ -108,6 +99,12 @@ Below are listed the steps for you to follow when creating an ASP.NET Core web s
         </configuration>
         ```
 
+2. Install the `Telerik.UI.for.AspNet.Core` dependency:
+
+    ###### Example
+
+        dotnet add package Telerik.UI.for.AspNet.Core
+
 3. Open `Startup.cs` by using a text editor (IDE) and update it in the way demonstrated in the following examples.
 
     * Locate the `ConfigureServices` method and add a call to `services.AddKendo` at the end.
@@ -146,7 +143,7 @@ Below are listed the steps for you to follow when creating an ASP.NET Core web s
 
 5. Copy the Kendo UI client-side resources.
 
-    * Manual installation&mdash;To manually install the resources, copy the `js` and `styles` folders from the `telerik.ui.for.aspnetmvc` archive to `wwwroot\lib\kendo-ui`.
+    * Manual installation&mdash;To manually install the resources, copy the `js` and `styles` folders from the `telerik.ui.for.aspnet.core` archive to `wwwroot\lib\kendo-ui`.
 
         **Figure 2. Kendo UI resources**
 

docs-aspnet-core/introduction.md

@@ -75,17 +75,19 @@ Telerik UI for ASP.NET Core contains the following directories:
 * `vsdoc`—The intellisense definitions for the Kendo combined scripts (as the above).
 * `VSExtensions`—The extensions for Visual Studio 2015 and 2017.
 * `wrappers\aspnetcore\Binaries\AspNet.Core`—Containing the .nupkg NuGet package file.
-* `wrappers\aspnetcore\Examples\AspNet.Core\VS2015`—The ASP.NET Core sample application built with Visual Studio 2015.
 * `wrappers\aspnetcore\Examples\AspNet.Core\VS2017`—The ASP.NET Core sample application built with Visual Studio 2017.
 * `wrappers\aspnetcore\EditorTemplates\razor`—The ready-to-use editor templates based on the Kendo UI widgets.
 
 ## Sample Application
 
 Telerik UI for ASP.NET Core comes with a sample .NET Core application which is an offline version of the [Telerik UI for ASP.NET Core Demos](http://demos.telerik.com/aspnet-core). The sample application is available in the following versions:
 
-* The .NET Core application built with Visual Studio 2015
 * The .NET Core application built with Visual Studio 2017
 
+> **Important**
+>
+> As of the Kendo UI R2 2018 release, the Visual Studio 2015 version of the sample application is no longer distributed because of its deprecated format and limited tooling support.
+
 ### Running the Sample Application
 
 To run the sample application:
@@ -94,7 +96,6 @@ To run the sample application:
 
 1. Open the sample Visual Studio Project:
 
-  * (For Visual Studio 2015) Open `wrappers\aspnetcore\Examples\AspNet.Core\VS2015\Kendo.Mvc.Examples\Kendo.Mvc.Examples.xproj`.
   * (For Visual Studio 2017) Open `wrappers\aspnetcore\Examples\AspNet.Core\VS2017\Kendo.Mvc.Examples\Kendo.Mvc.Examples.xproj`.
 
 1. Press `CTRL+F5` to build and run the application.

styles/web/Default/card/layout.less

@@ -12,8 +12,8 @@
 @card-actions-padding-x: 8px;
 @card-actions-padding-y: 8px;
 @card-actions-border-width: 1px;
-@button-padding-x: 8px;
-@button-padding-y: 4px;
+@card-button-padding-x: 8px;
+@card-button-padding-y: 4px;
 @card-deck-gap: 16px;
 
 // Card
@@ -168,7 +168,7 @@
     }
 
     > .k-button.k-flat:first-child {
-        margin-left: (-@button-padding-x);
+        margin-left: (-@card-button-padding-x);
     }
 }
 .k-card-action {
@@ -180,7 +180,7 @@
 
     > .k-button {
         .border-radius( 0 );
-        padding: (@card-actions-padding-y + @button-padding-y) @card-actions-padding-x;
+        padding: (@card-actions-padding-y + @card-button-padding-y) @card-actions-padding-x;
         flex: 1 1 auto;
     }
 }

styles/web/common/menu.less

@@ -159,7 +159,8 @@ ul.k-menu-vertical > .k-item
 
 .k-menu-scroll-wrapper .k-item > .k-link > .k-i-arrow-60-right,
 .k-popups-wrapper .k-item > .k-link > .k-i-arrow-60-right,
-.k-menu-group .k-link > .k-menu-expand-arrow
+.k-menu-group .k-link > .k-menu-expand-arrow,
+.k-menu-vertical .k-link > .k-menu-expand-arrow,
 {
     position: absolute;
     top: 50%;

styles/web/kendo.rtl.less

@@ -513,16 +513,17 @@
     margin-left: -8px;
 }
 
-.k-rtl .k-menu-group .k-menu-expand-arrow
+.k-rtl .k-menu-group .k-menu-expand-arrow,
+.k-rtl .k-menu-vertical .k-link > .k-menu-expand-arrow,
 {
     right: auto;
     left: .2rem;
 }
 
-.k-rtl .k-menu .k-group .k-item > .k-link
+.k-rtl .k-menu .k-menu-group .k-item > .k-link
 {
-    padding-left: 1.8em;
-    padding-right: .9em;
+    padding-left: 4.929em;
+    padding-right: 1.714em;
 }
 
 .k-rtl .k-menu .k-image,