DOC-3226: Enhance license key documentation for TinyMCE 8, clarifying T8LK prefix requirements and updating integration references across various frameworks.

Author: kemister85

modules/ROOT/pages/8.0-release-notes.adoc

@@ -124,11 +124,18 @@ For information on using Enhanced Skins & Icon Packs, see: xref:enhanced-skins-a
 
 === Enhanced license key system with T8LK prefix
 
-The license key system in {productname} 8 has been enhanced to provide improved subscription access control and streamlined renewal processes. All commercial license keys for self-hosted deployments now require the `T8LK:` prefix to indicate version 8 compatibility.
+The license key system in {productname} 8 has been enhanced to provide improved subscription access control and streamlined renewal processes. This change primarily affects self-hosted deployments, as cloud users ({cloudname}) do not require a license key.
 
-Key changes include:
+[IMPORTANT]
+====
+* If you use {cloudname}, no license key is required - your cloud subscription automatically includes the commercial license.
+* For self-hosted deployments, all commercial license keys must use the new `T8LK:` prefix format.
+* Existing TinyMCE 7 license keys cannot be made compatible with TinyMCE 8 by adding the T8LK prefix.
+====
 
-* All commercial license keys must start with `"T8LK:"` prefix
+Key changes for self-hosted deployments:
+
+* New `T8LK:` prefix requirement for all commercial license keys.
 * Enhanced JWT-based validation that runs entirely in the browser
 * No server communication or "phone home" checks required
 * Support for both date-based and version-locked keys
@@ -137,11 +144,23 @@ Key changes include:
 
 [IMPORTANT]
 ====
-* GPL usage still requires setting `license_key: 'gpl'` (case insensitive)
-* For open source projects using premium features, use the combined format: `license_key: 'GPL+T8LK:...'`
-* The license key is not required when using {cloudname} with an API key
+*Cloud Deployments:*
+
+* When using {cloudname}, only an API key is required - no license key needed
+* Your cloud subscription automatically includes the commercial license
+
+*Self-hosted Deployments:*
+
+* Commercial use: Contact your account manager or visit link:https://www.tiny.cloud/my-account[Tiny Cloud Account] to obtain a T8LK-prefixed license key
+* GPL use: Set `license_key: 'gpl'` (case insensitive)
+* Open source projects using premium features: Use the combined format `license_key: 'GPL+T8LK:...'`
 ====
 
+=== Upgrading from TinyMCE 7
+
+* *Cloud Users ({cloudname})*: No license key changes needed - simply update your {productname} version.
+* *Self-hosted Users*: Contact your account manager to obtain a new T8LK-prefixed license key.
+
 For more information on the new license key system, see: xref:license-key.adoc[License Key].
 
 

modules/ROOT/pages/license-key.adoc

@@ -86,7 +86,7 @@ a|
   ** Cloud services access
   ** Premium plugin access
   ** Automatic updates
-* No license key required (defaults to a commercial license)
+* No license key required as its automatically issued. (defaults to a commercial license)
 a|
 * Fully managed service:
   ** No local deployment needed
@@ -190,6 +190,37 @@ In addition to the editor being readonly, a console log warning message and/or e
 
 The license key ensures compliance with {productname} licensing terms. It's part of our efforts to refine the license key system and may have additional functionalities in the future.
 
+=== How do I obtain a TinyMCE 8 license key?
+
+To obtain a new TinyMCE 8 license key (T8LK-prefixed):
+
+* *Existing customers*: Contact your account manager or visit link:https://www.tiny.cloud/my-account[Tiny Cloud Account] to upgrade your subscription.
+* *New customers*: Visit link:https://www.tiny.cloud/pricing[Tiny Cloud Pricing] to purchase a new license.
+
+[IMPORTANT]
+====
+Existing TinyMCE 7 license keys cannot be modified to work with TinyMCE 8 by adding the T8LK prefix. A new TinyMCE 8 license must be obtained through the proper channels listed above.
+====
+
+=== I'm upgrading from {productname} 7 - how do I get a {productname} 8 license key?
+
+If you are using {cloudname} (cloud-hosted):
+
+* No license key is required - simply update your {productname} version as your cloud subscription includes the commercial license.
+
+If you are an existing {productname} 7 self-hosted customer upgrading to {productname} 8:
+
+. *Active Subscription*:
+* Contact your account manager or visit link:https://www.tiny.cloud/my-account[Tiny Cloud Account] to obtain a new T8LK-prefixed license key.
+. *Expired Subscription*:
+* Contact your account manager or visit link:https://www.tiny.cloud/pricing[Tiny Cloud Pricing] to renew your subscription.
+* A new T8LK-prefixed license key will be provided as part of the renewal process.
+
+[NOTE]
+====
+Your existing {productname} 7 license key will continue to work with TinyMCE 7 self-hosted installations. But, you will require a separate T8LK-prefixed license key for {productname} 8 editor instances for self-hosted installations.
+====
+
 === How can I get further assistance?
 
 For any licensing or technical support questions, see our available options on the https://www.tiny.cloud/docs/tinymce/latest/support/[support page.]

modules/ROOT/partials/integrations/angular-tech-ref.adoc

@@ -130,18 +130,7 @@ include::partial$misc/get-an-api-key.adoc[]
 [[licensekey]]
 === `+licenseKey+`
 
-{cloudname} License key.
-
-Use this when self-hosting {productname} instead of loading from {cloudname}. For more information, see: xref:license-key.adoc[License Key].
-
-*Type:* `+String+`
-
-*Default value:* `+undefined+`
-
-*Possible values:*
-* `undefined` - Use this when loading from {cloudname} with an API key
-* `'gpl'` - For open source projects using GPL license
-* `'T8LK:...'` - For commercial {productname} installations
+include::partial$integrations/common/license-key-property.adoc[]
 
 ==== Example: Commercial license
 [source,html]

modules/ROOT/partials/integrations/blazor-tech-ref.adoc

@@ -188,16 +188,8 @@ In your component:
 
 === `LicenseKey`
 
-Specifies the {productname} license key. Required for self-hosted deployments of {productname}. This property is not required for deployments using the {cloudname}.
 
-License keys must start with the "T8LK:" prefix and use client-side JWT validation that runs entirely in the browser, requiring no server communication or "phone home" checks. For more information, see: xref:license-key.adoc[License Key].
-
-*Type:* `+String+`
-
-*Possible values:*
-* `null` - Use this when loading from {cloudname} with an API key
-* `"gpl"` - For open source projects using GPL license
-* `"T8LK:..."` - For commercial {productname} installations
+include::partial$integrations/common/license-key-property.adoc[]
 
 ==== Example: Commercial license (TinyMCE 8+)
 [source,cs]

modules/ROOT/partials/integrations/common/license-key-property.adoc

@@ -0,0 +1,19 @@
+Specifies the {productname} license key. Required for self-hosted deployments of {productname}. This property is **not required** for cloud-only deployments using the {cloudname} as your cloud subscription automatically includes the commercial license. For more information, see: xref:license-key.adoc[License Key].
+
+*Type:* `+String+`
+
+*Default value:* `+undefined+`
+
+*Possible values:*
+* `undefined` - Use this when loading from {cloudname} with an API key
+* `'gpl'` - For open source projects using GPL license
+* `'T8LK:...'` - For commercial {productname} installations (must use this prefix for version 8+)
+
+[NOTE]
+====
+In hybrid deployments (using both cloud and self-hosted features):
+
+* You can provide both an API key and a license key
+* The editor will use cloud services when available
+* It will automatically fall back to the local license key if cloud services are not contactable
+====

modules/ROOT/partials/integrations/react-tech-ref.adoc

@@ -187,18 +187,8 @@ include::partial$misc/get-an-api-key.adoc[]
 [[licenseKey]]
 === `+licenseKey+`
 
-{cloudname} License key.
 
-Use this when self-hosting {productname} instead of loading from {cloudname}. License keys must start with the "T8LK:" prefix and use client-side JWT validation that runs entirely in the browser, requiring no server communication or "phone home" checks. For more information, see: xref:license-key.adoc[License Key].
-
-*Type:* `+String+`
-
-*Default value:* `+undefined+`
-
-*Possible values:*
-* `undefined` - Use this when loading from {cloudname} with an API key
-* `'gpl'` - For open source projects using GPL license
-* `'T8LK:...'` - For commercial {productname} installations
+include::partial$integrations/common/license-key-property.adoc[]
 
 ==== Example: Commercial license
 [source,jsx]

modules/ROOT/partials/integrations/svelte-quick-start.adoc

@@ -118,7 +118,7 @@ export default defineConfig({
 ----
 . Open `+src/App.svelte+` and replace the contents with:
 +
-[source,javascript]
+[source,svelte]
 ----
 <script>
 import Editor from '@tinymce/tinymce-svelte';

modules/ROOT/partials/integrations/svelte-tech-ref.adoc

@@ -56,18 +56,8 @@ include::partial$misc/get-an-api-key.adoc[]
 [[licensekey]]
 === `+licenseKey+`
 
-{cloudname} License key.
 
-Use this option when self-hosting {productname} instead of loading from {cloudname}. License keys must start with the "T8LK:" prefix and use client-side JWT validation that runs entirely in the browser, requiring no server communication or "phone home" checks. For more information, see: xref:license-key.adoc[License Key].
-
-*Type:* `+String+`
-
-*Default value:* `+undefined+`
-
-*Possible values:*
-* `undefined` - Use this when loading from {cloudname} with an API key
-* `'gpl'` - For open source projects using GPL license
-* `'T8LK:...'` - For commercial {productname} installations
+include::partial$integrations/common/license-key-property.adoc[]
 
 ==== Example: Commercial license
 [source,jsx]

modules/ROOT/partials/integrations/vue-tech-ref.adoc

@@ -137,18 +137,8 @@ include::partial$misc/get-an-api-key.adoc[]
 [[license-key]]
 === `+licenseKey+`
 
-{cloudname} License key.
 
-Use this when self-hosting {productname} instead of loading from {cloudname}. License keys must start with the "T8LK:" prefix and use client-side JWT validation that runs entirely in the browser, requiring no server communication or "phone home" checks. For more information, see: xref:license-key.adoc[License Key].
-
-*Type:* `+String+`
-
-*Default value:* `+undefined+`
-
-*Possible values:*
-* `undefined` - Use this when loading from {cloudname} with an API key
-* `'gpl'` - For open source projects using GPL license
-* `'T8LK:...'` - For commercial {productname} installations
+include::partial$integrations/common/license-key-property.adoc[]
 
 ==== Example: Commercial license
 [source,html]

modules/ROOT/partials/integrations/webcomponent-tech-ref.adoc

@@ -79,16 +79,7 @@ To use {productname} from the {cloudname}, add the `+api-key+` attribute to the
 [[licensekey]]
 == Setting the license key
 
-When self-hosting {productname}, specify a license key using the `+license-key+` attribute on the `+tinymce-editor+` element. License keys must start with the "T8LK:" prefix and use client-side JWT validation that runs entirely in the browser, requiring no server communication or "phone home" checks. Do not use both an API key and a license key - use API key for cloud deployments, and license key for self-hosted deployments. For more information, see: xref:license-key.adoc[License Key].
-
-*Type:* `+String+`
-
-*Default value:* `+undefined+`
-
-*Possible values:*
-* `undefined` - Use this when loading from {cloudname} with an API key
-* `"gpl"` - For open source projects using GPL license
-* `"T8LK:..."` - For commercial {productname} installations
+include::partial$integrations/common/license-key-property.adoc[]
 
 === Example: Commercial license
 [source,html]