Editing content

Visual and Source modes

Open an entry from Content. Visual mode provides a content-focused view for supported Markdown and MDX documents. Source mode lets you edit the complete document, including frontmatter and MDX imports.

The visual editor does not execute your repository’s code. A custom MDX component may not render as it does on your deployed website. Malformed documents remain editable in Source so you can repair them.

Documentation components

Alongside generic Markdown and MDX editing, Prosefly provides dedicated editor profiles for Starlight, Fumadocs, and @prosefly/astro-components. These recognize supported component syntax and properties for documentation blocks such as callouts, tabs, cards, steps, and file trees. The available blocks differ by profile; Fumadocs and Prosefly components also support accordions.

The Collection’s editor profile determines this support. Custom components and unsupported expressions remain available in Source. Dedicated component editing does not run your repository’s code or reproduce the complete website layout.

Properties and outline

Use Properties to edit fields such as title, date, and tags. Available fields depend on the Collection’s discovered or configured schema. Visual edits and property changes save into the same complete document.

The Outline panel helps navigate headings. Focus mode gives the document more room. Narrow workspaces use a drawer for properties.

Save a draft

Check the document’s saving, saved, and collaboration status before leaving. A draft is saved to Prosefly, not committed to Git. Source editing can retain a local recovery copy; resolve any recovery prompt against the current shared document before continuing.

Add images

Upload through the editor or select a ready image from the media library. Existing repository image paths remain Markdown paths in Visual mode. Relative paths resolve from the content file, while root paths use the Space’s public directory.

Repository images and uploaded media have different storage rules. Read the media guide.

Review the result

Use publication review to see the actual source diff before writing changes to Git. Preview your built website through its own build workflow when you need to verify framework-specific rendering.