ZacharyZhang-NY
faf0987cf8
The build fetches showcase.lock's commit and runs the catalog's own validator. /showcase/ lists featured apps first, then the rest by newest or stars, with categories and search; /showcase/<id>/ shows previews, links and the README. The header drops its sound switch below 414px so the fourth link fits.
1.3 KiB
1.3 KiB
Showcase round, 2026-10-04
An apps page like gpui-kit.com/apps, fed by a public repo, ZacharyZhang-NY/Ely-GPUI-Showcases.
Choices, the user's: the catalog starts empty; the site fetches the repo at a pinned commit when it builds; categories and search, stars from CI, a detail page from the app's README, a featured order.
- S1 Plan: these lines, the T51 lines in
TASKS.md - S2 Repo · Catalog:
apps/<id>/manifest.json,featured.json, README, CONTRIBUTING;scripts/validate.mjswith tests - S3 Repo · CI: validate on every push and pull request; stars refreshed on main and weekly,
scripts/stars.mjswith tests - S4 Repo · Publish: the public repo on GitHub, pushed, CI green
- S5 Site · Data:
frontend/showcase.lockpins a commit;scripts/showcase.mjsfetches it, runs the repo's validator, renders READMEs, writes the catalog; dev, build and CI run it - S6 Site · List:
/showcase/, a Showcase link in the header, featured first, the rest newest then stars, categories with counts, search, the empty state, Submit - S7 Site · Detail:
/showcase/$app/, previews, links, platforms, stars, the README - S8 Site · Tests: unit tests for order and filters; Playwright for the page, the empty state and the link
- S9 Docs: AGENTS.md; acceptance, item by item