README screenshots and an optional public demo instance #136

New issue

Open

opened 2026-09-05 01:37:31 +00:00 by claude-bot · 0 comments

claude-bot commented

2026-09-05 01:37:31 +00:00

Contributor

Split out of #63, which delivered the two parts I could do properly: the in-process simulator (DEMO_MODE=true) and the demo seeding. Two checkboxes remain, and both need a human.

Screenshots / GIF of the calendar, day panel and scheme editor

I can generate these but I cannot verify them. Playwright is already set up for the E2E suite, so capturing PNGs of a demo-mode instance is mechanical. What I cannot do is look at the result and tell whether it is a good screenshot — whether the layout held, whether the colours read well at that size, whether the crop shows the thing it is meant to show, whether it looks like software someone would want to run.

Committing images I cannot see, to a README whose job is first impressions, is the one place where "it produced output" is furthest from "it works". So this needs someone to run it and look.

DEMO_MODE=true now makes that easy — the calendar has colour in it and the review queue has content, so a screenshot taken against a fresh demo install is representative rather than a blank grid.

Year calendar
Day panel with a scheme selected
Scheme editor (now with the palette-from-image and plain-language controls from #17 / #22)
Optional: a GIF of the virtual-strip preview animating (#14), which is the thing hardest to convey in stills

Optional: a public read-only demo instance

DISABLE_AUTH=true plus a viewer-only role, behind DEMO_MODE. This is a hosting decision rather than a code one — it needs a box, a domain, and a view on what happens when someone finds it. Worth doing only if public adoption is actually a goal.

One thing to check before pointing DNS at anything: a public instance would be a write-capable surface unless the role gating is right. Quick push and the remote page (#24) are admin-only, but that is enforced by role, not by demo mode — DISABLE_AUTH=true without a viewer-only default would hand every visitor the lights.

Split out of #63, which delivered the two parts I could do properly: the in-process simulator (`DEMO_MODE=true`) and the demo seeding. Two checkboxes remain, and both need a human. ## Screenshots / GIF of the calendar, day panel and scheme editor **I can generate these but I cannot verify them.** Playwright is already set up for the E2E suite, so capturing PNGs of a demo-mode instance is mechanical. What I cannot do is look at the result and tell whether it is a *good* screenshot — whether the layout held, whether the colours read well at that size, whether the crop shows the thing it is meant to show, whether it looks like software someone would want to run. Committing images I cannot see, to a README whose job is first impressions, is the one place where "it produced output" is furthest from "it works". So this needs someone to run it and look. `DEMO_MODE=true` now makes that easy — the calendar has colour in it and the review queue has content, so a screenshot taken against a fresh demo install is representative rather than a blank grid. - [ ] Year calendar - [ ] Day panel with a scheme selected - [ ] Scheme editor (now with the palette-from-image and plain-language controls from #17 / #22) - [ ] Optional: a GIF of the virtual-strip preview animating (#14), which is the thing hardest to convey in stills ## Optional: a public read-only demo instance `DISABLE_AUTH=true` plus a viewer-only role, behind `DEMO_MODE`. This is a hosting decision rather than a code one — it needs a box, a domain, and a view on what happens when someone finds it. Worth doing only if public adoption is actually a goal. One thing to check before pointing DNS at anything: a public instance would be a **write-capable** surface unless the role gating is right. Quick push and the remote page (#24) are admin-only, but that is enforced by *role*, not by demo mode — `DISABLE_AUTH=true` without a viewer-only default would hand every visitor the lights.

claude-bot changed title from README screenshots and an optional public demo instance</title> <parameter name="body">Split out of #63, which delivered the two parts I could do properly: the in-process simulator (DEMO_MODE=true) and the demo seeding. Two checkboxes remain, and bot… to README screenshots and an optional public demo instance

2026-09-05 01:37:41 +00:00

claude-bot added the

area/frontend

priority/low

type/feature

labels

2026-09-05 01:37:44 +00:00