1. Create a repository
Create a private or public GitHub repository for the supplied source folder. Commit content/, assets/, data/, build.py and .github/workflows/. A public repository will reveal draft Markdown and repository history; choose the visibility you want.
2. Edit a Markdown journal entry
Each journal post is a file under content/journal/ with simple frontmatter. Use GitHub’s file editor to correct text, add citations and submit the change. The site derives human-readable pages and an RSS feed from these files.
3. Generate a downloadable artifact
The supplied GitHub Actions workflow installs Python dependencies, builds the site and uploads benandanti-static-site.zip as a workflow artifact. Download the artifact from the workflow run.
4. Publish to Name.com
Extract the generated ZIP into the document root assigned to benandanti.org. Replace old files, keeping any unrelated server files backed up and separate. Do not upload the source repository, credentials or workflow files into the public document root.
Optional automation
After confirming your host’s actual deployment protocol and directory, GitHub Actions could upload the build automatically using carefully scoped repository secrets. No credentials or unsupported hosting assumptions are included.
Limitations
This is a GitHub-managed Markdown publishing workflow, not a live GitHub comments system. It does not pull posts at runtime. The public journal continues working during GitHub outages.