DOC-3329: Remove theme option, re-feactor editor-theme.adoc and improve bundling-plugins.adoc structure.

Author: kemister85

modules/ROOT/pages/bundling-plugins.adoc

@@ -3,14 +3,24 @@
 :description_short: Information on bundling plugins
 :description: Information on bundling TinyMCE plugins using module loading
 
+== Overview
+
+{productname} plugins can be bundled using module loaders such as Webpack, Rollup, or Vite. This guide covers how to include both community and premium plugins in your application bundle.
+
+{productname} includes both community and premium plugins:
+
+* **Community plugins**: Available with all {productname} installations
+* **Premium plugins**: Available with paid {productname} subscriptions via the `+tinymce-premium+` package
+
 :editorcomponent: plugin
 include::partial$module-loading/bundling-ref-example.adoc[]
 :!editorcomponent:
 
 include::partial$plugin-files/plugin-file-index.js.adoc[]
 
+== Bundling syntax examples
 
-Example syntax for including the example "<plugincode>" plugin in a bundle using `content.js`for bundling:
+The following examples show the syntax for including plugins in a bundle. The examples use a placeholder `+<plugincode>+` to represent any plugin name:
 
 [cols='1,2,3']
 |===
@@ -81,27 +91,28 @@ require('<path_to_tinymce_premium_zip>/plugins/<plugincode>');
 
 After installing the `+tinymce-premium+` package, you need to configure the plugins in your editor. There are two main approaches:
 
-=== License key manager
-
 [IMPORTANT]
 ====
-Remember to include the `+licensekeymanager+` plugin when using premium plugins with a commercial license. The editor will not function properly without it. For more information, see: xref:license-key.adoc[License Key].
-====
+*License Key Manager Requirement:*
 
-When bundling:
+When using premium plugins with a commercial license, you must include the `+licensekeymanager+` plugin. The editor will not function properly without it. For more information, see: xref:license-key.adoc[License Key].
+
+*xref:bundling-plugins.adoc#bundling-recommended[When bundling]:*
 [source,js]
 ----
 import 'tinymce-premium/plugins/licensekeymanager';
 ----
 
-When using `+external_plugins+`:
+*xref:bundling-plugins.adoc#using-external-plugins[When using `+external_plugins+`]:*
 [source,js]
 ----
 external_plugins: {
   'licensekeymanager': '<path_to_premium_plugins>/licensekeymanager/plugin.min.js'
 }
 ----
+====
 
+[[bundling-recommended]]
 === Bundling (Recommended)
 
 For most modern applications, bundling premium plugins is recommended. This includes the plugin code directly in your application bundle.
@@ -130,6 +141,7 @@ tinymce.init({
 
 For complete bundling examples, see the <<premium-plugins,Premium plugins>> and <<community-plugins,Community plugins>> sections below.
 
+[[using-external-plugins]]
 === Using external_plugins (Non-bundling)
 
 When bundling is not available or you want to lazy-load plugins, use the `+external_plugins+` option:

modules/ROOT/pages/editor-theme.adoc

@@ -1,9 +1,11 @@
 = {productname} Theme options
 :navtitle: Themes
 :description: Configure the editor's theme.
+:keywords: theme, silver, theme_url
 
-WARNING: {companyname} does not recommend creating custom themes. The default `+silver+` theme provides the editor user interface components such as buttons, dialogs, and menus. To change the editor appearance, customize the skin, icons, and other user interface elements such as the toolbar.
+== Overview
 
-include::partial$configuration/theme.adoc[]
+{productname} breaks the core editor into several parts to optimize load times. The theme provides the editor UI-related logic and components such as buttons, dialogs, and menus. The currently supported theme, "Silver", is automatically loaded unless its files are missing from the core {productname} distribution or are hosted separately.
 
-include::partial$configuration/theme_url.adoc[]
+
+include::partial$configuration/theme_url.adoc[leveloffset=+1]

modules/ROOT/partials/configuration/theme.adoc

@@ -1,16 +1,36 @@
 [[theme_url]]
 == `+theme_url+`
 
-If you are using {productname} themes, this option enables you to specify the location of the theme file. This is useful if you are loading {productname} from one URL, for example a CDN, while loading a theme on, say, a local server.
+This option allows you to specify a custom location for the theme files. Use this option **only** when you need to load the theme files from a location that is not bundled with the core {productname} distribution. The current supportedtheme is called *Silver*.
 
 *Type:* `+String+`
 
-=== Example: using `+theme_url+`
+
+[NOTE]
+====
+The `+theme_url+` option should only be used in specific deployment scenarios:
+
+**CDN Loading:**
+
+When loading the theme files from a CDN or external server while {productname} core files are loaded from a different location:
+
+[source,js]
+----
+tinymce.init({
+  selector: 'textarea',
+  theme_url: 'https://cdn.example.com/tinymce/themes/silver/theme.min.js'
+});
+----
+
+**Custom Deployment Structure:**
+
+During development or when using a custom deployment structure where the theme files are in different directories:
 
 [source,js]
 ----
 tinymce.init({
-  selector: 'textarea',  // change this value according to your HTML
-  theme_url: '/mytheme/mytheme.js'
+  selector: 'textarea',
+  theme_url: '<path_to_tinymce_theme>/themes/silver/theme.min.js'
 });
 ----
+====

modules/ROOT/partials/configuration/theme_url.adoc

@@ -109,7 +109,6 @@ tinymce/
 * Custom icons packs
 * Custom plugins
 * Custom skins
-* Custom themes
 . Delete the existing `{prodnamecode}/` directory and replace with the new `{prodnamecode}/`.
 
 [NOTE]
@@ -123,5 +122,4 @@ To simplify the upgrade process to future versions of {productname}:
 * Set the location of custom icon packages using xref:editor-icons.adoc#icons_url[`+icons_url+`] instead of `+icons+`.
 * Set the location of custom localization packages using xref:ui-localization.adoc#language_url[`+language_url+`] instead of `+language+`.
 * Set the location of custom skin packages using xref:editor-skin.adoc#skin_url[`+skin_url+`] instead of `+skin+`.
-* Set the location of custom themes using xref:editor-theme.adoc#theme_url[`+theme_url+`] instead of `+theme+`.
 ====