Importing from Markdown Files
WP Super Docs can import a ZIP file of Markdown files directly, which makes it a universal landing point for any documentation tool that can export to Markdown, even ones without a dedicated importer of their own.
The expected ZIP structure#
- Each
.mdfile becomes a doc. - Each sub-folder becomes a category.
- Optional YAML frontmatter at the top of a file sets its title, slug, description, status, and order.
docs.zip
├── getting-started/
│ ├── installation.md
│ └── quick-start.md
└── advanced/
└── custom-integrations.md
Supported frontmatter keys#
| Key | Example | Default if omitted |
|---|---|---|
title | Getting Started | Filename, humanized |
slug | getting-started | Filename, slugified |
description | A quick intro. | (blank) |
status | draft | publish |
order | 10 | 0 |
---
title: Getting Started
order: 1
---
Your doc content here, in normal Markdown.
Running the import#
Go to WP Super Docs → Import, choose Markdown ZIP, and fill in:
- ZIP file: the ZIP you’re uploading.
- Assign to product: which existing WP Super Docs product every imported doc goes under.
- Assign to version (only shown if you have versioning set up): optionally assign every doc in this import to one version.
- Duplicate handling: skip anything whose slug already exists, or update existing docs whose slug matches.

Click Import docs.
Importing from GitBook#
GitBook doesn’t export a Markdown ZIP directly. Use the free, open-source GitBook Exporter tool to download your entire GitBook space as a structured Markdown ZIP, then upload that ZIP using the form above exactly as described.
Importing from ReadMe.io#
ReadMe’s official export already produces a ZIP of Markdown files organized into category folders, no third-party tool needed. Download it from your ReadMe project, then upload it using the form above. The title, slug, order, and hidden (mapped to draft status) fields in ReadMe’s exported frontmatter are all recognized automatically.
ReadMe uses some custom block syntax (for example [block:image]) for embedded content, which imports as plain text rather than being converted. Plan to review and clean up any such blocks after importing.
Importing from Notion#
Use Notion’s built-in Markdown & CSV export. Sub-page folders in the export become categories, and each Markdown file becomes a doc; Notion’s page IDs are automatically stripped from titles.
Export from the most specific top-level page that contains only your docs, rather than your entire workspace, to keep the resulting category structure clean.
Importing from Docusaurus#
Docusaurus stores all documentation as Markdown files in a docs/ folder already (or whichever folder is set as your docs root in docusaurus.config.js). ZIP that folder directly and upload it, no conversion tool needed.
Beyond the standard frontmatter keys, several Docusaurus-specific conventions are handled automatically:
| Docusaurus feature | How it’s handled |
|---|---|
_category_.json / _category_.yaml | Folder labels and ordering |
sidebar_position | Maps to doc sort order |
sidebar_label | Used as the title when no title key is present |
id | Used as the slug when no slug key is present |
draft: true | Imported as a WordPress draft |
.mdx files | JSX components stripped, Markdown content imported |
Was this helpful?
Thanks for your feedback!
✓ Feedback received. Thank you!