Website Redesign 1 / a001-REDESIGN.mdSep 13, 2026

The site redesign — state, decisions and where everything is (2026-09-13)

Read this before touching the Reading theme, the reader, the collections or the notebook. It is the handover from the session "Website Redesign 1" (2026-09-12/13, omni, gated log): what was decided and why, what was built and where, what is gated, what is known to be missing, and how to test it. PLAN.md's top three sections (site_next, the reader, phase B) are the implementers' own notes and go deeper on code; this file is the map.

1. What this is, in one paragraph

The owner wants a327ex.com to feel organized and purposeful instead of a feed, with books presented Kindle-like (two facing pages, horizontal turns) and books and games mixed. The thread produced: a 51-mockup board (Fable + Astra), a codified dark theme kit (THEME.md + eight sheets), and three Opus 5 implementation runs that built the whole thing into the renderer as an OPT-IN theme called Reading (site_next in code). Nothing about the default site changed for visitors. The redesign is committed (be030a7 and the two commits after it) and deployed, but gated: visitors on the web cannot select the Reading theme.

2. Where things are

WhatWhere
This maprenderer/REDESIGN.md
Implementer notes per run (code-level)renderer/PLAN.md, top three sections
The theme kit (authoritative values)renderer/reference/site-theme-2026-09-13/THEME.md + sheets 01-*.png … 08-*.png, index.md
The 51 mockups and the boardrenderer/reference/redesign-2026-09-12/ (gallery.html, index.md, index-2.md, web/*.jpg; the PNGs are local-only, gitignored)
The Ricochet exemplar the kit copiedrenderer/reference/ricochet-exemplar/ricochet-design.md (sheets local-only; originals on Z:\2025-2026\code\a327ex-linux-2026-09\from-hdd\Ricochet\reference\)
Verification snapshots (local-only)renderer/reference/site-theme-2026-09-13/snaps/, snaps-reader/, snaps-collections/
The delegation packets and reportsAnchor/workflow/delegate/runs/20260912-site-redesign-astra-opinion/ (Astra: discussion, images, kit; thirteen turns), 20260913-site-theme-build/, 20260913-site-reader/, 20260913-site-collections/ (Opus 5; each has brief.md = the contract and report.md = what was done, with every decision the implementer made)
New renderer modulesrenderer/reader.lua, renderer/works.lua, renderer/collections.lua, renderer/notebook.lua
Changed renderer filestheme.lua, main.lua, elements.lua, canvas.lua, homepage.lua, sidebar.lua, search.lua, tools/build-web.sh, tools/deploy.sh

3. The design conclusions (why things are the way they are)

From the Fable/Astra discussion (round two settled most of it; the mockups tested it):

  1. Choosing, reading sequentially and consulting are the governing distinction, not "stock versus flow". The front door is for choosing; the reader is for sequential reading; logs plus search are for consulting. That is why logs still scroll while stories, essays and the notebook page.
  2. Works get lasting homes. A book and its game are one work; the home holds the thing, its development history (the log series) and related essays. This is the seed of the future "one story = novel + game" presentation.
  3. Pages are windows onto the single-column layout. No second layout engine: the reader computes break offsets at text-line and element boundaries and draws each page by translating and clipping the column. Every element draw, selection, find and link hit-test keeps working in column coordinates. This is the architectural decision that made the build cheap and safe.
  4. The round-one readers looked "lacking" because their pages were empty. Real text at a book measure in the same chrome reads as a book. Pages must be full.
  5. Position addresses and citation addresses are different things. The reader remembers a place by element-and-line ordinal (per device); page numbers are never in URLs; persistent block ids for public citations are future work.
  6. Gold locates, blue acts. Gold is only for the current item, entry ids and progress. Artifact and replay links became blue under the theme.
  7. The notebook is a book whose chapters are months (mockup 34): the untitled posts paged in the reader's chrome, newest first, days as the contents overlay.
  8. The daily broadsheet was dropped (a day is an arbitrary layout budget) in favor of the paginated notebook.
  9. Instant cut on page turn, no curl, no paper. Wheel flick turns one page (debounced); edge zones only in the free outer margins; clicking on a page never turns it.
  10. Mock-up decisions the owner made (2026-09-12): front door = image 5 (works + notebook column), reader = 7 (then 28 v2), notebook = 12/34, work homes 15/16/40/41, logs 17/45, replay 21/42/48. The dark theme of those images is the theme. He said the sidebar is unnecessary and text can be smaller.

4. The theme (run 1: 20260913-site-theme-build)

5. The reader (run 2: 20260913-site-reader) — renderer/reader.lua

6. Collections, homes, front door, notebook, log frame (run 3: 20260913-site-collections)

7. The gate

Visitors on the web must not see the in-work site. theme_gate_open() in main.lua (next to THEME_ORDER) is true on the desktop build and on a web device holding the admin token (pageviews_admin()); otherwise the F2 cycle and the stepper hold Dark / Light, a persisted site_next is clamped back to Dark at boot (settings_load), and the collection routes land on the homepage. To ship the redesign, remove the web condition in that one function. The admin token is polled from web_boot_param('adminToken') every 60 frames, so on an admin device the first boot may clamp a persisted Reading to Dark once; re-select it.

8. How to see it (desktop)

  1. cd a327ex-site\renderer then run.bat (or A327EX_THEME=next run.bat).
  2. F2 until the theme reads Reading, or settings > Theme > Reading. Settings > Reading layout: Pages (default) / Scroll.
  3. Front door; the top line; Works > a home; Notebook (months strip, Dates overlay, gold ids); Essays; Experiments; AI Logs (click a cell); Search "snkrx"; a log page's series frame; a story or essay in the reader (arrows, Space, wheel flick, edge zones, Contents, the ending, resize below 1120 for one page).
  4. F2 back to Dark: the old site, unchanged.
  5. renderer/positions.lua holds remembered places (delete to clear the Continue band).

9. How to verify mechanically (never by running interactively)

10. What to do next (suggested order)

  1. The owner judges the build in run.bat and lists changes.
  2. Server-side routes and crawler HTML for /works, /works/<slug>, /notebook, /essays, /experiments, /logs (server/content.lua + server.lua + seo.lua), so a hard reload works and crawlers see the collections.
  3. The converter's untitled flag (one line in tools/convert.lua serialize()).
  4. The game hosted inside its work home (game_host.lua: it paints over the page when the host is not the page itself).
  5. Mobile: the hamburger's sections under the theme; selection and find on the collection pages; the Aa popover; persistent block ids for citations; the edge-preview tooltip.
  6. Cover art per work (the 64x96 typographic cover breaks long titles by character).
  7. Ship: remove the web condition in theme_gate_open(), or make Reading the default.

11. How the work was done (for the delegation record)

Fable directed; Astra (Codex, gpt-6-astra, xhigh) did the discussion rounds, all 59 images and THEME.md in one thread (anchor delegate followup now drives such threads); three Opus 5 subagents at extra effort implemented under packets (brief + scope + stop conditions + verification + report), each reviewed by Fable through the diff, a re-run of the checks and the headless snapshots. Each run's report.md lists every decision the implementer made on its own; brief.md is what it was asked. The mockup board is gallery.html in the mockups folder (also published as a claude.ai artifact during the session).

Settings