# Word capabilities and product assembly

Choose Word document capabilities above Core and understand the product UI boundary.

The complete Word product uses the Classic Word preset. Block reuses tables and numbering through separate adapters; this does not imply support for all Word capabilities. See [per-plugin status and integration rules](/en/plugins/compatibility).

Word packages own semantics for paragraphs, sections, lists, tables, fields, stories and drawings. `@quirekit/classic-docx` combines these with Classic product UI. Word, DOCX and Pro packages currently use commercial distribution, separate from Core's MIT license.

## Assembly layers

| Layer | Responsibility |
| --- | --- |
| Core / ordinary extensions | Documents, transactions and shared commands |
| Word domain packages | Canonical content, formatting, commands and conversion |
| Classic Word preset | Integrates Word capabilities into the paginated product |
| DOCX plugin | Registers file import and export services |
| Classic Pro | Optional review, content-control and form-protection UI |

## Example

```ts
import { createClassicEditor } from '@quirekit/classic-editor'
import {
  createClassicWordPreset,
  createClassicWordDefaultDocument,
  createClassicWordDocxPlugin,
} from '@quirekit/classic-docx'

const editor = createClassicEditor({
  element: document.querySelector('#editor'),
  preset: createClassicWordPreset(),
  document: createClassicWordDefaultDocument('en'),
  plugins: [createClassicWordDocxPlugin()],
})
```

Obtain commercial packages through their distribution channel first. Vue applications use the matching `/vue` entries. [Classic integration and live effects](/en/classic/quick-start) runs the official preset and publishes the complete host source, avoiding duplicate product assembly across pages.

## Support boundaries

Preserving source objects, importing, editing and lossless export are different capabilities. Inspect conversion diagnostics: missing fonts, resources or unsupported fields may affect the result. PDF/OFD, AI and collaboration require separate assembly. This page does not promise complete Microsoft Word compatibility.