Prosefly

Find the right home for your content.

Compare the tools behind your writing workflow. Start with where your content lives, then look at how your team edits, reviews, and publishes it.

Git & file-based CMSs

Keep the files. Choose the workflow.

These tools also work with content in files or Git. The differences are in setup, editing, and the path from draft to publication.

Database CMSs

Files in Git, or content through an API?

Structured content platforms serve a different need. Compare the storage model and the responsibility of running your content stack.

A visual editor that understands your docs.

Start with visual Markdown and MDX editing. Dedicated support for Starlight, Fumadocs, and Prosefly components lets you work with supported documentation blocks in the same editor.

  • Starlight

    Edit asides, tabs, cards, and file trees, with support for Starlight component syntax and Expressive Code metadata.

  • Fumadocs

    Work with callouts, tabs, steps, and accordions using their Fumadocs component syntax and supported properties.

  • Prosefly components

    Edit callouts, tabs, cards, and accordions from @prosefly/astro-components, used by Lotus and Dahlia.

Support follows the Collection’s editor profile and the component syntax it recognizes. Custom components and unsupported expressions remain available in Source; repository code is not executed.

Explore visual editing

Keep your website. Make room for writing.

Connect your repository and try the workflow with your own content.

Try ProseflyRead the quickstart