DOC-3329: Add mention of lazy loading extra resources, and how to handle language pack imports per plugin.

Author: kemister85

modules/ROOT/pages/bundling-icons.adoc

@@ -88,6 +88,8 @@ import 'tinymce-premium/icons/material';
 ----
 * After bundling, set `+icons: 'material'+` (or any imported icon pack) in the editor configuration.
 
+=== Non-bundling methods
+
 *Non-bundling with file layering*
 
 * When hosting directly from `+node_modules+`, copy `+node_modules/tinymce-premium/icons/+` into `+node_modules/tinymce/icons/+` as part of the build or deployment step (for example, in a `+postinstall+` script).

modules/ROOT/pages/bundling-plugins.adoc

@@ -174,4 +174,55 @@ For more information, see: xref:editor-important-options.adoc#external_plugins[`
 
 include::partial$module-loading/bundling-plugin-files.adoc[]
 
+[[plugin-language-files-bundling]]
+=== Bundling plugin language files
+
+Plugin language files are separate from the main {productname} UI language files. Each plugin has its own language files located in `+plugins/<plugincode>/langs/+`.
+
+* **Core UI language files**: Located in `+langs/+` (e.g., `+tinymce-premium/langs/ar.js+`)
+* **Premium plugin language files**: Located in `+plugins/<plugincode>/langs/+` (e.g., `+tinymce-premium/plugins/advcode/langs/ar.js+`)
+
+To bundle premium plugin language files, import them using the same module syntax as bundling plugins, but append `+/langs/<language>.js+` to the import path:
+
+[source, js]
+----
+// Import the plugin
+import 'tinymce-premium/plugins/advcode';
+// Import the premium plugin's Arabic language file
+import 'tinymce-premium/plugins/advcode/langs/ar.js';
+// Import the main UI Arabic language file (if needed)
+import 'tinymce-premium/langs/ar.js';
+
+tinymce.init({
+  selector: 'textarea',
+  language: 'ar',
+  plugins: 'advcode',
+  // ... other configuration
+});
+----
+
+[NOTE]
+====
+For premium plugins from `+tinymce-premium+`, the language file path must include the `.js` extension.
+====
+
+[[plugin-lazy-loading]]
+=== Plugin lazy-loading and additional resources
+
+[IMPORTANT]
+====
+Plugins lazy-load additional resources (JS and CSS files) at runtime for optimal performance. These resources must be:
+
+* **Included in the bundle** along with the plugin (recommended for bundled applications)
+* **Placed as static assets** in the expected location (for non-bundled deployments)
+
+Missing resources may cause plugins to fail or display errors.
+====
+
+When bundling, explicitly import any additional resources that plugins require. The module bundler includes these files in the application bundle, making them available at runtime.
+
+For non-bundled deployments using `+external_plugins+`, ensure all required resource files (CSS, JS, and language files) are accessible at the expected paths relative to the plugin file location.
+
+See <<plugin-resources,Additional plugin resources>> for specific examples of plugins that require additional resources.
+
 include::partial$module-loading/bundling-plugin-resources.adoc[]

modules/ROOT/partials/module-loading/bundling-plugin-files.adoc

@@ -1,9 +1,6 @@
 [[premium-plugins]]
 === Premium plugins
 
-
-Premium plugins are available via the `+tinymce-premium+` NPM package (recommended) or from ZIP downloads. The NPM package is the recommended method for easier installation and upgrades.
-
 include::partial$plugin-files/plugin-file-bundling-message.adoc[]
 
 include::partial$module-loading/bundling-premium-plugins-npm.adoc[]

modules/ROOT/partials/module-loading/bundling-premium-plugins-npm.adoc

@@ -1,5 +1,3 @@
-=== Premium plugins from NPM
-
 The `+tinymce-premium+` package is the recommended way to install and use premium plugins with {productname}. It includes all premium plugins, skins, icons, and language packs.
 
 To bundle premium plugins from the NPM package, import the individual plugins you need.