Write visually, keep the source
Draft ordinary Markdown and MDX in the visual editor, or use Source when your article needs custom syntax. Your content stays in its existing format and path.
Blogs and journals
A place for the next story.
Write articles and studio notes without giving up your existing website. Work on the text, properties, and images together, then publish the files back to Git.
blog/studio-notes.mdx
Studio journal 2026.10.08
Making space for the work
A few notes on finding a rhythm, keeping a small practice, and returning to the page.
WritingStudio notes
A little room to think
Some ideas arrive slowly. A quiet afternoon, a blank page, and a place to keep the first version.
Spend your time on the story.
An article is more than its body text. Keep the draft, its metadata, and its images close together so the next edit does not mean another round of file juggling.
Keep article properties close
Edit supported frontmatter fields next to the text. Your Collection configuration determines which fields are available; there is no fixed title, date, or tags schema.
Bring images into the writing flow
Insert ready images from the shared media library or keep existing repository image references. Uploaded assets stay separate from Git content.
From the next draft to your website.
- 01
Connect the articles you already have
Scan the website repository and confirm the Collection containing your posts. Review the detected or explicitly configured fields.
- 02
Work on the next draft
Write the article, update its properties, and add images. Saving a draft does not create a Git commit.
- 03
Publish when the article is ready
Review the diff, then publish a commit or pull request. Your existing website build decides how the article appears.
How this works in practice
Custom MDX and Hugo shortcodes may need Source editing. Publishing writes files to Git; it does not schedule a future release or automatically change a framework’s draft property. Keep original copies of uploaded images alongside your normal repository backups.
Your published words belong in Git.
Save drafts in your workspace. Publish text back to your repository as a commit or pull request, then let your existing website build take it from there. Uploaded media stays separate and is referenced by URL.
How content ownership worksKeep using the tools behind your site.
Explore the supported content workflows for your framework or documentation tool.
More ways to use Prosefly
Make room for your next draft.
Connect your existing repository and give your content a shared place to grow.