Product plugins
Compose Classic file services, professional capabilities and interface plugins, or build your own product features.
Classic product plugins are installed through the instance's plugins option and compose ribbons, menus, sidebars and file services. Ordinary Core extensions go in extensions and own document structure and behavior. These contracts are distinct. See the plugin catalog for ordinary integrations and effects.
Compose product capabilities
| Capability | Product packages | Boundary |
|---|---|---|
| Word preset and DOCX | @quirekit/classic-docx | The preset assembles content capabilities; the DOCX plugin registers file services |
| Review and forms | @quirekit/classic-pro | Install professional interfaces and confirm the product line separately |
| AI | @quirekit/classic-ai | Classic-specific wiring; the host supplies required AI services |
| PDF / OFD | @quirekit/classic-pdf, @quirekit/classic-ofd | Install export adapters and confirm export coverage |
| Business features | Custom ClassicEditorPlugin | Declare product actions, surfaces and services; Core commands still mutate content |
Configuration by entry point
| Entry | Installation | Reference |
|---|---|---|
| Community and professional Word presets | preset | Community, professional |
| Word file services | plugins | DOCX / DOTX |
| Fixed-layout export | plugins | PDF and printing, OFD |
| AI | plugins | Complete assembly, workspace assembly, host sidebar port |
| Document templates | plugins | Catalog and document creation |
| Graphics and data | extensions | Flowchart, mind map, whiteboard, text diagram, data view |
Graphic/data adapters remain Core Extensions with additional Classic controls. Each reference lists its host ports and defaults. See all plugins for the full catalog.
Licensing a package does not install it. A preset's resolveExtensions() array does not include the complete product registry. Mount the complete product through Classic rather than claiming file menus and license feedback are installed from the extension array alone.
Live development example
This reuses the verified product plugin: a ribbon group, product inspector, content insertion action and JSON backup service. Open the inspector, edit content and download its current backup. The source includes every local dependency.
Plugin and contribution IDs remain unique within the instance. Availability checks read facts; document actions call Core commands. Panels manage resources through mount, update and disposal.
Follow the implementation tutorial and Classic API. This example does not install Pro, AI or export packages. See commercial use for product-line choices.