Prosefly
All frameworks

Prosefly × Dahlia

Write together for your Dahlia docs.

Give the team behind your Dahlia website a shared place to maintain guides, edit page properties, and publish changes back to Git.

Connect your websiteRead the quickstart
Example repository contentDahlia
  • theme.config.json
  • src/content.config.ts
  • src/content/docs/overview.mdx

Selected content file

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

# Your first guide

A place for the things your team learns.
An illustrative file layout, not a live workspace.

Your files. A shared place to write.

Maintain your existing guide files

Discover supported Dahlia docsLoader Collections without relocating the content. Edit Markdown and MDX while keeping the original file paths.

Keep page properties close to the text

Manage supported docsSchema fields such as title, description, and order. Use Source for complex properties and custom MDX.

Review guide and navigation changes

With a confirmed native binding, arrange supported docsNav items and review the affected configuration alongside your content.

From your repository to your workspace.

  1. 01

    Connect the Dahlia repository

    Authorize GitHub and connect the repository containing your Dahlia website.

  2. 02

    Check the discovered documentation

    Confirm the docs Collection, page fields, and supported native docsNav binding.

  3. 03

    Edit a guide and publish through Git

    Save drafts in the workspace, review the changes, then create a commit or pull request for your existing website build.

What to know before you connect

Native navigation requires the actual Dahlia integration and matching docsLoader with supported static docsNav. Automatic groups use the theme’s directory rules. Reordering manual items does not move content files. New section creation and unresolved dynamic configuration are not supported.

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

Set up your workspace, understand publication, or explore the tools behind your website.

Explore another framework