TinyMCE license key configuration docs (#2012)

* documentation about tinymce license key configuration

* tinymce-customization.md aktualisieren

Co-authored-by: Steve Piercy <[email protected]>

* tinymce-customization.md aktualisieren

Co-authored-by: Steve Piercy <[email protected]>

* tinymce-customization.md aktualisieren

Co-authored-by: Steve Piercy <[email protected]>

* tinymce-customization.md aktualisieren

Co-authored-by: Steve Piercy <[email protected]>

* tinymce-customization.md aktualisieren

Co-authored-by: Steve Piercy <[email protected]>

* tinymce-customization.md aktualisieren

Co-authored-by: Steve Piercy <[email protected]>

* tinymce-customization.md aktualisieren

Co-authored-by: Steve Piercy <[email protected]>

* note about tinymce 8 and commercial license setup

* Apply suggestions from code review

Co-authored-by: Steve Piercy <[email protected]>

* Update docs/backend/upgrading/version-specific-migration/upgrade-to-62.md

oops sorry for that

Co-authored-by: Steve Piercy <[email protected]>

* Update docs/backend/upgrading/version-specific-migration/upgrade-to-62.md

Co-authored-by: Steve Piercy <[email protected]>

* Update docs/classic-ui/tinymce-customization.md

---------

Co-authored-by: Steve Piercy <[email protected]>

Author: petschki

docs/backend/upgrading/version-specific-migration/upgrade-to-62.md

@@ -91,3 +91,11 @@ This is because we keep a mapping from the old to the new location.
 For example, `plone.locking` registers that `plone.locking.browser.info.pt` has a new location, `plone.app.layout.viewlets.locking.pt`.
 You should rename your override to the new location if you no longer need compatibility with Plone 6.1 or earlier.
 ```
+
+## TinyMCE 8 for Classic UI
+
+The {term}`WYSIWYG` editor for Classic UI, {term}`TinyMCE`, was updated to version 8.
+
+You're now able to enter your commercial license key in the {menuitem}`TinyMCE` control panel.
+
+See {doc}`/classic-ui/tinymce-customization` for setup instructions.

docs/classic-ui/tinymce-customization.md

@@ -205,3 +205,39 @@ The file {file}`profiles/default/registry.xml` can be split in several files in
 the directory `profiles/default/registry` with arbitrary names ending in `.xml`.
 This makes it easier to maintain and reuse your registry files.
 ```
+
+## Use TinyMCE with a commercial license
+
+```{versionadded} Plone 6.2
+```
+
+If you own a commercial TinyMCE license, you can enter the key in the control panel {menuselection}`Site Setup --> TinyMCE --> Advanced`.
+
+The TinyMCE 8 commercial license key will have a `T8LK:` prefix.
+
+See more information in the [TinyMCE licensing documentation](https://www.tiny.cloud/docs/tinymce/latest/license-key/).
+
+If you have a TinyMCE license before version 8, read the important [License key migration documentation](https://www.tiny.cloud/docs/tinymce/latest/migration-from-7x/#license-key-system-update).
+
+
+### Commercial license key manager plugin
+
+Since we can't provide the license key manager plugin out of the box, because this is only shipped with a paid TinyMCE package, you have to provide the plugin in your own add-on package.
+
+See [Setting up the Commercial License Key Manager](https://www.tiny.cloud/docs/tinymce/latest/license-key/#setting-up-the-commercial-license-key-manager) for more information of how to get the plugin.
+
+You have to provide the plugin file as a static resource and register it in {menuselection}`Site Setup --> TinyMCE --> Plugins and Toolbar -> Custom plugins` as shown.
+
+```text
+licensekeymanager|++plone++path.to.licensekeymanager.resource.js
+```
+
+You can also provide this value in your add-on GenericSetup configuration, such as {file}`profiles/default/registry/tinymce.xml`.
+
+```xml
+<records prefix="plone" interface="plone.base.interfaces.controlpanel.ITinyMCESchema">
+  <value key="custom_plugins" purge="false">
+    <element>licensekeymanager|++plone++path.to.licensekeymanager.resource.js</element>
+  </value>
+</records>
+```