← all epics

Public site and comms

repo: n/a — this workspace (site/, epics/, deliverables/, brand/) · updated 2026-08-06

What this is

The public website for Lor: The Ten Thousand Things, plus the weekly-deliverable comms cadence it’s built to carry. The site is deliberately a thin renderer over content that already exists as plain markdown at the repo root (epics/, deliverables/) — it does not own any content. Astro 5 content collections use the glob loader pointed at ../epics and ../deliverables so nothing is duplicated into site/.

Why it exists

Kris has a standing weekly commitment to share a deliverable with a friend (Travis). This site turns that private habit into a public one, and does double duty as the front door for the eventual Christmas 2026 release. It also demonstrates, concretely, the “repo is the source of truth, the site is a rendering of it” principle — see the /workshop page and the third deliverable (deliverables/003-this-website.md).

Scope

• Pages: /, /deliverables + /deliverables/[n], /epics + /epics/[id], /codex, /workshop, /about, /press, /join.
• Agent-legibility surfaces: /llms.txt, every content page also served as raw markdown at <path>.md, /epics/index.json.
• Design: “storybook cover” direction (decided 2026-07-30, Kris, from mockups) — see brand/design.md for the full record: painted title-screen hero, saturated cream/gold/plum/pink palette, self-hosted Pixelify Sans + Press Start 2P, dark-panel dialogue-UI components (Kris panels, choice buttons), coloured-ball epic cards, hexagram broken/unbroken lines as a sparing graphic motif, mobile-first (the game itself is mobile). Supersedes the earlier “restrained ink-on-parchment, no gradients/shadows” description.
• Hosting: the AI Task Runner platform, not GitHub Pages. npm run build writes straight into ../public (a symlink the platform manages) and the site is immediately live at brand/site.config.json’s siteUrl (currently https://lor.kris.ai-task-runner.com) — no deploy step, no repo settings to flip. A GitHub Actions Pages workflow was drafted early on but is unused and disabled (.github/deploy-site.yml.disabled — kept outside .github/workflows/ because the git token in use refuses to push any file under that path, even a disabled one, without workflow scope); kept only in case a future custom domain makes Pages worth reactivating.
• Giscus comments component on deliverable pages, gated off via brand/site.config.json’s comments.enabled — permanently off as of 2026-08-04: giscus requires a public repo, and the decision (epics/workspace-dashboard/questions/001-repo-visibility.md) is that no lor repo will ever be public. The component stays in the codebase only until a non-GitHub comments approach is ever wanted.
• /join beta-signup: no backend exists; falls back to mailto until brand/site.config.json’s betaFormEndpoint is filled in.

Non-goals

• No CMS, no backend, no database. If it can’t be a markdown file read at build time, it’s out of scope for this epic.
• Not responsible for deciding the game’s name (see naming-and-brand) — the site renders whatever brand/brand.json says, including the “working title” marker while titleIsProvisional is true.
• Not responsible for the marketing plan (channels, timeline, audience) — that lives in marketing-and-communication/ and its own CLAUDE.md.

Parked ideas

• Health-bar-style progress indicators for epic/task completion (from the game’s own combat UI — Kris liked the look). Left out for now: there’s no meaningful completion signal to show, since most epics are parked ideas rather than measured work in progress. Revisit once an epic has a real, measurable completion signal worth visualizing — a task count alone isn’t it.

Key open questions

• Whether/when to enable GitHub Discussions + Giscus. Answered 2026-08-04: never on this repo — all lor repos are permanently private (giscus needs a public repo). If comments are ever wanted, it’s a different mechanism entirely. Same decision makes the GitHub Pages fallback (.github/deploy-site.yml.disabled) cost money if ever revived — Pages on a private repo needs a paid plan.
• Whether a real beta-signup backend gets built before /join needs to convert visitors, or mailto suffices through launch.
• Whether the weekly deliverable cadence to Travis continues privately in addition to, or is fully replaced by, the public posts.

Relevant docs

• land-of-lor/CLAUDE.md, land-of-lor/docs/README.md — source material for /codex.
• marketing-and-communication/CLAUDE.md — the broader comms plan this site’s launch feeds into.
• WHY.md — tone and priority reference for /about.

Status

1 backlog

Next: Nothing urgent. The Giscus/Discussions question is closed (2026-08-04 decision: repos permanently private, giscus impossible). Optional, non-blocking: whether /join ever needs a real form backend, and whether/which historic docs get ported into the deliverables log as backdated entries.

Deliverables (1)

• #3 — This website (2026-07-29)

Tasks (1)

backlog (1)

• public-site-and-comms/001 — Consider porting land-of-lor/docs/historic/ artifacts into the deliverables log as backdated entries (priority 3, estimate M )

Ask an agent about this epic

Also available as raw markdown.