Prosefly
All frameworks

Prosefly × Fumadocs

Write Fumadocs content with your team.

Bring your Fumadocs MDX files into a shared workspace. Edit supported properties and review native page-list changes alongside the content.

Connect your websiteRead the quickstart
Example repository contentFumadocs
  • source.config.ts
  • content/docs/meta.json
  • content/docs/index.mdx

Selected content file

---
title: Project overview
description: Start here to get to know the project.
---

# Your first guide

A place for the things your team learns.
An illustrative file layout, not a live workspace.

Your files. A shared place to write.

Discover your MDX Collections

Scan supported defineDocs and document Collection definitions, with literal content directories and readable schema fields.

Keep native page lists

Confirm the matching navigation binding to place pages in supported meta.json lists. Navigation remains in the repository beside your docs.

Keep your application independent

The content workflow uses your repository files. Your Fumadocs host and existing website build remain responsible for rendering and deployment.

From your repository to your workspace.

  1. 01

    Connect the Fumadocs application

    Authorize GitHub and connect the repository containing your Fumadocs source configuration.

  2. 02

    Review Collections and page lists

    Scan the repository, check detected content directories and fields, and confirm supported navigation bindings.

  3. 03

    Edit a page and publish the diff

    Choose its supported placement, review the document and affected meta.json files, then publish through Git.

What to know before you connect

Native navigation is verified for Fumadocs Core 16.0.x with MDX 15.0.x under supported dependency declarations. Broader or unknown versions remain read-only until verified. Localized meta files, custom loaders, source merges, and route transforms may require content-only publication.

Published content stays in your Git repository.

Drafts stay in Prosefly until you publish. Review your changes, then create a commit or pull request. Your existing website build handles deployment.

Understand content ownership

Keep going

Set up your workspace, understand publication, or explore the tools behind your website.

Explore another framework