Prosefly
All comparisons
ProseflyDecap CMS

Prosefly vs Decap CMS

Keep drafts in a workspace, or manage them as Git branches?

Both publish content to Git. Their draft workflows are different: Prosefly saves drafts in the workspace, while Decap’s editorial workflow uses branches, commits, and pull requests.

Compare the details

The key distinction is when Git changes.

In Decap’s default workflow, saving pushes a commit to the publication branch. Its optional editorial workflow saves drafts on branches and opens pull requests. In Prosefly, saving a draft never commits Git; publishing is a separate action.

Two ways to work with content.

Prosefly

A hosted writing workspace for an existing Git website.

  1. 01

    Connect a GitHub repository and choose a Space.

  2. 02

    Write together; save drafts in your workspace.

  3. 03

    Review the diff, then publish a commit or pull request.

Decap CMS

An extensible open-source CMS that maps editing actions to Git operations.

  1. 01

    Add the admin UI, choose a backend, and configure collections.

  2. 02

    Save directly to the publication branch, or enable editorial workflow.

  3. 03

    With editorial workflow, publish by merging the draft pull request.

A summary of each content workflow. Configuration and optional services can change the details.

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

What changes in your day-to-day work.

Published content
Prosefly

Published Markdown and MDX in your Git repository.

Decap CMS

Content files in your Git repository alongside website code.

Getting started
Prosefly

Connect GitHub, scan supported content, and configure a Space.

Decap CMS

Add the admin UI, configure config.yml, and connect a Git backend.

Editing experience
Prosefly

Visual and source editing, frontmatter properties, and real-time collaboration. Dedicated visual editing support for Starlight, Fumadocs, and @prosefly/astro-components.

Decap CMS

Rich-text widgets, preview, and custom editor extensions.

Drafts & saving
Prosefly

Draft saving never commits Git. Drafts stay in the workspace.

Decap CMS

Default saving commits directly; editorial workflow commits drafts on branches.

Publishing
Prosefly

Review file changes, then publish a commit or pull request.

Decap CMS

Editorial workflow merges the draft pull request into the publication branch.

Media
Prosefly

Uploaded images, audio, and video stay separate from published text and are referenced by URL.

Decap CMS

Repository media and optional external media integrations.

Hosting & maintenance
Prosefly

Prosefly hosts the workspace. You maintain your website and its build pipeline.

Decap CMS

Maintain CMS configuration and authentication; keep your existing site hosting.

Git publication does not deploy your site. Prosefly relies on your existing build pipeline, and repository refreshes require an explicit scan.

This comparison describes Decap CMS core. Decap Turbo is a separate hosted offering with its own services and plans. Prosefly currently connects through GitHub; do not assume support for every Git provider.

Choose around the work you need to do.

Choose Prosefly when

  • Your website already uses Markdown or MDX.
  • You use Starlight, Fumadocs, or @prosefly/astro-components and want visual editing for supported documentation components.
  • Your team wants real-time writing and a separate draft workspace.
  • You want to keep your site builder and deployment pipeline.

Consider Decap CMS when

  • You want an open-source CMS embedded in your site.
  • You want unpublished edits represented as Git branches and pull requests.
  • You need extensible widgets, previews, or a choice of Git backends.

Take a closer look

Sources & scope

Reviewed

Product facts were checked against the official documents below. The choice guidance is our assessment. Optional integrations and paid editions may add capabilities; check the current documentation and terms before choosing.

Other comparisons

Keep your website. Make room for writing.

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

Try ProseflyRead the quickstart