Skip to main content
Mintlify visual editor interface in light mode Access the visual editor from your dashboard to manage your documentation directly in your browser.
  • WYSIWYG editing: Make changes to your documentation using a what-you-see-is-what-you-get (WYSIWYG) editor that shows how your content will look when published.
  • Git synchronization: All changes automatically sync with your Git repository to maintain version control.
  • Team collaboration: Multiple people can work on documentation simultaneously.
  • Component integration: Add callouts, code blocks, and other components with slash commands.
  • No setup required: Start writing immediately from your dashboard.

Overview

Here is how you’ll typically work in the visual editor:
1

Choose your branch

Create a branch or make changes directly to your deployment branch. We recommend creating a branch so that you can preview your changes before they go live.
2

Open your file

Navigate to an existing file in the sidebar or create a new one using the file explorer.
3

Edit your content

Make changes in the visual editor. Press / to open the component menu.
4

Preview your changes

Visual mode shows you how your changes will appear on your live site. Use this to verify everything looks correct.
5

Publish your changes

If you’re working on your deployment branch, publish your changes directly from the visual editor. On other branches, you’ll create a pull request for review before publishing.

Editor modes

The visual editor has two modes to accommodate different editing preferences and needs: visual mode and Markdown mode. Use the mode toggle in the editor toolbar to switch modes.
Mode toggle icons highlighted in the visual editor.

Visual mode

Visual mode provides a WYSIWYG experience where changes that you make in the editor reflect how your published documentation will look. This mode is ideal for when you want to see how your changes will look in real-time.
Visual editing mode in the Mintlify visual editor

Markdown mode

Markdown mode provides direct access to the underlying MDX code of your documentation. This mode is ideal for when you need precise control over component properties or when you prefer to write in Markdown syntax.
Markdown mode in the Mintlify visual editor

Manage content

Use the sidebar file explorer to browse your documentation files. Click on any file to open it in the editor. Press Command + P on macOS or Ctrl + P on Windows to search for files by name.

Create new pages

Select the Create a new file icon in the file explorer sidebar.
Files menu in the visual editor
Filenames are automatically appended with a .mdx extension. To change the file type, click the file extension. Select the file type you want from the dropdown menu.
File extension menu in the visual editor.

Rename pages

To rename a page, click the kebab menu icon for the file you want to rename. Select Rename from the dropdown menu.
Rename page in the visual editor.

Delete pages

To delete a page, click the kebab menu icon for the file you want to delete. Select Delete from the dropdown menu.
Delete page in the visual editor.

Organize your navigation

Edit your docs.json file to add new pages and remove deleted pages from your site navigation. See Navigation for more information on how to organize pages. Example: Add a Themes page to the Profile group In this example, you created a new page titled Themes and you want to add it to the Profile group in your documentation. Add the path to the new page to the pages array of the Profile group in your docs.json file for it to appear in your site navigation.
Adding a Themes page to the Profile group
{
    "navigation": {
        "groups": [
            {
                "group": "Getting started",
                "pages": [
                    "index",
                    "quickstart",
                    "installation"
                ]
            },
            {
                "group": "Profile",
                "pages": [
                    "settings",
                    "account-types",
                    "dashboard",
                    "themes"
                ]
            }
        ]
    }
}

Edit content

Make changes to your pages using visual mode or Markdown mode in the editor. In visual mode, press / to open the component menu. Add content blocks, callouts, code blocks, and other components to customize your documentation.
The unfurled component menu emphasized in the Mintlify visual editor
In Markdown mode, you directly edit the MDX of your pages. This can be helpful when you need to:
  • Set specific component properties
  • Work with complex nested components
  • Copy and paste MDX content from other sources
See Format text and Format code for more information on how to write using Markdown syntax.

Publish your changes

The branch that you work on determines how the editor publishes your changes:
  • Deployment branch: Publishing updates your live site immediately.
  • Other branches: Publishing creates a pull request so you can review changes before deploying them to production.
The publish button emphasized in the Mintlify visual editor

Pull requests and reviewing changes

Pull requests let you propose changes from your branch so that other people can review them before merging into your live documentation. This helps ensure that your changes are correct and gives your team a chance to collaborate on content.
Even if you’re working solo, pull requests are valuable for previewing changes and maintaining a clear history of updates.

Create a pull request

1

Save your work

Select Save Changes to save all changes on your branch.
2

Create the pull request

Select Publish Pull Request from the editor toolbar.
3

Add a title and description

Write a clear title and description explaining:
  • What changes you made
  • Why you made them
  • Any specific areas that need review
4

Create and share

Select Publish Pull Request. The editor will provide a link to view your pull request.
Publish pull request button emphasized in the Mintlify visual editor

Review pull requests

Once your pull request is created:
  1. Review changes: You and your team members can review your pull request in your Git provider like GitHub or GitLab.
  2. Leave feedback: Add comments or request changes.
  3. Make additional changes: Make additional changes in the visual editor. When you save changes, the editor pushes them to your pull request.
  4. Approve: Approve the pull request when you’re satisfied with the changes.
  5. Merge: Merge the pull request when you’re ready to deploy your changes to production.

Keyboard shortcuts

The visual editor supports all common keyboard shortcuts such as copy, paste, undo, and select all, and the following shortcuts:
CommandmacOSWindows
Search filesCmd + PControl + P
Add link to highlighted textCmd + KControl + K
Add line breakCmd + EnterControl + Enter
BoldCmd + BControl + B
ItalicCmd + IControl + I
UnderlineCmd + UControl + U
StrikethroughCmd + Shift + SControl + Shift + S
CodeCmd + EControl + E
Normal textCmd + Alt + 0Control + Alt + 0
Heading 1Cmd + Alt + 1Control + Alt + 1
Heading 2Cmd + Alt + 2Control + Alt + 2
Heading 3Cmd + Alt + 3Control + Alt + 3
Heading 4Cmd + Alt + 4Control + Alt + 4
Ordered listCmd + Shift + 7Control + Shift + 7
Unordered listCmd + Shift + 8Control + Shift + 8
BlockquoteCmd + Shift + BControl + Shift + B
SubscriptCmd + ,Control + ,
SuperscriptCmd + .Control + .

Troubleshooting

Find solutions to common issues you might encounter while using the visual editor.
Possible causes:
  • Deployment is still in progress
  • Browser caching issues
  • Build or deployment errors
Solutions:
  1. Check deployment status in your dashboard.
  2. Hard refresh your browser (Ctrl + F5 or Cmd + Shift + R)
  3. Clear your browser cache.
Possible causes:
  • Insufficient permissions to the Git repository
  • Authentication issues with your Git provider
Solutions:
  1. Verify you have correct access to the repository.
  2. Check if your Git integration is properly configured.
  3. Review the Editor Permissions documentation.
Possible causes:
  • Network connectivity problems
  • Large documentation repositories
Solutions:
  1. Check your internet connection.
  2. Refresh the page.
  3. Contact support if the issue persists.
Possible causes:
  • Invalid MDX syntax in files
  • Missing or corrupted files
  • Large file sizes causing timeouts
Solutions:
  1. Check the file syntax for MDX formatting errors
  2. Verify the file exists in your repository.

Next steps

I