Skip to content

DOC-3367: Add new bundling guide overview page.#3983

Open
kemister85 wants to merge 4 commits intotinymce/8from
hotfix/8/DOC-3367
Open

DOC-3367: Add new bundling guide overview page.#3983
kemister85 wants to merge 4 commits intotinymce/8from
hotfix/8/DOC-3367

Conversation

@kemister85
Copy link
Contributor

@kemister85 kemister85 commented Feb 12, 2026

Ticket: DOC-3367

Site: New: Bundling guide (page)

Summary

Adds a new bundling overview guide and improves bundling documentation consistency across the codebase.

Changes

New Files

  • modules/ROOT/pages/bundling-guide.adoc - New bundling overview page providing:
    • Overview of bundling TinyMCE with module bundlers (Webpack, Vite, Rollup, Browserify)
    • Required imports (TinyMCE core, silver theme, dom model, default icons, skins, content CSS)
    • Plugin import syntax for community and premium plugins
    • Plugin gotchas (plugins requiring additional resources, plugin dependencies)
    • CSS files information
    • Language files information
    • Links to all related bundling reference pages
  • 60 plugin feature pages - Added include::partial$misc/bundling-guide-link.adoc[] to all core and premium plugins.

Pre-checks:

  • Branch prefixed with feature/<version>/, hotfix/<version>/, staging/<version>/, or release/<version>/.
  • modules/ROOT/nav.adoc has been updated (if applicable).

Review:

  • Documentation Team Lead has reviewed

@kemister85 kemister85 requested review from a team, jscasca, kimwoodfield, metricjs, soritaheng and tiny-ben-tran and removed request for a team February 12, 2026 00:13
@kemister85 kemister85 marked this pull request as ready for review February 12, 2026 00:13
@kemister85 kemister85 requested a review from a team as a code owner February 12, 2026 00:13
kemister85 and others added 2 commits March 2, 2026 13:11
Co-authored-by: Sorita Heng <69398037+soritaheng@users.noreply.github.com>
Co-authored-by: Sorita Heng <69398037+soritaheng@users.noreply.github.com>

== Required imports

include::partial$module-loading/bundling-required-components.adoc[]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can't find the file, but there's a line that repeats itself:

A custom or premium icon pack to extend or override the default icons for toolbar buttons, including contextual toolbars. This can be a premium or custom icon pack.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We do call it out super well further down, so it's a nitpick

import 'tinymce/skins/ui/oxide/content.js';

/* Content CSS for editor content styling */
import 'tinymce/skins/content/default/content.js';
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Said in the section above that this isn't required, then put it in an example of required imports?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we could say 'recommended imports' instead?


Most plugins can be imported directly using their plugin code. The import path depends on whether the plugin is a community or premium plugin:

=== Community plugins
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do wonder if it's worth mentioning somewhere in this page that we've mostly (entirely?) talking about pulling files from NPM? Like, it's implied but also... The premium example in particular won't make sense if you're thinking of using a bundle or something.


Both syntaxes are supported, but this documentation uses ES6 module syntax in all examples.

== Required imports
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we be listing the license key manager in here actually? It's only required if using a premium plugin, but. Still a requirement?


* The `+advtable+` plugin requires the `+table+` plugin

Always import dependent plugins before the plugin that requires them.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should probably mention where else to find this info, since we've framed this as an example and not a full list. Should advise to check the plugin's page I guess?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants