Handbook: generate screenshots with Playwright #140
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
MassiveDynamic/kataba#140
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Part of #137
Depends on #138.
What
A Playwright pipeline that generates the handbook screenshots, so they can be regenerated after UI changes instead of being retaken by hand.
Decisions (from the #137 grilling)
handbook/screenshots/ore2e/handbook/); it reuses the e2e infrastructure where sensible.npm run handbook:screenshots, not as part of the test run.handbook/, so the handbook build needs neither the app nor a database.Acceptance criteria
npm run handbook:screenshotsseeds, starts what it needs, captures and writes PNGs to a stable path inhandbook/Implemented in #144:
npm run handbook:screenshotsseeds a makerspace example instance into kataba_e2e (as a backup, restored like one), builds and starts kataba on port 3200 and writes 30 PNGs tohandbook/docs/assets/screenshots/with stable names (light mode, English, 1280 × 800, Europe/Berlin). How and when to regenerate is in README › Handbook › Screenshots.