Skip to content

Conversation

@ethanpalm
Copy link
Collaborator

@ethanpalm ethanpalm commented Nov 26, 2025

Documentation changes

This PR replaces most uses of MDX with Markdown since we support .md and .mdx file types.

Biggest change is in pages.mdx where we explain that a page is a Markdown file and it can be either type, but MDX can use JSX.

I left all the API-related content as MDX only since no one currently has .md endpoint pages and we don't want people creating them. So users would only really be going from MDX to openAPI or setting up MDX endpoint pages.

Closes https://linear.app/mintlify/issue/DOC-210/update-docs-to-mention-standard-md-file-support


For Reviewers

When reviewing documentation PRs, please consider:

✅ Technical accuracy

  • Code examples work as written
  • Commands and configurations are correct
  • Links resolve to the right destinations
  • Prerequisites and requirements are accurate

✅ Clarity and completeness

  • Instructions are clear and easy to follow
  • Steps are in logical order
  • Nothing important is missing
  • Examples help illustrate the concepts

✅ User experience

  • A new user could follow these docs successfully
  • Common gotchas or edge cases are addressed
  • Error messages or troubleshooting guidance is helpful

Note

Clarifies Markdown page support (.md and .mdx) and standardizes MDX terminology across docs, with key updates to Pages, Editor, and Migration guides.

  • Docs: page format support
    • Update organize/pages.mdx to define pages as Markdown; support .md and .mdx; recommend MDX for full functionality.
  • Editor
    • Revise Markdown mode description and examples; standardize references to editing MDX; fix slash-command instruction formatting in editor.mdx.
  • Migration
    • Update manual migration steps in migration.mdx to use Markdown pages; add tip to convert .md to .mdx; adjust asset reference wording.
  • API Playground
    • Standardize MDX terminology in api-playground/mdx-setup.mdx and api-playground/overview.mdx regarding custom endpoint pages.
  • Customization
    • Standardize MDX references in customize/react-components.mdx and customize/custom-scripts.mdx.
  • Personalization
    • Clarify MDX usage for user content access and examples in deploy/personalization-setup.mdx.
  • Settings
    • Clarify api.mdx configuration description in organize/settings.mdx.
  • Navigation
    • Minor rewording of page definition in organize/navigation.mdx.

Written by Cursor Bugbot for commit 7211090. This will update automatically on new commits. Configure here.

Copy link
Contributor

@k-finken k-finken left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this looks good but I don't think we should replace MDX with Markdown in most of the spots since Markdown isn't a superset of those two. I think we should keep MDX in most of the spots and just label a few specifics with we support .md as well.

CC @hahnbeelee

3. If you have OpenAPI specifications, add them to your `docs.json` and configure the API playground.

<Tip>
If you migrate your content as `.md` files, convert them to `.mdx` to support interactive features like React components.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

love this ❤️

Copy link
Contributor

@k-finken k-finken left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left 1 comment but otherwise looks great 🚢

@ethanpalm ethanpalm merged commit 6f0cf51 into main Nov 26, 2025
5 checks passed
@ethanpalm ethanpalm deleted the md-support branch November 26, 2025 03:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants