# Connect Starlight Docs to a CMS

Connect Starlight to Prosefly, edit page properties and supported components, and review manual or automatic sidebar changes.

import StarlightDemo from '@/components/starlight/StarlightDemo.astro';

Give your team a visual CMS for an existing Starlight documentation site. An administrator connects the repository and configures publication. Writers can update guides, page properties, and supported components without learning Git commands.

You keep the Starlight site, its URLs, and its build pipeline. This guide takes one page from repository discovery to a reviewed content and navigation change.

## 1. Check the docs Collection

Your repository should contain the Starlight Astro application and its documentation files. The standard docs Collection uses Starlight's loader and schema:

```ts title="src/content.config.ts"
import { defineCollection } from 'astro:content';
import { docsLoader } from '@astrojs/starlight/loaders';
import { docsSchema } from '@astrojs/starlight/schema';

export const collections = {
  docs: defineCollection({ loader: docsLoader(), schema: docsSchema() }),
};
```

Keep the existing configuration if it already defines the Collection. Supported static schema extensions can add or override fields; Prosefly reads the definition without executing the application.

## 2. Connect, scan, and confirm navigation

From **Organization settings → Repositories**, connect the GitHub repository and choose **Scan repository**. [Connect GitHub](/docs/connect-github/) covers the account and GitHub App authorization steps.

Check the detected Starlight application, docs directory, Collection properties, editor profile, and native navigation configuration. Confirm the Content Space and its supported navigation binding, then wait for indexing to finish.

<p id="starlight-scan-guide">
  Try this step in the <a href="#try-editor">complete workflow</a>.
</p>

## 3. Edit a guide and its page properties

Open a guide from **Content**. Use the visual editor for Markdown and supported Starlight components, including asides, tabs, cards, and file trees. In **Properties**, update fields such as Title and Description; additional supported fields are available under More properties.

<p>
  Try this step in the <a href="#try-editor">complete workflow</a>.
</p>

Open Source for custom components or expressions without visual controls. You can try the supported controls in the [Starlight editor example](/frameworks/starlight/#try-editor); the example requires no account and resets on refresh.

## 4. Arrange manual entries and automatic groups

Open **Navigation** beside Properties and Outline. A supported static Starlight sidebar can combine manual entries and automatic directories, for example inside the existing `starlight()` configuration:

```js
sidebar: [
  { label: 'Start Here', items: ['overview'] },
  { label: 'Guides', autogenerate: { directory: 'guides' } },
];
```

- **Manual groups:** arrange supported entries in existing writable groups, or place an unlisted page in a supported group.
- **Automatic groups:** `autogenerate.directory` supplies the pages. Drag existing pages to reorder them within the same directory; Prosefly updates their `sidebar.order` frontmatter.

<p id="starlight-navigation-guide">
  Try this step in the <a href="#try-editor">complete workflow</a>.
</p>

Reordering generated pages does not move Markdown files. Wait for the navigation save status before opening review. The changes are still drafts and have not reached Git.

## 5. Review the affected files and publish

Open publication review and inspect every changed file. A manual sidebar edit can change `astro.config.mjs`; sorting automatic pages can change `sidebar.order` in their frontmatter. Review these alongside the document text.

<p id="starlight-review-guide">
  Try this step in the <a href="#try-editor">complete workflow</a>.
</p>

Publish using the Content Space's configured Commit or Pull request mode. A PR must be merged into the target branch; the existing Starlight build then renders and deploys the site. Check the published page and sidebar after that build completes.

If the configuration cannot provide a writable native navigation binding, publish content only where appropriate. Content-only publication does not add a page to the sidebar. See [website navigation](/docs/repositories-and-spaces/) and [Publishing to Git](/docs/publishing/) for these decisions.

## 6. Your existing Starlight site stays in place.

After Git publication, the existing Astro build renders and deploys your site. A pull request first needs to be merged. The Website stage below shows the published Starlight example.

<p id="starlight-published-guide">
  Try this step in the <a href="#try-editor">complete workflow</a>.
</p>

## Try the complete workflow

The example opens at editing. Use its stage controls to move through repository connection, discovery, editing, navigation, review, and the website preview.

<figure>
  <StarlightDemo language="en" stage="edit" id="try-editor" />
  <figcaption>
    Starlight workflow: connect → scan → edit → navigation → review → website.
  </figcaption>
</figure>

## Check the first update

Confirm the page's title and body, its intended sidebar placement, and the generated order. If configuration or files change outside Prosefly, scan again and refresh the index before continuing.

Continue with the [Starlight CMS overview](/frameworks/starlight/), [product documentation workflow](/use-cases/documentation/), [MDX component guides](/docs/editor/), or [Starlight authoring documentation](https://starlight.astro.build/guides/authoring-content/).