Documentation is more than paragraphs. A warning callout explains a constraint. Tabs show alternatives. A card points the reader to the next guide. Those components are part of how the website communicates.
A generic rich-text editor can cover the basics. A documentation workspace also needs to understand the supported component syntax around the text.
Start with the Collection profile
Prosefly provides generic Markdown and MDX visual editing and dedicated support for recognized Starlight, Fumadocs, and @prosefly/astro-components syntax. The active Collection profile determines which supported blocks the editor can work with.
This support does not mean that Prosefly executes your repository code or renders every possible MDX component. A component can be valid for your website and still require editing in Source.
Work with familiar documentation blocks
Supported profiles give writers an editing experience for recognized blocks such as callouts, tabs, and cards. The precise set depends on the profile and the component syntax. This lets the author focus on the explanation while preserving the document format used by the site.
Keep the original source accessible. When a block uses unsupported syntax, a custom expression, or a configuration the profile cannot safely understand, edit the full file in Source.
Review the result as content
The editor is one part of the workflow. Before publication, review the Markdown or MDX changes and any supported page properties or navigation changes. Your existing website build remains responsible for the final rendering.
For the current editing scope, read the editing guide. The Starlight and Fumadocs pages describe their content and navigation workflows.