Skip to content

docs(readme): reshoot the three README screenshots from the production UI - #320

Merged
MerciHanrim merged 1 commit into
mainfrom
docs/readme-screenshots
Oct 5, 2026
Merged

MerciHanrim merged 1 commit into
mainfrom
docs/readme-screenshots

Conversation

@MerciHanrim

Copy link
Copy Markdown
Owner

The three images the README shows predated the shared icons (#298), the storage gate and temporary sessions (#297) and the Temporary session button's new look (#319). They are reshot from the production UI. Documentation only: no app code, version or release note changes.

The images

File README Session Scene
hero-coffee.png the top image temporary the Coffee roastery Template with its three zone frames in view, three steps into a run, the Timeline below; the orange-bordered Temporary session button in the toolbar
gacha-overview.png Representative use cases personal the gacha Template run to its End (step 202), the Pickup rate Register selected, its expression read back in the Inspector
gacha-pickup-guarantee.png Representative use cases personal the Premium Pickup zone on its own after the same run, its Ceiling hits Pool selected
  • The hero image is the one taken in a temporary session, to show its button; the other two are a personal browser, so a temporary session does not look like the default.
  • The hero image's alt text now names the temporary session and its button; the other two still describe what is on screen.
  • File names, places in the README and sizes (1600 x 900) are unchanged. The toolbar's PREVIEW label is the product's own label and stays.

How they were taken

  • On the production deployment's deploy-hash origin (v0.17.2 · build 7d40cdf), whose page, scripts and stylesheet are byte-identical to production; nothing was done on production itself.
  • One fresh browser context per image, every other origin blocked (the only request blocked was Cloudflare's analytics beacon), 1600 x 900 at scale 1, light theme, English, reduced motion; driven through the page as a person would, with no page errors.
  • Shot twice: both runs gave byte-identical images.

Checks

  • npx tsc -b, oxlint, 3,077 unit tests and every check pass; check:change-declaration finds nothing built or shipped changed.

…n UI

The three images the README shows predated the shared icons (#298), the
storage gate and temporary sessions (#297) and the Temporary session
button's new look (#319). They are reshot from the production deployment
(v0.17.2 · build 7d40cdf, on its deploy-hash origin, byte-identical to
production), each in a fresh browser context with every other origin
blocked, at the same 1600 x 900 size, light theme and English as before.

- hero-coffee.png: the Coffee roastery Template, all three zone frames
  in view, three steps into a run, in a temporary session, so the
  orange-bordered Temporary session button shows in the toolbar; its alt
  text now says so.
- gacha-overview.png and gacha-pickup-guarantee.png: a personal browser,
  so a temporary session does not look like the default; the same scenes
  as before (the run to its End at step 202, the Pickup rate Register
  selected; the Premium Pickup zone alone with its Ceiling hits Pool
  selected). Their alt text still describes what is on screen.
- File names, places in the README and sizes are unchanged. The
  toolbar's PREVIEW label is the product's own label and stays.
- No app code, version or release note changes.
@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying cozy-loop-studio with  Cloudflare Pages  Cloudflare Pages

Latest commit: 6c13760
Status: ✅  Deploy successful!
Preview URL: https://ce951b7a.cozy-loop-studio.pages.dev
Branch Preview URL: https://docs-readme-screenshots.cozy-loop-studio.pages.dev

View logs

@MerciHanrim
MerciHanrim merged commit 9f0c90c into main Oct 5, 2026
10 checks passed
@MerciHanrim
MerciHanrim deleted the docs/readme-screenshots branch October 5, 2026 04:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant