Realliance Pages landing site: how members publish their own static sites
- HTML 55%
- CSS 45%
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 |
||
|---|---|---|
| assets/brand | ||
| brand.lock.json | ||
| index.html | ||
| README.md | ||
| site.css | ||
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
mainholds the source: plain HTML and CSS, with no build step and no JavaScript.- The
pagesbranch is what gets published. It holds a copy ofindex.html,site.cssandassets/. assets/brand/holds unchanged files fromrealliance/brandat the signed tagv0.1.0. Keep their hashed names.brand.lock.jsonrecords 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.