Prosefly
All frameworks

Prosefly × Starlight

A visual CMS for your Starlight docs.

Let your whole team edit Starlight documentation without learning Git. Write Markdown and MDX, edit supported components, and review sidebar changes before publishing. Keep your existing Starlight site.

Prosefly recognizes your existing Starlight docs configuration. No extra CMS collection or field definitions for supported setups.

From an existing Starlight site to a reviewed update.

Connect your repository, confirm the detected Docs Collection, edit a guide, and arrange its sidebar. Try the workflow here before connecting your own site.

  • Keep your Starlight docs definitions

    Read the existing docsLoader and docsSchema definitions, including supported static schema extensions. Prosefly detects the docs Collection and its page properties without a second CMS schema.

  • Give pages a place in the sidebar

    With a confirmed navigation binding, arrange manual entries in existing writable groups and reorder automatically generated pages within the same directory. Starlight autogenerate.directory groups are supported.

  • Review content and navigation together

    Review the document, sidebar configuration, and sidebar.order changes together before creating a commit or pull request.

View example repository files
Example repository contentStarlight
  • astro.config.mjs
  • src/content.config.ts
  • src/content/docs/guides/overview.mdx

Selected repository file

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

# Your first guide

A place for the things your team learns.
Illustrative repository files. Use your project’s own paths and configuration.

Try the Starlight CMS workflow.

Connect the sample repository, confirm its Docs Collection, then edit a guide and review its content and navigation changes.

Prosefly/Repositories
getting-started.mdxProsefly / Starlight / Docs
Starlight

Loading editor…

Draft stays on this page

Interactive demo. Changes stay on this page; no repository is connected or published.

Interactive example: changes stay on this page. No repository is connected or published.

Connect your site. Keep its configuration.

  1. 01

    Connect your documentation repository

    Authorize GitHub and scan the Astro application that uses Starlight.

  2. 02

    Confirm Docs, fields, and navigation

    Review the automatically detected docs Collection, page fields, editor profile, and supported sidebar binding. Confirm what your existing Starlight configuration already defines.

  3. 03

    Write a guide and review its placement

    Edit the page, choose a supported navigation placement, and review all affected files before publication.

What to know before you connect

Native sidebar editing requires supported static configuration. Dynamic sidebar expressions may require content-only publication. Moving a navigation item does not move its Markdown file. Complex frontmatter remains editable in Source.

Using a CMS with Starlight

Do I need to rebuild or move my Starlight site?

No. Prosefly connects to your GitHub repository and uses the existing docs Collection. You keep your Starlight theme, URLs, hosting, and build process. Published changes enter that process as repository files.

Which Starlight content can I edit visually?

You can edit Markdown and supported MDX components, including asides, tabs, cards, and file trees, along with supported page properties and Expressive Code metadata. Custom components and unsupported expressions remain editable in Source.

How does Starlight sidebar editing work?

Prosefly supports both manually configured sidebars and automatic groups generated with autogenerate.directory. Arrange manual entries in existing writable groups, or drag generated pages to reorder them within the same directory. Sorting generated pages updates their sidebar.order frontmatter without moving the Markdown files. Review all affected files before publishing.

Does Starlight need a Prosefly-specific config file?

Not for supported static setups. Prosefly recognizes Starlight’s docsLoader, docsSchema, and supported native sidebar configuration. Review and confirm the scan results; you do not need to redefine the same collections and fields for the CMS.

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

Connect a Content Space, understand publication, or explore the tools behind your website.

Explore another framework