← All project architectures

How Woodhouse works

A window into
the work.

Woodhouse brings independently run games, music and tools into one place. We check the evidence, edit what is useful and publish a dated account that leads you to the real product.

From project work to a public page

Review is the step that makes material ready to publish.

  1. Projects make things

    Each product owns its experience, source, artwork and releases.

    Evidence enters review
  2. We check and edit

    Check what actually works. Choose the story. Remove private material.

    Explicit publication decision
  3. Keep a public record

    Approved summaries, evidence, media and review dates live in the editorial system.

    Published content only
  4. You read and explore

    Woodhouse serves the page. Follow its links to try the independent product.

    Explore the projects →

Private inputs need review. An editor can derive a public-safe summary from private work. Original issue bodies, conversations and credentials stay outside public content; they have no direct publishing route.

Editable technical diagram (D2 source) ↗

Who owns what?

Each part has a job.

Woodhouse connects the portfolio. Each game, station or tool keeps control of its own product and release decisions.

See useful connections in the Factory →
The independent products
The places you play, listen or create. Their sites own current product identity and artwork.
GitHub
The authority for source code, issues and pull requests. Many repositories are private; Woodhouse publishes reviewed summaries.
Editorial review & EmDash
Editors decide what is safe and useful to publish. EmDash, the content system, stores structured records and their publishing state.
Astro & Cloudflare
Astro supplies the page design. A Cloudflare Worker reads published records and renders the public page; static assets are delivered alongside it.
Your browser
Displays the page and runs its local interactions. Following a product link takes you to that product's own experience.

Reading the evidence

A date tells you what was checked.

The latest portfolio snapshot was reviewed 12 November 2026. Project states belong to that review. Loading this page today does not verify a new release or move a project's review date forward.

New evidence needs another editorial review. Earlier editions remain available as history.

What visitors can access

Published pages, public evidence, approved images and read-only agent views. The live publication keeps the editorial office, authoring API and draft previews closed.

What the numbers mean

Analytics has a separate, limited collection endpoint. Its published aggregates explain their coverage; a click, a product visit and a useful action are different measurements.

Read the publishing principles →

Under the page

The technical details are here when you need them.

What happens at build time, and what happens when I visit?

A code release builds the page templates, styles, scripts and static images. On a server render, Astro queries published EmDash records. Cached pages or query results may be reused, so a request does not always make a fresh database read.

D1 stores editorial records. R2 stores approved editorial media. Existing analytics tables and their limited collection endpoint are separate from CMS authoring; D1 is not an empty or editorial-only database.

This production release exposes the reading surfaces. Editorial access and publishing schedules are gated separately; installing a CMS does not mean its public authoring routes are open.

EmDash's published-content and rendering contract ↗

Where do product images come from?

Current product artwork follows the producer's own sharing metadata. A bounded request-time read checks approved product destinations and caches the result for five minutes. If that read fails, the last resolved image or reviewed record remains available. This presentation refresh does not change the reviewed project status.

Optional Woodhouse campaign images and dossier illustrations keep their own credits. An image failure must not present a Woodhouse illustration as the producer's canonical art.

Browse the artwork and its sources →

What can the public agent view do?

Agent Reception makes the same reviewed public information easier for software to read. It cannot query private repositories, run tools or publish an update. The authenticated editorial interface is a separate capability.

Visit Agent Reception →