GameCult Site

gamecult-site is the public gamecult.org root site: studio pitch, projects, docs, blog, and the usual pile of ambitions trying to look organized in public.

Valuable here: the GameCult brand, defined in code: site/quartz.config.ts (configuration.theme: typefaces, weights, palette tokens) and site/quartz/styles/custom.scss (ground wash, layout, page-type variants). docs/brand-design-language.md explains which decisions there were deliberate. Anything with a visual surface in the swarm follows this rather than inventing a look. Second, the published content: GameCult/index.md (manifesto), GameCult/Projects/ (one public page per project), GameCult/Blog/, GameCult/Docs/.

Problem it solves: the studio needs one public face and one visual identity that every repo and agent can read from source, instead of prose descriptions that drift. The Quartz engine itself is shared and lives in GameCult/GameCult-Quartz; this repo owns only the content and the GameCult overlay.

Entry points: site/quartz.config.ts, site/quartz.layout.ts, docs/brand-design-language.md, GameCult/; build with scripts/quartz/quartz.ps1 build (see Local Development).

Live versus planned: live is the site at gamecult.org, deployed to GitHub Pages from main by .github/workflows/deploy-quartz.yml, built on the shared engine in GameCult/GameCult-Quartz (extraction rationale: docs/gamecult-quartz-extraction-plan.md). In progress is the masthead and one-column redesign campaign (docs/masthead-campaign.md and the docs/masthead-cut-*.spec.json cut specs); treat that document as the plan, not as a description of the site today.

The site builds against the shared GameCult-Quartz engine. This repo owns published content and the GameCult overlay.

Repo Shape

• GameCult/: published Markdown content
• site/: GameCult-specific Quartz overlay
  • quartz.config.ts
  • quartz.layout.ts
  • custom components
  • custom styles in site/quartz/styles/custom.scss
  • static assets
• quartz-site/public/: generated static output
• scripts/quartz/quartz.ps1: local build/dev launcher
• .github/workflows/deploy-quartz.yml: Pages deploy workflow, delegated to GameCult-Quartz

Shared Engine Dependency

Local builds expect the shared engine repo to exist either:

• as a sibling checkout named GameCult-Quartz, or
• at the path provided through GAMECULT_QUARTZ_ROOT

Install dependencies in GameCult-Quartz first:

cd ..\GameCult-Quartz
npm ci

Local Development

From this repo root:

.\scripts\quartz\quartz.ps1 dev

For a one-off production build:

.\scripts\quartz\quartz.ps1 build

The shared engine stages a runtime under .quartz-build/engine and writes the final static site to quartz-site/public.

Content Map

• GameCult/index.md: root landing page and manifesto
• GameCult/Projects/: public project pages
• GameCult/Blog/: posts, fiction, and announcements
• GameCult/Docs/: documentation and infrastructure-facing pages

Aetheria lives on its own site at https://aetheria.gamecult.org; this repo links outward instead of pretending to be both things at once.