@editora/plugins

Installation

npm i @editora/plugins @editora/core

import "@editora/plugins/styles.css";

Quick Start

Import and register only required plugins.

Usage

Plugins expose commands, toolbar wiring, and optional dialogs/sidebars.

Use:

• @editora/plugins for the full catalog
• @editora/plugins/lite for common/core plugins
• @editora/plugins/enterprise for advanced/specialized plugins
• @editora/plugins/<plugin-name> for per-plugin imports

All entry paths are free and fully customizable.

Enterprise Subset Includes

• MentionPlugin, TrackChangesPlugin, VersionDiffPlugin, ConditionalContentPlugin, DataBindingPlugin
• ContentRulesPlugin, CitationsPlugin, ApprovalWorkflowPlugin, PIIRedactionPlugin, SmartPastePlugin
• BlocksLibraryPlugin, DocSchemaPlugin, TranslationWorkflowPlugin, SlashCommandsPlugin
• SpellCheckPlugin, A11yCheckerPlugin, CommentsPlugin, MergeTagPlugin, TemplatePlugin
• MediaManagerPlugin, DocumentManagerPlugin

Examples

• Basic formatting set
• Media and table workflow set
• Collaboration and QA plugin set

API Reference

Each plugin exposes a factory and command definitions with optional config options.

Also available: @editora/plugins/styles.css for plugin UI styling (table toolbar, dialogs, color pickers).

Best Practices

• Keep plugin list minimal per editor context.
• Validate cross-plugin behavior with history/undo.
• Ensure command names are unique and stable.

Accessibility

Dialogs, menus, and panels should remain keyboard-operable and readable across themes.

Performance Notes

Avoid loading heavy optional plugins in baseline flows; split by use case where possible. Prefer subpath imports, @editora/plugins/lite, or @editora/plugins/enterprise for baseline bundle control.