Skip to content

Commit 66f2c51

Browse files
authored
docs: reframe nav around Editor umbrella + Document Engine (SD-2873) (#3047)
* docs: reframe nav around Editor umbrella + Document Engine (SD-2873) Group SuperDoc, React, Custom UI, Built-in UI, and Collaboration under a single Editor umbrella so the top-level nav reads as Editor / Document Engine / everything else. Custom UI is the recommended way to drive the editor in new React apps; Built-in UI stays supported. URLs unchanged in this commit; folder/path migration follows separately. * docs: migrate URLs to new IA with redirects (SD-2873) (#3049) * docs: migrate URLs under /editor/* with redirects (SD-2873) Move pages so the URL structure matches the Editor umbrella: core/superdoc to editor/superdoc, core/react to editor/react, bring-your-own-ui to editor/custom-ui, modules to editor/built-in-ui, modules/collaboration to editor/collaboration. Move SuperEditor and extension authoring under advanced/. Add redirects (specific before broad) so prior links keep working. Sweep cross-references across mdx, llms.txt, and llms-full.txt. * fix(docs): order legacy redirects before new wildcards (SD-2873) Hoist /modules/collaboration/{backend,client,cloud,self-hosted}/*, /core/superdoc/{properties,types}, and /core/supereditor/hooks above the new /modules/collaboration/:path*, /core/superdoc/:path*, and /core/supereditor/:path* wildcards so legacy deep links keep hitting their intended pages instead of being rewritten into nonexistent paths. * docs: tighten Built-in UI nav and hide custom extensions (SD-2873) - Flatten Built-in UI > Toolbar (drop the Built-in vs BYO vs Headless comparison page; the comparison no longer fits since BYO and Headless live elsewhere). Toolbar is now a single page. - Rename Built-in UI > Track changes module to Track changes. - Rename Built-in UI > Links to Link popover (the page is about popoverResolver, not link insertion). - Hide /advanced/custom-extensions from nav (file kept, hidden frontmatter) while we plan the v2 editor surface. - Add redirects so /modules/toolbar/{built-in,overview} and /editor/built-in-ui/toolbar/{built-in,overview} all land on the flattened toolbar page. * docs: move PDF + Whiteboard out of Built-in UI into their own group (SD-2873) PDF is a separate document type (pdf.js rendering pipeline) and Whiteboard is an annotation layer that only applies to PDFs. Neither is ready-made UI on top of the DOCX editor, so they don't fit the Built-in UI category. Group them under Editor > PDF (sibling of Built-in UI, Collaboration, etc.) so they stay close to the SuperDoc browser surface (still configured via modules.pdf / modules.whiteboard) without polluting the Built-in UI category. Add redirects so /modules/{pdf,whiteboard} and the previous /editor/built-in-ui/{pdf,whiteboard} land on the new paths. * docs: drop Advanced from nav and hide its pages (SD-2873) The Advanced group was turning into a junk drawer of paths we're walking away from in v2 of the editor. Hide all of them from nav while keeping the files reachable by direct URL for existing inbound links: - SuperEditor (4 pages): the Document API on SuperDoc covers the headless story now (editor.doc.* gives full programmatic access without instantiating SuperEditor directly). - Headless toolbar + examples: superdoc/ui will eventually offer full toolbar control across frameworks (tracked in SD-2874); hiding now so we don't teach the deprecated path. Existing redirects keep old URLs working; the pages just don't appear in the sidebar. * docs: dissolve Guides into feature homes (SD-2873) Top-level Guides was a junk drawer mixing product surfaces, migration docs, and internal contributor material. Move every page to where the feature actually lives so each section reads as one coherent topic. Editor: - Collaboration > Storage (was Guides > Storage) - Custom UI > Navigation (was Guides > Stable navigation) - Proofing > Overview, Custom provider (was Guides > Proofing) - Theming > Custom themes, CSS variable migration (was Guides + Migration) Document API: - Migration (was Guides > Migration > Document API) Resources: - Upgrade guides > Breaking changes v1, Migrate from ProseMirror Hidden: - TypeScript migration (internal contributor doc, not consumer-facing) Drop the entire Guides nav group. Add redirects so every old /guides/* URL resolves to its new home. Sweep cross-references. Also fix the accessibility page: the docs referenced superdoc.isHighContrastMode (no such public property); replace with the real setHighContrastMode(value) method. * fix(docs): collapse redirect chains and fix broken targets (SD-2873) - /resources/storage now points directly at /editor/collaboration/storage (was pointing at the old /guides/general/storage which we just moved). - /resources/guides points at /getting-started/introduction (the old generic guides landing page no longer exists). - /api-reference/documents/sign points at /solutions/esign/api-reference (the previous target /api-reference/signature/sign was never built). - /guide/integration jumps directly to /getting-started/quickstart instead of chaining through /getting-started/installation. - /getting-started/ai-ready jumps directly to /ai/agents/llm-tools instead of chaining through /getting-started/ai-agents. Audit: 73 redirects total, 0 chains, 0 broken destinations, ordering is specific-before-broad. * docs: rewrite Getting Started FAQ pages and add deep homes (SD-2873) Getting Started has four entries that exist for FAQ/discoverability (Import/Export, Font Support, Theming, AI). Two were broken JS-redirect stubs and two were oversized API references. Reshape each as a tight 'first-week setup' page with a clear deep-dive link. - Import and export: keep tight workflow page in Getting Started; move the full reference to Editor > SuperDoc > Import/Export. - Theming: keep 5-minute setup in Getting Started; move the full overview to Editor > Theming > Overview. - Font support: replace JS-redirect stub with a real practical guide (the canonical fonts doc — no other home for it). - AI: replace JS-redirect stub with a chooser page that points at MCP, agent tools, CLI/SDK, and import/export based on use case. Sweep stale links: - Introduction cards: Installation -> Quick start, AI Agents -> AI. - Quickstart: /document-engine/ai-agents/{mcp-server,llm-tools} -> /ai/{mcp/overview, agents/llm-tools}. - apps/create/src/templates.ts AGENTS.md generator: update old /core/superdoc/configuration and /document-engine/ai-agents/* paths so newly scaffolded projects ship correct docs links. * docs: tighten Getting Started FAQ pages with correct API usage (SD-2873) - Theming: createTheme returns a className applied via document.documentElement.classList.add, not a constructor option. Adds popover/CSP pitfalls. - Fonts: modules.toolbar.fonts takes [{ label, key }] objects, not bare strings. Adds dropdown-not-auto-populated pitfall. - AI: chooser table + three concrete paths with real install command. - Import/Export: leads with value statement; adds duplicate-download/HTML-base-DOCX pitfalls. * docs: rewrite Quick start as linear Install → Render → Load → Export → Next (SD-2873) The previous quickstart (269 lines) opened with a Mermaid decision tree and split into three parallel sections (AI agent, backend SDK, browser editor). It worked as a map but front-loaded too much surface area before the reader had written any code. New shape is a single linear path for the most common audience (someone embedding the DOCX editor in a web app): 1. Install (npm / React / CDN tabs) 2. Render the editor (JS / React tabs) 3. Load a document (URL / File input / Fetch tabs) 4. Export it (Download / Upload tabs) 5. What are you building? table — routes to Custom UI, Built-in UI, Document Engine, AI, Collaboration based on the goal AI agents get an Info callout near the top with the npx @superdoc-dev/create one-liner — visible but out of the main flow. SDK/CLI moves to the routing table; agents and backend code aren't the primary quickstart audience. Result: ~140 lines, single read path, decision lives at the bottom once the reader has a working editor. * docs: rewrite Getting Started AI page as a chooser + expectations page (SD-2873) The previous version used a CardGroup with marketing copy. Replace with structured prose that answers the questions someone searching 'SuperDoc AI' actually has: - What is the data boundary (no LLM bundled, nothing auto-uploaded) - Pick-your-path table (MCP / SDK / browser editor) - What AI can control (concrete operation list) - Three short path sections with real install commands and code - Common patterns table (clause drafting, redlines, comments, etc.) - 'What SuperDoc does not do' to set expectations Quick start AI callout now points at /getting-started/ai (the path picker) instead of jumping straight to /ai/mcp/overview. * docs: rewrite Document Engine overview as a calm pillar landing (SD-2873) The previous page listed MCP as a peer surface alongside Document API, SDKs, and CLI, which blurred the line between Document Engine and AI in the new IA. Reframe as 'the programmatic layer for .docx files' and move MCP routing out to the AI section. - Open with a clear definition and the three places Document Engine shows up (editor, SDKs, CLI). Don't say 'without a visible editor' - Document API in the browser usually exists alongside an open editor. - AI callout near the top routes to /getting-started/ai (the chooser), not /ai/overview directly, so AI users get the path picker. - Surfaces table is now three rows (no MCP). 'Best for' framing is about programmatic role, not just runtime. - Add 'How it works' section explaining that Document API is the operation contract and the surfaces are different ways to call it. - 'Which surface should I use?' table includes Custom UI, serverless, and AI as routes - reflects how customers actually arrive here. - Drop the Mermaid diagram (added ceremony, not clarity). * fix(docs): replace Font Awesome icons with valid Lucide names (SD-2873) docs.json sets icons.library to lucide, but several pages used Font Awesome / brand icon names that silently rendered as blank boxes. Renames: - arrow-up-right-from-square -> external-link - screwdriver-wrench -> wrench - compass-drafting -> compass - gear (4 framework pages) -> cog - crosshairs -> crosshair - arrow-right-arrow-left -> arrow-left-right - file-export -> file-output - react/vuejs/js (no Lucide equivalents) -> code - google/microsoft (no Lucide brand icons) -> book/file-text Add an Icons section to apps/docs/AGENTS.md (and its CLAUDE.md symlink) so future agents know: - Mintlify only resolves icon names against the configured library - Verify names against lucide.dev/icons before using - Common Font Awesome -> Lucide name traps - Brand icons need SVG paths since Lucide doesn't ship them * feat(docs): add Lucide icon validator + tighten icon picks (SD-2873) Add scripts/validate-icons.ts that walks every <Card icon=...>, <Icon icon=...>, and docs.json icon reference and validates the name against the locally installed Lucide icon set. Wire into lefthook pre-commit so invalid icons fail the commit instead of silently rendering as blank boxes in production. The validator caught two more icons missed in the previous pass: - cube -> box - unlock -> lock-open Tighten icon picks per code-review feedback: - React-related cards: code -> atom - Vue card: code -> blocks - Vanilla JS card: code -> braces - Comments card (Custom UI overview): message -> message-square - Discord references in docs.json (contextual + navbar): discord -> messages-square (Lucide ships no brand icons) Add a follow-up note in apps/docs/AGENTS.md so future agents know about pnpm run check:icons. * docs: pull diffing out of SDKs and reframe as Document Engine workflow (SD-2873) The page was nested under 'SDKs > SDK Diffing' but the underlying operations (diff.capture, diff.compare, diff.apply) are canonical Document API operations, not SDK-specific. Promote diffing to a sibling of SDKs and CLI under Document Engine. - Move document-engine/sdk-diffing.mdx to document-engine/diffing.mdx. - Rename title from 'SDK Diffing' to 'Compare documents' (sidebar stays 'Diffing'). Reframe the opener: diffing is a Document Engine workflow; the examples use SDKs because file-to-file comparison usually runs in backend automation, but the feature isn't SDK-owned. - Update Document Engine nav: SDKs becomes a flat page (no sub-group), Diffing becomes a sibling alongside SDKs and CLI. - Add redirect /document-engine/sdk-diffing -> /document-engine/diffing. - Sweep cross-references and update the SDK overview's link to point at the new path with the new framing. * fix(docs): final pass correctness fixes (SD-2873) - Drop /getting-started/ai redirect: a real Getting Started AI page now exists at that URL; the old redirect was sending it elsewhere. - Fix editor.doc.insert snippet on the Getting Started AI page: the real shape is { target, value, type: 'html' }, not { target, html }. - Document Engine overview was wrong about the CLI: it runs in persistent sessions (open/run/save/close), not one-shot commands. - Add Diffing as a fourth Where-to-next card on Document Engine overview. It's a sibling of Document API/SDKs/CLI, not nested. - Drop CLI Skills from the AI overview path-picker. Skills are not shipped yet (the page itself says so). Promoting them in the primary path table is misleading; keep the page reachable but don't route new users there. * docs: brand voice + terminology sweep, hide legacy AI pages, rename Custom UI demo (SD-2873) Final pass over the docs surface to align with brand.md voice and the new IA terminology. Terminology: - 'Bring Your Own UI' / 'BYO UI' to 'Custom UI' across 12+ mdx files, llms.txt, llms-full.txt, code comments in packages/super-editor and packages/superdoc. - Rename the Custom UI demo: demos/bring-your-own-ui to demos/custom-ui. Update package.json name, playwright port mapping key, README, and GitHub URL references in mdx. Brand voice: - Em-dash sweep across hand-written mdx (skip auto-generated files under document-api/reference and the gen:docs marker block in document-engine/sdks.mdx). 'X — Y' becomes 'X. Y' or 'X (Y)' or 'X: Y' depending on context. - Wrap frontmatter description values that contain colons in double quotes so YAML parses correctly (caught by mintlify validate). - Touch up grammatical regressions where the colon substitution read worse than the em-dash (theming.mdx, document-engine/overview.mdx, getting-started/{ai,import-export}.mdx). Legacy hides (kept reachable for inbound links, removed from search): - document-engine/ai-agents/* (7 pages) and getting-started/ai-agents.mdx add hidden: true frontmatter. Redirects already point /ai/* and /getting-started/ai at the new homes; this stops the old pages from surfacing in search results. Notes: - Auto-generated content (Document API reference, sdks.mdx marker block) still has em-dashes. Filing a follow-up for the generator. - demos/custom-ui/ folder renamed cleanly (no backward-compat shim per direction). Old GitHub URLs that pointed at demos/bring-your-own-ui will 404; trade-off accepted. * fix(ci): finish bring-your-own-ui to custom-ui rename (SD-2873) The demo rename missed the CI matrix, the Playwright port map, and the README filter command. Smoke test failed because the cached workspace had no demos/bring-your-own-ui, so Playwright's webServer fell back to a pnpm command on a runner with no pnpm installed.
1 parent 957c6aa commit 66f2c51

129 files changed

Lines changed: 1753 additions & 1391 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

.github/workflows/ci-demos.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ jobs:
3333
run: pnpm build:superdoc
3434

3535
- name: Build @superdoc-dev/react
36-
# bring-your-own-ui imports the React wrapper from its dist/.
36+
# custom-ui imports the React wrapper from its dist/.
3737
# Other demos don't need this; cheap enough to run unconditionally.
3838
run: pnpm --filter @superdoc-dev/react run build
3939

@@ -56,7 +56,7 @@ jobs:
5656
fail-fast: false
5757
matrix:
5858
demo:
59-
- bring-your-own-ui
59+
- custom-ui
6060
- cdn
6161
- custom-mark
6262
- custom-node

apps/create/src/templates.ts

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -176,7 +176,7 @@ Key options for the editor:
176176
| \`modules.comments\` | \`object\` | Comments panel configuration |
177177
| \`modules.collaboration\` | \`object\` | Real-time collaboration (Yjs) |
178178
179-
Full config: https://docs.superdoc.dev/core/superdoc/configuration
179+
Full config: https://docs.superdoc.dev/editor/superdoc/configuration
180180
181181
## Theming
182182
@@ -256,7 +256,7 @@ superdoc save && superdoc close
256256
- Quickstart: https://docs.superdoc.dev/getting-started/quickstart
257257
- React guide: https://docs.superdoc.dev/getting-started/frameworks/react
258258
- Document Engine: https://docs.superdoc.dev/document-engine/overview
259-
- MCP server: https://docs.superdoc.dev/document-engine/ai-agents/mcp-server
259+
- MCP server: https://docs.superdoc.dev/ai/mcp/overview
260260
- Examples: https://github.com/superdoc-dev/superdoc/tree/main/examples
261261
`;
262262
}

apps/docs/AGENTS.md

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -171,6 +171,29 @@ const superdoc = new SuperDoc({
171171

172172
**When NOT to use CodeGroup:** Snippets that are already complete (have imports + initialization), config-only blocks, bash commands, XML/HTML examples.
173173

174+
## Icons
175+
176+
`docs.json` sets `"icons": { "library": "lucide" }`. Mintlify resolves every `icon="..."` value (in `<Card>`, `<CardGroup>`, `<Icon>`, etc.) against **Lucide only** — there is no per-icon library override. Names from Font Awesome, Material Design, Tabler, or brand icon sets silently render as a blank box.
177+
178+
**Rule of thumb:** before adding an icon, check the name exists at https://lucide.dev/icons/. If it doesn't, pick a Lucide alternative or use a custom SVG path.
179+
180+
Common name traps when migrating from Font Awesome:
181+
182+
| Don't use (FA only) | Use this (Lucide) |
183+
|---|---|
184+
| `gear` | `cog` or `settings` |
185+
| `crosshairs` | `crosshair` (singular) |
186+
| `compass-drafting` | `compass` |
187+
| `screwdriver-wrench` | `wrench` |
188+
| `arrow-up-right-from-square` | `external-link` or `square-arrow-out-up-right` |
189+
| `arrow-right-arrow-left` | `arrow-left-right` |
190+
| `file-export` | `file-output` or `download` |
191+
| `react`, `vuejs`, `js`, `microsoft`, `google` | No Lucide brand icons — pick a generic (`code`, `book`, `file-text`) or use an SVG path |
192+
193+
For brand/language icons (React, Vue.js, Microsoft, etc.), Lucide doesn't ship them. Either use a generic Lucide icon that fits the context, or supply an SVG via `icon="/path/to/icon.svg"` or an external URL.
194+
195+
A `pnpm run check:icons` validator runs in pre-commit and walks every `<Card icon="...">`, `<Icon icon="...">`, and `docs.json` icon reference against the locally installed Lucide set. Catches drift before deploy. Add new icons through this validator — if it complains, the name isn't in the Lucide library.
196+
174197
## Testing
175198

176199
Code examples are tested automatically via pre-commit hooks and CI. Two checks run when `.mdx` files change:

apps/docs/extensions/creating-extensions.mdx renamed to apps/docs/advanced/custom-extensions.mdx

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,13 @@
11
---
2+
title: Custom extensions
3+
sidebarTitle: Custom extensions
24
hidden: true
3-
title: Creating Extensions
4-
sidebarTitle: Create Your Own
55
---
66

7+
<Note>
8+
Custom extensions are an advanced surface. For most app-level customization, the [Document API](/document-api/overview) handles document mutations and [Custom UI](/editor/custom-ui/overview) handles toolbar, comments, and review panels — both are stable, framework-friendly, and aligned with SuperDoc's document model. Reach for custom extensions only when you need editor internals (custom marks, nodes, or chain commands).
9+
</Note>
10+
711
Create extensions to add custom features to SuperDoc.
812

913
## Basic extension

apps/docs/modules/toolbar/examples.mdx renamed to apps/docs/advanced/headless-toolbar-examples.mdx

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,14 @@
11
---
22
title: Headless Toolbar Examples
3+
hidden: true
34
sidebarTitle: Examples
45
keywords: "toolbar examples, vue toolbar, svelte toolbar, custom toolbar examples"
56
---
67

78
Framework-agnostic patterns built on `createHeadlessToolbar()`. Pick the one closest to your stack.
89

910
<Note>
10-
**On React?** Reach for [Bring Your Own UI › Toolbar and commands](/bring-your-own-ui/toolbar-and-commands) instead. The typed React surface (`useSuperDocCommand`, `ui.commands.register`) re-renders one button per command, ships with selection / comments / track-changes hooks, and works with any design system (shadcn, MUI, Mantine, Tailwind). The headless examples below are for non-React stacks.
11+
**On React?** Reach for [Custom UI › Toolbar and commands](/editor/custom-ui/toolbar-and-commands) instead. The typed React surface (`useSuperDocCommand`, `ui.commands.register`) re-renders one button per command, ships with selection / comments / track-changes hooks, and works with any design system (shadcn, MUI, Mantine, Tailwind). The headless examples below are for non-React stacks.
1112
</Note>
1213

1314
## Vue + Vuetify
@@ -140,10 +141,10 @@ Replace `<example-name>` with `vue-vuetify`, `svelte-shadcn`, or `vanilla`.
140141
## Next steps
141142

142143
<CardGroup cols={2}>
143-
<Card title="Bring Your Own UI (React)" icon="react" href="/bring-your-own-ui/toolbar-and-commands">
144+
<Card title="Custom UI (React)" icon="atom" href="/editor/custom-ui/toolbar-and-commands">
144145
The recommended path for React apps. Typed hooks, custom commands, selection-aware buttons.
145146
</Card>
146-
<Card title="Headless toolbar API reference" icon="code" href="/modules/toolbar/headless">
147+
<Card title="Headless toolbar API reference" icon="code" href="/advanced/headless-toolbar">
147148
Full command table, snapshot shape, and helper utilities.
148149
</Card>
149150
</CardGroup>
Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
---
22
title: Headless Toolbar
3+
hidden: true
34
sidebarTitle: Headless
45
keywords: "headless toolbar, custom toolbar, toolbar api, createHeadlessToolbar, toolbar state, toolbar commands"
56
---
@@ -8,7 +9,7 @@ Build your own toolbar UI. SuperDoc provides the state and commands — you rend
89

910
## Using React?
1011

11-
`superdoc/headless-toolbar` is the framework-agnostic substrate. **For new React apps, reach for `useSuperDocCommand` from `superdoc/ui/react` instead.** It re-renders one button per command (not the whole toolbar) and ships alongside companion hooks for selection, comments, and tracked changes. See [Bring Your Own UI › Toolbar and commands](/bring-your-own-ui/toolbar-and-commands).
12+
`superdoc/headless-toolbar` is the framework-agnostic substrate. **For new React apps, reach for `useSuperDocCommand` from `superdoc/ui/react` instead.** It re-renders one button per command (not the whole toolbar) and ships alongside companion hooks for selection, comments, and tracked changes. See [Custom UI › Toolbar and commands](/editor/custom-ui/toolbar-and-commands).
1213

1314
`superdoc/headless-toolbar` stays supported for existing integrations and framework-agnostic toolbar-only use cases. Both paths read from the same internal substrate.
1415

@@ -428,7 +429,7 @@ function Toolbar({ superdoc }) {
428429
## Examples
429430

430431
<CardGroup cols={2}>
431-
<Card title="Framework examples" icon="layout-grid" href="/modules/toolbar/examples">
432+
<Card title="Framework examples" icon="layout-grid" href="/advanced/headless-toolbar-examples">
432433
Full examples with React + shadcn, React + MUI, Vue + Vuetify, Svelte, and vanilla JS
433434
</Card>
434435
</CardGroup>

apps/docs/core/supereditor/configuration.mdx renamed to apps/docs/advanced/supereditor/configuration.mdx

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
---
22
title: Configuration
3+
hidden: true
34
keywords: "supereditor config, editor configuration, prosemirror setup, document editor options, advanced config"
45
---
56

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
---
22
title: Events
3+
hidden: true
34
keywords: "supereditor events, editor lifecycle, document events, editor callbacks, editor hooks"
45
---
56

apps/docs/core/supereditor/methods.mdx renamed to apps/docs/advanced/supereditor/methods.mdx

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
---
22
title: Methods
3+
hidden: true
34
keywords: "supereditor methods, editor commands, document manipulation, editor api"
45
---
56

@@ -52,7 +53,7 @@ await editor.open(null, { mode: 'html', html: '<p>Hello</p>' });
5253
</CodeGroup>
5354

5455
<Note>
55-
This is the instance method. For one-liner creation, use the static `Editor.open()` factory — see [Configuration](/core/supereditor/configuration).
56+
This is the instance method. For one-liner creation, use the static `Editor.open()` factory — see [Configuration](/advanced/supereditor/configuration).
5657
</Note>
5758

5859
### `close`
@@ -191,7 +192,7 @@ Lower-level export with additional control.
191192
`'external'`, `'clean'`, or custom
192193
</ParamField>
193194
<ParamField path="comments" type="Array">
194-
Comments to include — [data structure](/modules/comments#comment-data-structure)
195+
Comments to include — [data structure](/editor/built-in-ui/comments#comment-data-structure)
195196
</ParamField>
196197
<ParamField path="fieldsHighlightColor" type="string" default="'#FFFF00'">
197198
Field highlight color

apps/docs/core/supereditor/overview.mdx renamed to apps/docs/advanced/supereditor/overview.mdx

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
---
22
title: SuperEditor API
3+
hidden: true
34
sidebarTitle: Overview
45
keywords: "supereditor class, prosemirror docx, tiptap alternative, editor commands, document manipulation api"
56
---
@@ -8,20 +9,20 @@ SuperEditor is the low-level DOCX editing engine that powers SuperDoc. Most apps
89

910
## Pick the right layer
1011

11-
**Use SuperDoc + Bring Your Own UI for custom React UI.** `<SuperDocEditor>` (or `new SuperDoc(...)`) plus `superdoc/ui/react` gives you typed hooks for toolbar, comments, tracked changes, selection, and document control. See [Bring Your Own UI](/bring-your-own-ui/overview).
12+
**Use SuperDoc + Custom UI for custom React UI.** `<SuperDocEditor>` (or `new SuperDoc(...)`) plus `superdoc/ui/react` gives you typed hooks for toolbar, comments, tracked changes, selection, and document control. See [Custom UI](/editor/custom-ui/overview).
1213

1314
**Use the Document API for document mutations.** [`editor.doc.*`](/document-api/overview) is the stable, request/response surface that's identical on server, client, and AI agents. It's the recommended path for any insert / replace / format / comment / tracked-change operation.
1415

15-
**Use SuperDoc with built-in modules** when the standard look is fine. See the [Modules](/modules/overview) section.
16+
**Use SuperDoc with built-in modules** when the standard look is fine. See the [Modules](/editor/built-in-ui/overview) section.
1617

1718
**Reach for SuperEditor directly when:**
1819

1920
- You're integrating with a framework SuperDoc doesn't yet wrap.
20-
- You need [headless/server-side processing](/core/supereditor/configuration#headless-converter-nodejs).
21+
- You need [headless/server-side processing](/advanced/supereditor/configuration#headless-converter-nodejs).
2122
- You're building a custom extension that taps into ProseMirror plugins or schemas.
2223
- You explicitly need engine internals the higher layers don't surface.
2324

24-
For a typical React DOCX editor with a custom UI, you don't need this page — start at [Bring Your Own UI](/bring-your-own-ui/overview).
25+
For a typical React DOCX editor with a custom UI, you don't need this page — start at [Custom UI](/editor/custom-ui/overview).
2526

2627
## Quick start
2728

@@ -50,6 +51,6 @@ The `SuperEditor` Vue component wraps the `Editor` class with reactive props and
5051

5152
## API structure
5253

53-
- **[Configuration](/core/supereditor/configuration)** - Initialization options
54-
- **[Methods](/core/supereditor/methods)** - Control the editor and access properties
55-
- **[Events](/core/supereditor/events)** - React to changes
54+
- **[Configuration](/advanced/supereditor/configuration)** - Initialization options
55+
- **[Methods](/advanced/supereditor/methods)** - Control the editor and access properties
56+
- **[Events](/advanced/supereditor/events)** - React to changes

0 commit comments

Comments
 (0)