A website often starts with a folder of Markdown files. The content is easy to keep, review, and move. As more people contribute, though, the writing experience can become the difficult part: not everyone wants to open a code editor or make a commit just to revise a paragraph.
Prosefly adds a shared place to write around the files you already have. The repository remains the home of your published text.
A place for work in progress
A draft needs room to change. You might rewrite the opening, ask a colleague to edit a section, or leave the document unfinished until tomorrow. None of those moments needs to become a published file.
Draft saving stays in the Prosefly workspace. It never creates a Git commit. Your team can collaborate in real time, work with supported frontmatter properties, and switch between visual editing and the full Markdown or MDX source.
A deliberate publication step
When the draft is ready, review the file changes. Publication writes the result to Git as a commit or pull request. The document returns to the same content path, with its frontmatter and source available to your existing tools.
Your website’s build pipeline then takes over. Publishing from Prosefly does not build or deploy the website itself.
A saved draft belongs in the workspace. A published document belongs in your repository.
Keep the website you already built
You do not need to replace your site builder with a new content delivery API. Prosefly works around supported Markdown and MDX content workflows in your existing repository.
Uploaded images, audio, and video are managed separately and referenced by URL in the text. Keeping your published words in Git does not mean that every uploaded asset becomes a repository file.
Start with content ownership to understand the boundary, or connect your first repository and try it with your own content.