Publish a story from the given directory to GitHub Pages.
Steps
- •Run the publish script to assemble both page versions:
code
bash scripts/publish_story.sh $ARGUMENTS
- •Verify the generated files in
pages/look correct (preamble at top, copyright at bottom of full version; Medium version useslayout: nullfor plain HTML with no theme, starts with title and subtitle, and has no copyright). - •Stage and commit the changed files under
pages/and any modified source files. - •Push to origin.
- •Watch the GitHub Actions deployment with
gh run watchuntil it succeeds. - •Verify the live pages by checking for expected content with
curl -s.
Audio
If the story directory contains an .m4a audio file (generated by the story-to-audio skill), the publish script automatically:
- •Copies the audio file into
pages/ - •Embeds an HTML5
<audio>player in the full version, between the preamble/prompt and the story content - •The Medium version does not include the audio player
Featured Image
If the story directory contains a .png file with the same basename as the story (e.g., the_confabulators_gambit.png for the_confabulators_gambit.md), the publish script automatically:
- •Copies the PNG into
pages/ - •Includes the image in the Medium version after the subtitle (for use as the Medium featured image)
Index
The publish script automatically updates pages/index.md:
- •If the story is already listed (matched by its basename link), the existing entry is updated with the current title and tagline
- •If the story is new, an entry is appended to the end of the index
- •Each entry links to the full version and the Medium version
Important
- •Never include Co-Authored-By lines or any AI branding in commits.
- •The story directory (e.g.,
gambit) must contain the story.mdfile and astory-prompt.md. - •Common files
common/preamble.mdandcommon/LICENSE-CC-BY-NC-4.0.mdmust exist.