Prosefly
All use cases

Product documentation

Keep your docs moving with your product.

Give writers and developers a shared workspace for guides, reference pages, and release notes. Review the files and supported navigation changes before they reach your website.

docs/getting-started.mdx

Product guide

  • Getting started
  • Configuration
  • Publishing

Product guide

Start your first project

Everything you need to go from an idea to a working project.

A good place to begin

Connect the project, check its settings, and share the first guide with your team.

Illustrative content, not a live workspace.

Make documentation part of the work.

A product changes one detail at a time. Give the people closest to those changes a place to update the explanation, with your existing review process.

Write together in the same guide

Collaborate on the document and its supported properties. Use visual editing for ordinary content and Source for the full Markdown or MDX.

Keep pages easy to find

For supported Starlight, Fumadocs, Lotus, and Dahlia configurations, confirm the native navigation binding and arrange pages in existing writable groups.

Review the change in context

Inspect the affected content and navigation files together. Publish a commit or open a pull request for your team’s GitHub review.

From the next draft to your website.

  1. 01

    Bring in your documentation

    Connect GitHub, scan the repository, and confirm the docs Collection and supported navigation binding.

  2. 02

    Update the guide with your team

    Edit the text and properties, check the page’s navigation placement, and keep the unpublished work as a workspace draft.

  3. 03

    Review and publish the files

    Inspect the diff and publish through Git. Your documentation site builds from the updated repository as usual.

How this works in practice

Navigation editing depends on a supported, confirmed native binding. Dynamic or ambiguous configurations may require content-only publication. Moving a navigation item does not move the document file. Prosefly does not build or deploy the documentation site.

Your published words belong in Git.

Save drafts in your workspace. Publish text back to your repository as a commit or pull request, then let your existing website build take it from there. Uploaded media stays separate and is referenced by URL.

How content ownership works

Keep using the tools behind your site.

Explore the supported content workflows for your framework or documentation tool.

More ways to use Prosefly

Make room for your next draft.

Connect your existing repository and give your content a shared place to grow.

Connect your docs