Importing is the fastest way to bring an existing body of knowledge into Doxbrix without rewriting everything by hand. It is especially useful when you are migra...
Importing is the fastest way to bring an existing body of knowledge into Doxbrix without rewriting everything by hand. It is especially useful when you are migra...
Importing is the fastest way to bring an existing body of knowledge into Doxbrix without rewriting everything by hand. It is especially useful when you are migrating from another documentation system, converting internal documents into a public site, or turning draft material into structured pages.
Doxbrix converts supported files into editable content built from real blocks, so the result is not just a file attachment. It becomes documentation your team can continue improving.
Supported formats
The Import document dialog accepts these file types, up to 20 MB each:
| Format | Extensions |
|---|---|
| Word | `.docx` |
| `.pdf` | |
| HTML | `.html`, `.htm` |
| Markdown | `.md` |
| MDX | `.mdx` |
| Plain text | `.txt` |
Import a document
Use Import Document when you want to convert a file into editable documentation content inside the page you are working on.
On a new line, press <kbd>/</kbd> and choose Import Document. Doxbrix opens Import document and shows how the imported content will be applied, such as Append to page, Insert at cursor, or Replace current block.
Drag a file into the drop area marked Click to browse or drag & drop, or click Choose file. The dialog also shows the supported file types and the Max 20 MB limit.
Doxbrix converts the file and displays progress such as *Converting
<filename>…*. After conversion, it confirms how many blocks were created. Review the result before continuing with normal editing.
Paste MDX or Markdown
If you already have Markdown or MDX as text, you do not need to upload a file. Use Import MDX from the slash menu to paste a snippet and convert it into blocks in place.
This is useful when:
- you are moving content from a repository or snippet library
- you want to reuse a known-good MDX example
- you are testing how imported content renders before bringing in a larger file set
Import an OpenAPI spec
To generate API reference content from an existing specification:
- In the content tree, click + on the destination space or group.
- Choose Add API reference.
- In Import OpenAPI Spec, choose Upload file or Paste JSON.
- Complete the import.
Doxbrix creates endpoint pages from the operations in the specification and pre-fills the relevant reference structure. This is much faster than hand-authoring an API section from scratch and helps keep the reference aligned with the source definition.
Clean up after import
Imported pages start as drafts. A quick editorial pass usually improves the result significantly:
Confirm that the page has one clear title and that the section hierarchy reads naturally.
Turn long procedural lists into steps, plain warnings into callouts, and loose side-by-side content into stronger layout blocks where needed.
Use Scan with AI and Improve with AI to tighten weak sections and raise the page to the same standard as hand-authored content.
Working as code?
If your team prefers a repository-based workflow, Doxbrix also supports importing and normalizing content through the CLI and migration workflows. See Import files and the migration guides for Notion, Confluence, and GitBook.