Repository navigation
Optimize landing images and run frontend regression checks in CI - #97
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 50 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Cloudflare preview: https://pr-97-lanis-ui-preview.bennetjoanwegener.workers.dev Commit: This preview uses the live LANIS API. Changes made after signing in affect your real account. |
The landing page currently serves large PNG screenshots, and frontend CI does not run the existing account-data and timetable regression checks.
Generate lossless WebP variants before development and production builds, serve them through
<picture>with PNG fallbacks, and lazy-load the feature screenshots below the hero. The five screenshots shrink from 4,668 KiB to 2,696 KiB (42.2%) with identical decoded pixels. Generated files stay out of Git; original PNGs remain available for editing and fallback support.Add
npm testand run it before the CI build, including the existing deployment checks and a pixel-preservation test for conversion.Validation: frontend regression tests and TypeScript checking passed; browser verification confirmed all five WebP files loaded. Full UI build was not run because the repository's AGENT.md prohibits it.