Meta Sites setup checklist

Repository and Pages

  • [ ] Create the Meta-Sites repository on GitHub.
  • [ ] Extract this ZIP and upload the project contents so index.html is at the repository root.
  • [ ] Turn on GitHub Pages in the repository settings.
  • [ ] Choose the branch containing the files and the root folder (/(root)), then save.
  • [ ] Wait for the deployment and copy the exact GitHub Pages URL shown in Settings → Pages.

Google Sites

  • [ ] Put the GitHub Pages URL in Google Sites as an embedded page or a normal link.
  • [ ] Publish the Google Site changes.

Edit and publish

  • [ ] Git-FED sends the current HTML file to Muse here, with the requested text and images.
  • [ ] Muse edits the supplied file and hands the edited version back.
  • [ ] Git-FED uploads the new version to GitHub. Muse never writes to GitHub.
  • [ ] Open the live Pages URL and check the edited text is there.
  • [ ] Refresh the Pages URL and check the text stays.
  • [ ] If Google Sites is the entry point, open it live and check its link or embed reaches the current Pages URL.

If the update is missing, follow Troubleshooting. For the screen-by-screen Google Sites path, see Google Sites steps.

Cloudflare and support page

  • [ ] Choose the production path: GitHub Pages behind the Worker proxy, or Cloudflare Pages connected directly to the GitHub repository.
  • [ ] For Worker proxying, replace the GitHub username placeholder in wrangler.toml and attach the Worker to the intended Cloudflare hostname.
  • [ ] Open the Cloudflare public HTML URL and verify a page, image, favicon, guide route, age screen, and refresh after every upload.
  • [ ] Confirm the 18+ self-attestation text and provider account, price, subscription frequency, donation destinations, and success URLs before accepting real payments.