Prosefly
All comparisons
ProseflyPages CMS

Prosefly vs Pages CMS

Direct repository editing, or a workspace before publication?

Both give writers an interface for an existing GitHub website. Compare direct file editing with a workspace that keeps draft saving separate from Git publication.

Compare the details

Choose how your team moves from writing to Git.

Pages CMS uses a .pages.yml file to describe editable content and media, then saves changes back to GitHub. Prosefly adds a draft workspace, real-time writing, and a separate review-and-publish step.

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.

Pages CMS

A lightweight editing layer for static sites in GitHub repositories.

  1. 01

    Describe content and media in .pages.yml.

  2. 02

    Open the GitHub repository in Pages CMS and edit its files.

  3. 03

    Save changes back to GitHub; keep your existing deployment flow.

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.

Pages CMS

Content files directly in a GitHub repository.

Getting started
Prosefly

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

Pages CMS

Install the GitHub App and define content in .pages.yml.

Editing experience
Prosefly

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

Pages CMS

Configured fields and rich-text editing for repository content.

Drafts & saving
Prosefly

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

Pages CMS

Saving edited content writes changes back to GitHub.

Publishing
Prosefly

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

Pages CMS

Save repository files; the existing site deployment flow continues.

Media
Prosefly

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

Pages CMS

Configure repository media folders and the public paths written into content.

Hosting & maintenance
Prosefly

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

Pages CMS

Use the hosted app or deploy your own Pages CMS instance.

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

Pages CMS also keeps content in your repository and does not replace your site generator. That is shared ground. Evaluate draft handling and the collaboration experience with your own team rather than treating Git ownership as a unique feature.

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 Pages CMS when

  • You want a focused UI for editing files in GitHub.
  • You prefer describing editable fields and media with YAML.
  • You want an open-source editor you can also self-host.

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