Repeatable media capture
Product media should show the actual product. This site follows the noctune-docs approach: capture real interfaces, keep deterministic test data where possible, put browser/device framing in components, and verify assets before deployment.
Published assets and provenance
capture/manifest.json records the source repository, commit, source file, output file, and checksum for every imported asset. The iOS images come from the iOS repository; Dial stills and clips come from its device framebuffer workflow. Core capture provenance is recorded alongside the published asset.
pnpm media:import
pnpm media:verifyImport requires sibling product checkouts (or PRODUCT_ROOT pointing to their parent). The importer reads committed blobs at pinned revisions so unrelated working-tree changes cannot enter a release. Verification rejects missing files, Git LFS pointers, checksum mismatches, and invalid image dimensions.
Fresh Core browser capture
Use an isolated Core instance containing only disposable fixture data. Start it on loopback and run:
CORE_CAPTURE_URL=http://127.0.0.1:3000 pnpm exec node scripts/capture-core.mjsThe script only accepts a loopback origin, navigates the real UI, and captures the viewport with Playwright. It supplies hardware status, schedules, sleep, settings (gestures, HomeKit, MQTT, backup), storage, logs, calibration, and Autopilot diagnostics through committed synthetic transport fixtures, replaces the sensor WebSocket with synthetic wire-format frames, blocks tRPC writes, and reads all remaining data from disposable local databases. The development badge is hidden; the application UI is unchanged. Follow capture/README.md to start the isolated instance. The capture selects the Stepper preference and captures every app screen: each main section, the schedule editors, each Sleep range, every System tab, and every Settings section. Set CAPTURE_ONLY=core-gestures.png,… to recapture selected outputs while reviewing; partial runs skip the Health video and keep the last full run’s provenance files. Inspect every .capture/core-*.png before promoting it and updating the manifest. Record the source commit in capture/core-capture.json as well. Do not use real sleep histories or a live customer’s system for documentation capture.
Fresh iOS capture
Build the app on an iOS Simulator using a disposable mock backend. Navigate to the intended screen and capture:
xcrun simctl status_bar booted override --time '9:41' --batteryState charged --batteryLevel 100
xcrun simctl io booted screenshot .capture/ios-temperature.png
xcrun simctl status_bar booted clearFor a short demonstration, use xcrun simctl io booted recordVideo .capture/ios-demo.mp4, perform one task, and stop recording. Show only synthetic data. Keep the simulator’s status bar in the image; the PhoneFrame component supplies the outer frame without inventing UI.
Fresh Dial capture
Use the upstream tools/walkthrough.py on a test Dial with serial access. Its output includes PNG stills and MP4 clips. See Dial development. Preserve the device pixels and use the site’s DialFrame for the bezel.
Review and promote
- Inspect every image and play every clip. Check labels, selected side, test data, and private information.
- Keep controls visible and frame the product consistently. Browser framing belongs in
BrowserFrame, not in painted screenshot pixels. - Record the product revision, capture method, dimensions, and SHA-256 checksum in the manifest.
- Run
pnpm check, including static build and browser tests. - Review desktop and mobile rendering before merging. PRs run the same validation; pushes to
maindeploy the static output to Pages.
Clips are short, silent, and accompanied by a text description. Dial clips are user-controlled. The Health map clip is muted and loops automatically, with controls still available.
New-interface tour
The overview video and Stage/Base clips are captured from Core’s built-in demo at commit 2c28d2e571742842a8679779c41922310a0c03b7. The real interface runs in an isolated production build. Network calls to Pod APIs and external origins are blocked; all actions stay inside the in-browser simulator.
capture/interfaces.json lists captured routes and chapters. scripts/capture-interfaces.mjs records screenshots and live interactions, and scripts/render-overview.mjs adds original editorial captions beside the unchanged recordings. See capture/README.md in the site repository for the complete reproducible commands. Media entries carry source revisions, dimensions, and SHA-256 checksums. Base remains explicitly labelled experimental and simulated.