@soeditor/editor

Lightweight CMS HTML WYSIWYG distribution for SoEditor. Modern applications mount the Classic Editor through the narrow /cms entry. The direct browser build exposes the WYSIWYG-only CMS API through globalThis.SoEditor.

import { createClassicEditor } from '@soeditor/editor/cms/optional';
import '@soeditor/editor/cms/styles.css';

const editor = await createClassicEditor(
    document.querySelector<HTMLTextAreaElement>('#content')!,
    {
        editingModes: ['wysiwyg', 'source'],
        initialEditingMode: 'wysiwyg',
        placeholder: 'Write article content',
        minHeight: 240,
        toolbarLayout: { collapsible: true, sticky: true },
    },
);

Use @soeditor/editor/cms for the smaller WYSIWYG-only default. The explicit /cms/optional entry is required when Source, Preview or a save adapter is configured; the standalone browser global also remains WYSIWYG-only.

When the host is a named textarea, its value follows canonical HTML and is updated before native form submission. Form reset restores the textarea's default value through the editor transaction path. destroy() removes owned surfaces and restores the original host visibility. The classic chrome includes bounded manual height resizing, optional maximize, responsive toolbar behavior, element path, text counts, dirty status, and command-backed contextual actions. The status bar is placed below the editing surface. Optional Classic integrations may add showBlocks to the toolbar for projection-only block boundaries and HTML tag labels. Call editor.maximize(false) or destroy the editor to restore document overflow exactly.

For saved content on the frontend, import @soeditor/editor/content.css and wrap the HTML in .soeditor-content. This stylesheet shares the editor's image alignment rules without loading editor JavaScript or chrome styles. See statistics, frontend styles and corpus measurements for the text-counting contract and integration checks.

An optional save configuration adds a command-backed Save/Retry control, opaque revision tokens, progress/conflict state, opt-in bounded autosave, and coordinated leave-page protection. The host-provided adapter remains responsible for transport and backend policy. See docs/cms-saving.md. CMS plugins, instance-scoped themes, and plain-text icon replacement are documented in docs/cms-plugin-ecosystem.md.

Historical lower-level assembly remains available from the compatibility root:

import { SoEditor, minimalPreset } from '@soeditor/editor';
import '@soeditor/editor/cms/styles.css';

const editor = await SoEditor.create({
    data: '<p>Hello</p>',
    format: minimalPreset.format,
    plugins: minimalPreset.plugins,
});

The package root retains released 1.0 compatibility exports. They are excluded from the /cms entry and standalone CMS global and receive compatibility fixes, not active product development.