# Core documentation

Start with Core concepts and APIs, then build your own editor.

QuireKit is a document editor framework **extending Tiptap Core**. It retains familiar `Editor`, `Extension`, `Node`, `Mark` and command-chain APIs, maintains a consistent ProseMirror runtime under the `@quirekit` scope, and adds contracts for views, layout and document formats.

## From Core to a complete product

For a Classic-like document product, follow [Build an editor product](/en/build): your first editor → document model → Canvas/SVG display → commands and interface → content extensions → product plugins → saving and files. Each chapter explains the task, demonstrates a focused change and gives you a result to try. Consult the [project reference](/en/build/reference) when you need the complete implementation.

[Editor](/en/api/editor), [extension contracts](/en/api/extensions), [View](/en/api/view) and [product API](/en/classic/api) explain arguments, results and effects by task; [Core signatures](/en/api/core) remain a supplementary reference.


## Choose your path

| Your task | Start here |
| --- | --- |
| Create an editor | [Quick start](/en/guide/quick-start) |
| Move from Tiptap | [Tiptap relationship](/en/guide/tiptap) |
| Understand data | [Documents and schemas](/en/concepts/document) |
| Load server content or restore a backup | [Content operations and validation](/en/guide/content) |
| Read caret positions or select text/nodes | [Selections and positions](/en/concepts/selection) |
| Build a capability | [Extension model](/en/concepts/extensions) |
| Add options, commands and runtime state | [Behavior extension tutorial](/en/guide/behavior) |
| Transform input or observe transaction state | [Input rules and PM plugins](/en/guide/rules) |
| Add interactive node controls | [NodeView tutorial](/en/guide/node-view) |
| Exchange content in browsers or servers | [HTML and Markdown](/en/guide/formats) |
| Look up a method | [Core API](/en/api/core) |
| Look up creation settings and callbacks | [Editor options and events](/en/api/options) |
| Try an existing plugin | [Plugin directory](/en/plugins) |
| Embed a paginated product and choose free or commercial use | [Classic documentation](/en/classic) |

## Framework and product

Core owns documents, transactions, commands and extension lifetimes. Views own presentation and input. Plugins contribute content and behavior. Classic composes these into a paginated product workspace. Core does not require Classic or the Word packages.

This sidebar covers Core concepts, APIs and the product-building tutorial. Plugins opens its integration and effects catalog; Classic opens separate product documentation for setup, configuration and licensing.

## Current release

This is an Alpha with an evolving API. Core and common extensions use MIT; view, product and Word packages have separate licenses and distribution channels. See [support and licensing](/en/support).