Meta Sites

A static HTML guide and website that makes the edit → upload → publish handoff easy to understand, test, and repeat.

Why this exists

A page can look updated in an editor and still show old copy after refresh if the change never made it into the file the host serves. That gap is frustrating for anyone updating a small site across an editor, GitHub, and a publishing host.

Meta Sites makes the chain visible: Muse edits the supplied HTML, Git-FED uploads it, and GitHub Pages serves that published file. It is intentionally a static-file project—not a database-backed editor or a web app with a build pipeline—so visitors can inspect the pages and follow the handoff directly.

See it work

Live demo: Not available yet. This repository has not been published, and it contains no configured public demo URL or deployment workflow. GitHub Pages can be enabled from the repository settings; the Cloudflare Worker is a template with a placeholder origin, not a deployed service.

Here is a 30-second capture of the actual site running locally—not a product mockup:

Run the site locally

From the repository root, start Python's built-in static server:

python3 -m http.server 8000

Open http://localhost:8000. No package install or build step is needed. Try the main page, the setup checklist, or the static-page example.

Screenshots

These are screenshots captured from the real local HTML pages.

Homepage	Original promo gallery
Animated FED-OS footer	Private-community eligibility page

Original promotional artwork

The project includes the original humorous mascot set as optimized images for the site. The original PNG files are also in assets/promos/ for higher-resolution reuse.

Quick start and real examples

There is no installer, package manifest, build command, or automated test suite in this repository. The files are served as-is.

# from the repository root
python3 -m http.server 8000

Then open http://localhost:8000. Useful routes and examples:

• The live-local landing page explains the four-step publishing handoff.
• Setup checklist walks through repository setup, GitHub Pages, Google Sites, and the refresh check.
• Static-page example shows the minimal HTML pattern and explains what it does—and does not—connect to.
• Promo gallery displays the original illustrations, looping mascot GIF, and symbol mark.
• Discord page has the centered widget and community buttons; the NSFW access request goes through an age-confirmation page.
• Private communities page asks for 18+ confirmation and an eligible country before revealing the Matrix link.

Publish it

GitHub Pages

1. Create a repository named Meta-Sites and place the contents of this folder at its root, with index.html beside assets/.
2. In GitHub, open Settings → Pages, choose Deploy from a branch, select the branch containing the files, and choose /(root).
3. Open the URL GitHub displays after deployment and test the home page, a nested HTML route, the symbol favicon, and a refresh.

See the deployment guide and GitHub Pages setup checklist.

Cloudflare

Choose one production setup: put the included fixed-origin Cloudflare Worker template in front of GitHub Pages, or connect the repository directly to Cloudflare Pages. The GITHUB_PAGES_ORIGIN value in wrangler.toml is still a placeholder; replace it and configure a real Cloudflare zone/hostname before deployment. Follow the Cloudflare routing guide. No Cloudflare project or custom domain has been configured here.

Project map

• index.html — real entry point for the static guide and visual landing page.
• assets/styles.css, assets/animated-background.js — dark motion design, ticker, and visual behavior.
• assets/promos/ — original mascot, four promo illustrations, source PNGs, optimized WebPs, and GIF.
• assets/demo/ — real rendered screenshots and the browser-tour GIF shown above.
• pages/ — HTML routes for the promo gallery, support, Discord, private communities, privacy, and return screens.
• docs/ and examples/ — editable Markdown source paired with browser-facing HTML pages.
• cloudflare/worker.js and wrangler.toml — unconfigured Cloudflare Worker proxy template.

Notes and limits

• The support age screen is self-attestation, not verified age control. Check provider account, prices, renewal terms, and return settings before accepting payments.
• The country check on the private Matrix page is also a self-reported browser-side check, not geolocation or secure access control. Its link is visible in public client files; do not use this page to protect a sensitive secret.
• No GitHub Pages or Cloudflare deployment has been performed. The browser screenshots above were captured from the local static preview.
• The public footer includes the FED-OS ecosystem, contacts, and social links. Facebook and the personal Substack are omitted as requested; the careers address is omitted until hiring is confirmed. The Matrix link is kept off the footer and routed through the separate 18+ page.

Project ownership

Muse edits the files supplied for an update and returns them. Git-FED uploads the changed files to GitHub. The configured host publishes the uploaded version. After each upload, check the public page and refresh it to confirm the update is still there.