Repositories and Spaces

Understand the hierarchy

An Organization owns memberships and its workspace. It connects Repositories. Each repository can contain several Spaces, and each Space contains Collections of content entries.

Use a separate Space for a distinct content area or website. A Collection groups files that share a content structure or editor profile.

Discover existing content

Connect a GitHub repository and scan its configured branch. Review the detected candidates before confirming them. Prosefly supports framework-aware discovery for supported Astro content setups and Fumadocs, and generic Markdown Collections for Hugo content.

Repository code is not executed in the editor. Custom loaders or dynamic configuration may require manual configuration and may not support native navigation editing.

Follow Connect GitHub for the account authorization, repository selection, and first scan.

Configure a Space

Owners and admins can manage Space configuration, Collection paths, editor profiles, and publication mode. Check the target branch and content paths before your first publication.

Manage website navigation

For supported Starlight, Lotus, Dahlia, and Fumadocs configurations, a scan can detect native navigation. Confirm the detected binding before using the Navigation panel.

Existing writable groups can accept new pages and reordered items. Automatic groups follow file paths; moving a navigation item does not move its Markdown file. Unsupported or ambiguous configuration may require content-only publication.

Refresh and archive

Git changes are reflected after an explicit scan and index rebuild, not through automatic GitHub webhook synchronization. Archived Spaces remain visible for review and can be reactivated by owners or admins, subject to capacity. Disconnecting a repository archives its Spaces; reconnecting does not automatically reactivate them.