Repository navigation
feat: generate README screenshots from the build - #53
Merged
Merged
Conversation
- The planner, dashboard heat strip and habit week strip still used hardcoded Portuguese abbreviations in the English UI. - Build the labels from the active locale (Intl for month/weekday names) so range headers and day initials follow the language switch.
- Test mode seeded Portuguese habits, transactions, notes and graph nodes even when the interface was in English, so screenshots and manual QA mixed languages. - Move the demo copy to `demo_*` message keys in both catalogs and read them through Paraglide, the same pattern already used by categories and domains. - Add habit history and a richer sample note so the test database shows streaks, a completed day goal and a meaningful note preview.
- The README needs desktop and mobile images that stay reproducible and never touch real data. - `npm run shots` checks/builds the static bundle, serves it locally and drives headless Chrome over CDP (same approach as the CSP harness, no new dependency). - Boots test mode with the English UI, navigates the app, hides dev-only chrome and captures the five states, then composes the 1600×640 banner and the 512×512 typographic logo.
- Replace the image placeholders with the logo, banner and the five screenshots produced by `npm run shots`. - Group the gallery as a desktop row (time, notes, finances) and a mobile row (dashboard, habits), with localized captions in both READMEs. - Point the docs index at the versioned `docs/assets/` directory.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The README still had placeholders for the logo, banner and screenshots, and manual captures would drift and mix languages. This adds a reproducible harness and wires the generated assets into both READMEs.
What
npm run shots(tools/shots.mjs): builds the static app if needed, serves it, drives headless Chrome over CDP (no new dependency), boots test mode in English and captures time, notes, finances (desktop) plus dashboard and habits (mobile).demo_*message keys so test mode follows the UI language; adds habit history and a richer sample note.Verification
npm run check— 0 errorsnpm test— 284 tests passednpm run build— oknpm run csp:check— 23/23 checks oknpm run shots— 5 screenshots + banner + logo regenerated and visually checkedNotes
ATLAS_CHROMEoverrides the path).