Realliance Pages landing site: how members publish their own static sites
  • HTML 55%
  • CSS 45%
Find a file
Christopher Miller d338c12088
Landing site: how members publish with Realliance Pages
Plain HTML and CSS, no build step, no JavaScript. Brand assets from
realliance/brand v0.1.0 (hashed names kept, pinned in brand.lock.json).

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FWhaDeswMqYvQaVdpL8oit
2026-11-04 07:48:12 -08:00
assets/brand Landing site: how members publish with Realliance Pages 2026-11-04 07:48:12 -08:00
brand.lock.json Landing site: how members publish with Realliance Pages 2026-11-04 07:48:12 -08:00
index.html Landing site: how members publish with Realliance Pages 2026-11-04 07:48:12 -08:00
README.md Landing site: how members publish with Realliance Pages 2026-11-04 07:48:12 -08:00
site.css Landing site: how members publish with Realliance Pages 2026-11-04 07:48:12 -08:00

Realliance pages

The landing site for Realliance Pages. It explains how forge members publish their own static sites. The site is the root site of the realliance org, so it serves at https://realliance.realliance.page/.

Layout

  • main holds the source: plain HTML and CSS, with no build step and no JavaScript.
  • The pages branch is what gets published. It holds a copy of index.html, site.css and assets/.
  • assets/brand/ holds unchanged files from realliance/brand at the signed tag v0.1.0. Keep their hashed names. brand.lock.json records the tag and each file's sha256.

Preview

python -m http.server -d . 8000

Publish

Change main by pull request with signed commits. Then publish from a clean checkout of main:

d=$(mktemp -d)
cp -r index.html site.css assets "$d"
cd "$d"
git init -q -b pages
git add -A
git commit -q -m "publish"
git push -f https://git.realliance.net/realliance/pages.git pages

The site is live within about a minute. See the Realliance Pages runbook for the rules.