Start here
Content ownership
Your repository is the source of truth for published content.
Your content lives in your own Git repository. Prosefly publishes Markdown and MDX files back to that repository, preserving their content paths and supported frontmatter formats.
Files, drafts, and media
| Content | Where it lives | When it changes Git |
|---|---|---|
| Published text | Files in your GitHub repository | On commit publication, or after a published PR is merged |
| Unpublished drafts | Your Prosefly workspace | Only when you explicitly publish |
| Navigation changes | Workspace while drafted; native repository config when published | When included in publication |
| Uploaded images, audio, and video | The managed media library | A document may reference their public URLs |
Saving a draft never creates a Git commit. A pull request holds the proposed files on its branch; the target branch changes only after merge.
A different storage model
Sanity’s Content Lake stores structured content in its datastore. Payload uses a configured database through its database adapters and provides APIs around that data. Payload can be self-hosted; the distinction here is the content format and storage model, rather than who owns the database.
Prosefly’s published text is stored as repository files. Your website can keep reading those files through its existing content pipeline without querying Prosefly to render every page.
Keep using your tools
Published files remain editable through GitHub or your usual code editor. Their history remains in Git. Scan the repository after external changes so Prosefly can refresh its view.
If an external change affects an entry with a saved draft, resolve the difference between the original base, current Git version, and draft before publishing. Prosefly does not automatically merge conflicting content.
Preserve a complete copy
Back up your Git repository through your normal Git workflow. Unpublished drafts and managed media are separate from that repository: export draft Markdown or publish it when appropriate, and keep copies of original media assets. Published files remain in Git after your Prosefly entitlement ends.
Last updated Oct 9, 2026