Overview
Choose the right editor for documents and structured resources.
Prosefly has two editors. The Visual Editor works with Markdown and MDX documents. The Resource Editor works with JSON and YAML data files. Both save drafts in your Content Space; publishing is a separate step.
Try the editor without an account
Open the Markdown example to edit a sample document before connecting a repository. Try the Starlight, Fumadocs, or Prosefly examples for supported MDX components, page properties, navigation, and a comparison of your changes.
Changes stay in the current tab and reset when you refresh. The example does not connect to GitHub, save shared drafts, or publish content.
Choose an editor
| Content | Editor | Start here |
|---|---|---|
| Markdown and MDX documents | Visual Editor, with a Source mode | Visual Editor |
| JSON and YAML resources | Resource Editor, with Visual and Code modes | Resource Editor |
The Collection’s file types and configuration determine which editor opens. Resource files use fields and lists rather than a document body.
Markdown and component support
Every editor profile includes the supported Markdown basics. Start with Basics, then use the individual guides for tables, task lists, code, diagrams, math, images, media, and footnotes. The Mermaid and Math guides show profile-specific rendering, while Footnotes covers references that stay in the document.
For MDX, choose the Collection profile that matches the components in your documents: Starlight, Fumadocs, or Prosefly. The MDX components section explains each block’s UI, source syntax, and profile differences. For example, Callout is available in all three profiles, Accordion covers Fumadocs and Prosefly groups plus Starlight Details, and Link Button is specific to Starlight.
The editor does not execute repository code or reproduce the full website. Custom components and unsupported expressions remain editable in Source. Preview the website through its own build when checking the final rendering.
Drafts and publication
Visual document edits save automatically; check the saving status before leaving. Resource edits require Save draft. A draft does not change your Git repository.
Before publishing, use publication review to inspect the actual file diff. Your Content Space’s publication settings determine whether the result is a commit or a pull request.
Writing assistance
Use AI writing to revise selected document text and Languages and translation to prepare a complete article in another configured language. Review the generated draft before publishing.
Last updated Oct 19, 2026