Skip to content

Commit bbc608e

Browse files
committed
Docs: DOC-3408 - Clarify that both bundling and lazy loading are fully supported
1 parent 89557f9 commit bbc608e

2 files changed

Lines changed: 11 additions & 6 deletions

File tree

modules/ROOT/pages/bundling-plugins.adoc

Lines changed: 10 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -88,7 +88,12 @@ require('<path_to_tinymce_premium_zip>/plugins/<plugincode>');
8888
[[using-premium-plugins]]
8989
== Using premium plugins
9090

91-
After installing the `+tinymce-premium+` package, you need to configure the plugins in your editor. There are two main approaches:
91+
After installing the `+tinymce-premium+` package, configure the plugins in the editor using one of two fully supported approaches. Both options are production-ready and will continue to be supported in future releases:
92+
93+
* **<<bundling-recommended,Bundling>>** -- includes plugin code directly in the application bundle using a module bundler
94+
* **<<using-external-plugins,Loading with `+external_plugins+`>>** -- loads plugins at runtime from a specified URL, enabling lazy-loading and CDN hosting
95+
96+
The right choice depends on the application architecture and deployment requirements.
9297

9398
[IMPORTANT]
9499
====
@@ -112,9 +117,9 @@ external_plugins: {
112117
====
113118

114119
[[bundling-recommended]]
115-
=== Bundling (Recommended)
120+
=== Bundling
116121

117-
For most modern applications, bundling premium plugins is recommended. This includes the plugin code directly in your application bundle.
122+
Bundling includes the plugin code directly in the application bundle. This approach works well for applications that already use a module bundler such as Webpack, Vite, or Rollup.
118123

119124
. Import the premium plugins you need:
120125
+
@@ -141,9 +146,9 @@ tinymce.init({
141146
For complete bundling examples, see the <<premium-plugins,Premium plugins>> and <<community-plugins,Community plugins>> sections below.
142147

143148
[[using-external-plugins]]
144-
=== Using external_plugins (Non-bundling)
149+
=== Loading with external_plugins
145150

146-
When bundling is not available or you want to lazy-load plugins, use the `+external_plugins+` option:
151+
The `+external_plugins+` option loads plugins at runtime from a specified URL. This approach enables lazy-loading, allows serving {productname} assets from a CDN or separate host, and avoids adding editor code to the application bundle. {cloudname} uses this same mechanism to load the editor.
147152

148153
[source,js]
149154
----

modules/ROOT/pages/license-key.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -74,7 +74,7 @@ tinymce.init({
7474
====
7575
* The `+licensekeymanager+` plugin is included in the `+tinymce-premium+` package.
7676
* The `+tinymce-premium+` package version must match the `+tinymce+` package version (e.g., both at 8.3.0).
77-
* The `+external_plugins+` option allows loading the license key manager from any location, useful when bundling is not available or when lazy-loading plugins. For more information, see: xref:editor-important-options.adoc#external_plugins[`+external_plugins+` configuration option].
77+
* The `+external_plugins+` option allows loading the license key manager from any location, such as a CDN or separate host. For more information, see: xref:editor-important-options.adoc#external_plugins[`+external_plugins+` configuration option].
7878
====
7979

8080
== License Types and Deployment Options

0 commit comments

Comments
 (0)