You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please get approval from the CHAOSScast facilitator before creating a CHAOSScast episode release checklist issue. You can learn more about the process for CHAOSScast by visiting our CHAOSScast process documentation
Title Format: Episode 123: My Great Title (default)
Content: Clean (unless we used swear words)
Summary: First paragraph from the Show Notes are a good starting point
Description: Insert the show notes in Markdown format.
Hint: convert show notes to Google Doc and export as Markdown
As the first line above the bolded episode info, add this line: Thank you to the folks at [Sustain](https://sustainoss.org/) for providing the hosting account for CHAOSSCast!
Keywords: (use sparingly to avoid keyword cannibilization)
Tags: (empty) -- we can use tags later for having sub-podcasts
Hosts and Guests: activate everyone who was on the show. Regular panelists are all hosts, even when they are guest on an episode.
Cover Art: upload cover art with the correct episode number
Header Image: (ignore, will use default)
Transcript: (ignore)
PUBLISH
Action: When the episode is scheduled for release that week, notify all participants via email, and send guests this link to a webform to get their mailing address
Please get approval from the CHAOSScast facilitator before creating a CHAOSScast episode release checklist issue. You can learn more about the process for CHAOSScast by visiting our CHAOSScast process documentation
Planning doc: https://docs.google.com/document/d/1QOfN4B3bTOLnOLKH3YWhdhZjhliYuJYw9WZtdqAOCMA/edit
CHAOSScast Episode Release Checklist
Scheduling an episode
Recording an episode
Publishing an episode (~30-40 min)
firstname-lastname
(e.g.,georg-link
)Thank you to the folks at [Sustain](https://sustainoss.org/) for providing the hosting account for CHAOSSCast!
The text was updated successfully, but these errors were encountered: