Prepare the episode page
Write introductions, guest details, links, and your own transcripts in Markdown or MDX. Maintain supported episode properties using your Collection’s schema.
Podcast content
Give every episode a home on your website.
Prepare show notes, guest information, and written transcripts alongside your audio or video links. Keep the episode copy in Git and the media in your shared library.
episodes/024.mdx
Episode 024
The creative process
A conversation about the habits, unfinished ideas, and small decisions behind creative work.
episode-024.mp332:18
- Show notes
- Guest links
- Written transcript
Keep the episode and its words together.
Publishing an episode means more than uploading a recording. Give the introduction, links, and written notes a shared place to take shape before they reach your website.
Use ready media links
Upload audio or video to the media library, then reference the ready public URL in the episode content or a supported property. Keep your website’s own player and rendering setup.
Understand delivery activity
Review available audio/video delivery-start reports, including podcast client and country breakdowns. These describe delivery activity, not completed plays or unique listeners.
From the next draft to your website.
- 01
Connect your episode Collection
Scan the website repository and confirm the files and fields used for episode pages.
- 02
Prepare the recording and copy
Upload the final media file, reference its ready URL, and work with your team on the show notes and written transcript.
- 03
Review the page and publish
Publish the reviewed episode copy through Git. Keep managing your site’s player, feed, and distribution in its existing setup.
How this works in practice
Transcripts are authored content; automatic transcription, RSS generation, and podcast-directory distribution are not provided. Audio/video uploads currently have a 150 MiB per-file limit. Media URLs are public and files are stored separately from Git. Delivery reports can lag and require the service’s analytics integration to be configured.
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.