Licensing docs continued

Author: dimodi

_contentTemplates/common/get-started.md

@@ -179,3 +179,9 @@ You can learn more about the [`TelerikRootComponent` purpose and usage](slug://r
 }
 </style>
 #end
+
+#license-key-version
+
+@[template](/_contentTemplates/common/get-started.md#license-key-version)
+
+#end

_contentTemplates/common/issues-and-warnings.md

@@ -27,9 +27,7 @@ Open the Client `.csproj` file and ensure that the following switch is present.
 You may find useful the following Microsoft articles on securing your NuGet feed setup and supply chain as general best practices:
 
 * <a href="https://devblogs.microsoft.com/nuget/lock-down-your-dependencies-using-configurable-trust-policies/" target="_blank">Lock down your dependencies using configurable trust policies - Blog Post</a>
-
 * <a href="https://devblogs.microsoft.com/nuget/how-to-scan-nuget-packages-for-security-vulnerabilities/" target="_blank">How to Scan NuGet Packages for Security Vulnerabilities - Blog Post</a>
-
 * <a href="https://docs.microsoft.com/en-us/nuget/concepts/security-best-practices" target="_blank">Best practices for a secure software supply chain - MSDN docs</a>
 
 Telerik provides signed NuGet packages that you can verify.

deployment/ci-cd-build-server.md

@@ -12,6 +12,8 @@ position: 5
 
 This article explains some concepts and how to troubleshoot the most common errors related to setting up the Telerik NuGet packages for automated builds, CI and CD.
 
+> Telerik license keys are outside the scope of this article. Refer to article [Telerik License Key in CI/CD](slug://deployment-license-key)
+
 Sections in this article:
 
 * [Basics](#basics)
@@ -38,25 +40,19 @@ You must protect your credentials and/or the Telerik packages and ensure they ar
 When using Azure pipelines, we encourage you to review the following resources on setting things up:
 
 * Blog post: [Azure DevOps and Telerik NuGet Packages](https://www.telerik.com/blogs/azure-devops-and-telerik-nuget-packages)
-
 * Sample Repo and Video Tutorial: [Telerik DevOpsExamples by Lance McCarthy](https://github.com/LanceMcCarthy/DevOpsExamples)
 
->caption There are a couple of common questions and issues:
+There are a couple of common questions and issues:
 
 * Obtaining credentials - see the points above for either using your own credentials, or using a shared package source.
-
 * Telerik feed not being found - the most common reason for a problem is that the path to the `NuGet.Config` file is wrong (it should, by default, be at the root level).
-
 * An `index.json not found` error can occur from many root causes. If you have successfully authenticated, this error usually means that the feed wasn't able to be searched or connected to. A common reason is an incorrect feed URL, such as including a trailing slash - Correct: `https://nuget.telerik.com/v3/index.json` and Incorrect: `https://nuget.telerik.com/v3/index.json/`.
 
->caption A few things to double check to ensure correct setup:
+A few things to double check to ensure correct setup:
 
 * The Service connection is using Basic Authentication and the URL is correct (`https://nuget.telerik.com/v3/index.json` exactly, no trailing slash).
-
 * That Service Connection is selected as the credentials source.
-
 * The credentials being used have a UI for Blazor license.
-
 * Make sure that you use `dotnet restore` and not `nuget restore` in your pipeline step.
 
 
@@ -74,8 +70,8 @@ jobs:
     runs-on: windows-latest
 
     env:
-      TELERIK_USERNAME: ${ { secrets.MyTelerikAccountUsername } }  # remove the space between the brackets
-      TELERIK_PASSWORD: ${ { secrets.MyTelerikAccountPassword } }  # remove the space between the brackets
+      TELERIK_USERNAME: ${ { secrets.MyTelerikAccountUsername } }  # remove the spaces between the brackets
+      TELERIK_PASSWORD: ${ { secrets.MyTelerikAccountPassword } }  # remove the spaces between the brackets
 
 ````
 
@@ -139,6 +135,11 @@ RUN dotnet build "./MyBlazorApp.csproj" -c Release -o /app/build
 ````
 
 
+## Next Steps
+
+* [Set Up Telerik License Key in CI/CD Environment](slug://deployment-license-key)
+
+
 ## Further Reading
 
 @[template](/_contentTemplates/common/issues-and-warnings.md#nuget-security-links)

deployment/ci-cd-license-key.md

@@ -10,6 +10,46 @@ position: 7
 
 # Telerik License Key in CI/CD Environment
 
+This article describes how to set up and activate your [Telerik UI for Blazor license key](slug://installation-license-key) across a few popular CI/CD services by using environment variables.
+
+@[template](/_contentTemplates/common/get-started.md#license-key-version)
+
+## Basics
+
+When working with CI/CD platforms, always add the [`Telerik.Licensing` NuGet package](slug://getting-started/what-you-need#nuget-packages) as a project dependency. This package activates the Telerik Blazor components at build time by using the provided license key.
+
+The license activation process in a CI/CD environment involves the following steps:
+
+1. Add the `Telerik.Licensing` NuGet package as a dependency to all projects that reference Telerik UI for Blazor or Telerik Document Processing:
+    ````XML.skip-repl
+    <PackageReference Include="Telerik.Licensing" Version="1.*" />
+    ````
+1. Go to the <a href="https://www.telerik.com/account/your-licenses/license-keys" target="_blank">License Keys page</a> in your Telerik account and get your license key.
+1. Set your license key value as an environment variable with a name `TELERIK_LICENSE`.
+
+## Creating Environment Variables
+
+The recommended way to provide your license key to the `Telerik.Licensing` NuGet package in CI/CD environment is to use environment variables. Each CI/CD platform has a different process for setting environment variables. This article lists only some of the most popular examples.
+
+### Azure Pipelines (YAML)
+
+1. Create a new <a href="https://docs.microsoft.com/en-us/azure/devops/pipelines/process/variables?view=azure-devops&tabs=yaml%2Cbatch" target="_blank">user-defined variable</a> named `TELERIK_LICENSE`.
+1. Paste the contents of the license key file as a value.
+
+### Azure Pipelines (Classic)
+
+1. Create a new <a href="https://docs.microsoft.com/en-us/azure/devops/pipelines/process/variables?view=azure-devops&tabs=classic%2Cbatch" target="_blank">user-defined variable</a> named `TELERIK_LICENSE`.
+1. Paste the contents of the license key file as a value.
+
+### GitHub Actions
+
+1. Create a new <a href="https://docs.github.com/en/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository" target="_blank">Repository Secret</a> or an <a href="https://docs.github.com/en/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization" target="_blank">Organization Secret</a>.
+1. Set the name of the secret to `TELERIK_LICENSE` and paste the contents of the license file as a value.
+1. After running `npm install` or `yarn`, add a build step to activate the license:
+    ````YAML
+    env:
+        TELERIK_LICENSE: ${ { secrets.TELERIK_LICENSE } } # remove the spaces between the brackets
+    ````
 
 ## Next Steps
 

deployment/overview.md

@@ -14,6 +14,7 @@ position: 1
 This article explains the basics of deploying a Telerik-enabled Blazor web application. It consists of the following sections:
 
 * [Prerequisites](#prerequisites)
+* [License Key](#license-key)
 * [Telerik Components](#telerik-components)
 * [Next Steps and Troubleshooting](#next-steps-and-troubleshooting)
 
@@ -27,6 +28,9 @@ Refer to the Microsoft Blazor deployment documentation and make sure you can dep
 * [Host and deploy Blazor Server apps](https://learn.microsoft.com/en-us/aspnet/core/blazor/host-and-deploy/server)
 * [Host and deploy Blazor WebAssembly apps](https://learn.microsoft.com/en-us/aspnet/core/blazor/host-and-deploy/webassembly)
 
+## License Key
+
+Before building a Telerik Blazor app in a CI/CD environment, [set up a Telerik license key in CI/CD](slug://deployment-license-key). The process is different than in a [local development environment](slug://installation-license-key).
 
 ## Telerik Components
 

installation/license-key.md

@@ -12,7 +12,7 @@ position: 1
 
 Telerik UI for Blazor requires activation through a license key for both trial and commercial licenses. This article describes how to download your personal license key and use it to activate the Telerik Blazor components.
 
->tip This article applies to Telerik UI for Blazor version **7.2.0** and above.
+@[template](/_contentTemplates/common/get-started.md#license-key-version)
 
 ## Basics
 
@@ -36,7 +36,7 @@ To download and install the license key automatically, use one of the following
 
 Any of the above two tools will install a license key for you and make it available for all projects that you develop on your local machine.
 
->tip Update the license key [whenever necessary](#updates).
+>tip Update the license key [whenever necessary](#license-key-updates).
 
 ## Manual Installation
 
@@ -50,13 +50,13 @@ To download and install a license key file manually:
 
 The above step will make the license key available to all projects that you develop on your local machine. If you need to activate Telerik UI for Blazor only in a specific app, then save `telerik-license.txt` to the root folder of your project or solution.
 
->tip Update the license key [whenever necessary](#updates).
+>tip Update the license key [whenever necessary](#license-key-updates).
 
 >warning The license key file is personal and confidential. Do not commit this file to source control!
 
-## Updates
+## License Key Updates
 
-Whenever you renew or purchase a new Telerik product, always download and install a new license key. The new license key includes information about all previous purchases. This process is referred to as a *license key update*.
+Whenever you renew or purchase a new Telerik license, always install a new license key. The new license key includes information about all previous purchases. This process is referred to as a *license key update*.
 
 * If you used [automatic license key installation](#automatic-installation), then open the tool that you used to download and install the license key file. You can also update the license key file by using the [manual steps above](#manual-installation).
 * If you used the [manual license key installation](#manual-installation), then repeat the same steps.
@@ -68,5 +68,6 @@ Whenever you renew or purchase a new Telerik product, always download and instal
 
 ## See Also
 
+* [Troubleshoot License Key Errors](slug://troubleshooting-license-key-errors)
 * [Get Started with a Blazor Web App](slug://getting-started/web-app)
 * [Workflow Details for Telerik UI for Blazor](slug://getting-started/what-you-need)

troubleshooting/license-key-errors.md

@@ -12,16 +12,20 @@ position: 3
 
 This page provides solutions for license key errors that you may encounter while building Telerik Blazor apps.
 
+@[template](/_contentTemplates/common/get-started.md#license-key-version)
+
 ## Basics
 
 A Telerik license key error may occur in the following scenarios:
 
-* Using a perpetual license with a product version that was released outside the validity period of your license.
+* Missing license key.
 * Using an expired subscription license after the end of the subscription term.
+* Using a perpetual license with a product version that was released outside the validity period of your license.
 * Using an expired trial license.
-* Missing license key. [Install a license key file](slug://installation-license-key). If you already downloaded it, make sure it's [saved at the right place](slug://installation-license-key#manual-installation).
-* Using an outdated license key. Always [update your license key](slug://installation-license-key#updates) after renewing your licenses or purchasing additional Telerik products.
-* Using a license key that doesn't include Telerik UI for Blazor. If you already have a commercial or trial Telerik UI for Blazor license, then [update your license key](slug://installation-license-key#updates). Otherwise, purchase or renew Telerik UI for Blazor, or start a trial to evaluate the product.
+* Using an outdated license key after making renewals or purchases.
+* Using a license key that doesn't include Telerik UI for Blazor.
+
+Refer to the error messages below for specific tips.
 
 ## Error Messages
 
@@ -42,13 +46,13 @@ Follow the [automatic](slug://installation-license-key#automatic-installation) o
 
 ### Your subscription license has expired
 
-<a href="https://www.telerik.com/account/your-licenses" target="_blank">Renew your subscribtion</a>. Then, [update your license key](slug://installation-license-key).
+<a href="https://www.telerik.com/account/your-licenses" target="_blank">Renew your subscribtion</a>. Then, [update your license key](slug://installation-license-key#license-key-updates).
 
 ### Your perpetual license is invalid
 
 You are using a product version released outside the validity period of your perpetual license. To remove the error message, do either of the following:
 
-* <a href="https://www.telerik.com/account/your-licenses" target="_blank">Renew your subscribtion</a>. Then, [download and install a new license key](slug://installation-license-key).
+* <a href="https://www.telerik.com/account/your-licenses" target="_blank">Renew your subscribtion</a>. Then, [update your license key](slug://installation-license-key#license-key-updates).
 * Downgrade your app to a Telerik UI for Blazor version that was released within the subscription period of your perpetual license.
 
 ### Your trial license has expired
@@ -57,8 +61,9 @@ You are using a product version released outside the validity period of your per
 
 ### Your license is not valid for the detected product(s)
 
-<a href="https://www.telerik.com/purchase/blazor-ui" target="_blank">Review the purchase options for Telerik UI for Blazor</a>. Then, [update your license key](slug://installation-license-key).
+<a href="https://www.telerik.com/purchase/blazor-ui" target="_blank">Review the purchase options for Telerik UI for Blazor</a>. Then, [update your license key](slug://installation-license-key#license-key-updates).
 
 ## See Also
 
-* [Prevent browser caching during version upgrades](slug://common-kb-browser-cache-buster)
+* [Download and Install License Key](slug://installation-license-key)
+* [Use License Keys in CI/CD](slug://deployment-license-key)