SPFN SITES — HOSTED PAGES
A GitHub repo in.
A website out.
Point your AI at a repo, push, and register it here — your site is live at <name>.spfn.page. No build chain. Push is deploy. A root spfn.site.yaml is the publishing contract.
01How it works
Three steps. No pipeline.
public repospfn.site.yamlregister<name>.spfn.page
STEP 01
Author the repo
A public GitHub repo with spfn.site.yaml at the root — pages, posts, and theme are plain files your AI writes. The full structure is in the spec.
STEP 02
Register it
Sign in with GitHub, pick a subdomain, point it at the repo. First come, first served.
STEP 03
Push is deploy
Every push shows up on your site within seconds. That is the whole pipeline.
02The contract
One file opts you in.
# spfn.site.yaml — at the repo root name: My Site description: What this site is about root: site # pages/, posts/, theme/, public/ live here
FIG 01 — THE WHOLE PUBLISHING CONTRACT
SPEC (HUMANS) — superfunction.xyz/docs/packages/pages
SPEC (AGENTS, RAW MD) — raw.githubusercontent.com/fxylabs/spfn/main/packages/pages/README.md