docs(common): static asset requirements and issues

Author: marin-bratanov

_contentTemplates/common/get-started.md

@@ -146,3 +146,23 @@ To setup a local NuGet package source, so you can install the Telerik components
 
 1. On the loaded page choose from your purchased products or trial downloads **Progress® Telerik® UI for Blazor**, and click on it.
 #end
+
+#client-app-startup-file-mod-code
+        namespace MyBlazorAppName.Client
+        {
+            public class Startup
+            {
+                public void ConfigureServices(IServiceCollection services)
+                {
+                    //more code may be present here
+                    services.AddTelerikBlazor();
+                }
+        
+                public void Configure(IComponentsApplicationBuilder app)
+                {
+                    //more code may be present here
+                    app.UseStaticFiles();
+                }
+            }
+        }
+#end

_contentTemplates/common/js-interop-file.md

@@ -1,5 +1,5 @@
 #add-blazor-js-file-to-component
- add the `telerik-blazor.js` file to your main index file. For a client-side Blazor app, it is `wwwroot/index.html`, and for a server-side Blazor app it is `~/Pages/Index.cshtml`. For example:
+ Add the `telerik-blazor.js` file to your main index file. For a client-side Blazor app, it is `wwwroot/index.html`, and for a server-side Blazor app it is `~/Pages/Index.cshtml`.
 
 @[template](/_contentTemplates/common/js-interop-file.md#js-interop-file-snippet)
 
@@ -9,6 +9,8 @@
  add the `telerik-blazor.js` file to your main index file - `wwwroot/index.html`:
 
 @[template](/_contentTemplates/common/js-interop-file.md#js-interop-file-snippet)
+
+    >note @[template](/_contentTemplates/common/js-interop-file.md#static-asset-issue-in-pure-client-project)
 #end
 
 #add-js-interop-file-to-getting-started-server
@@ -27,3 +29,7 @@
 
 #end
 
+#static-asset-issue-in-pure-client-project
+This static asset works for server-side and ASP.NET Core hosted client-side project types. If you use a purely client-side model, you must reference the script from our CDN, because of [an issue in the framework](https://github.com/aspnet/AspNetCore/issues/10986): `https://kendo.cdn.telerik.com/blazor/1.2.0/telerik-blazor.min.js`. Make sure that the version in the URL matches the version of the Telerik Blazor package used in your project.
+#end
+

getting-started/client-blazor.md

@@ -55,23 +55,11 @@ For client-side Blazor, we recommend the usage of `Blazor (ASP.NET Hosted)` proj
 
 1. @[template](/_contentTemplates/common/js-interop-file.md#add-js-interop-file-to-getting-started-client)
 
-1. Open the `~/Startup.cs` file in the client web application and register the Telerik Blazor service:
+1. Open the `~/Startup.cs` file in the client web application and amend it to support static assets and to register the Telerik Blazor service:
 
     **C#**
 
-        namespace MyBlazorAppName.Client
-        {
-            public class Startup
-            {
-                public void ConfigureServices(IServiceCollection services)
-                {
-                    //more code may be present here
-                    services.AddTelerikBlazor();
-                }
-                
-                //more code may be present here
-            }
-        }
+@[template](/_contentTemplates/common/get-started.md#client-app-startup-file-mod-code)
 
 1. @[template](/_contentTemplates/common/issues-and-warnings.md#mono-linker-issue)
 

getting-started/what-you-need.md

@@ -11,7 +11,7 @@ position: 3
 
 # What You Need to Use the Telerik Blazor Components
 
-This article explains the packages you need to use the Telerik UI for Blazor components, and how to get them.
+This article explains the packages you need to use the Telerik UI for Blazor components, how to get them, and how to configure your project to include the Telerik Blazor components.
 
 To use the Telerik UI for Blazor, you need:
 
@@ -52,15 +52,13 @@ To have the Telerik Blazor components look and behave as expected in the browser
             <link rel="stylesheet" href="https://unpkg.com/@progress/kendo-theme-default@latest/dist/all.css" />
         </head>
 
-* Our JS Interop file. It provides features that cannot be implemented with native Blazor. You need to
-
-    @[template](/_contentTemplates/common/js-interop-file.md#add-js-interop-file-to-getting-started-client)
+* Our JS Interop file. It provides features that cannot be implemented with native Blazor. @[template](/_contentTemplates/common/js-interop-file.md#add-blazor-js-file-to-component)
 
-    For a server-side Blazor scenario, add it to the `~/Pages/_Host.razor` file.
+    >warning @[template](/_contentTemplates/common/js-interop-file.md#static-asset-issue-in-pure-client-project)
 
 ## Project Configuration
 
-To have the framework recognize the Telerik Components, you must register them in the `Startup.cs` file of your Blazor project (if you are using [client-side Blazor](), this is the client web application's file):
+To have the framework recognize the Telerik Components, you must register them in the `Startup.cs` file of your Blazor project (if you are using client-side Blazor, this is the Client web application's file):
 
 ````Startup.cs
 namespace MyBlazorAppName
@@ -78,9 +76,18 @@ namespace MyBlazorAppName
 }
 ````
 
+### Client-side Project Considerations
+
 If you are using a **client-side Blazor** project, 
 @[template](/_contentTemplates/common/issues-and-warnings.md#mono-linker-issue)
 
+To enable the use of static assets for the JS Interop file, you must be using an ASP.NET Core hosted project and add the following line to your Client project `Startup.cs` file:
+
+**C#**
+
+@[template](/_contentTemplates/common/get-started.md#client-app-startup-file-mod-code)
+
+
 ## Before You Continue
 
 Before you continue, make sure you can use Blazor. Read below for more details.