Skip to content

feat(www): add a showcase section and page - #15

Merged
kecan0406 merged 2 commits into
mainfrom
feat/www-showcase
Sep 30, 2026
Merged

kecan0406 merged 2 commits into
mainfrom
feat/www-showcase

Conversation

@kecan0406

Copy link
Copy Markdown
Owner

What changes

The landing page ends with a Showcase section that features the first site, and a new /showcase page lists every site with a slot for the next one. hackers.pub is the first entry (hackers-pub/hackerspub#408), with its cat motif beside the name (CC BY-SA 4.0, credited on the card).

Adding a site is meant to be easy:

  • Each site is one JSON file in www/showcase/, so two pull requests never touch the same lines.
  • A Vite plugin (virtual:showcase, like llms.ts) checks every file at build time. A bad entry fails pnpm build:www with the file and the field, e.g. showcase/x.json: "url" must be an https:// URL.
  • "Add on GitHub" opens GitHub's new-file page with an entry template (commented fields). GitHub forks the repository and opens the pull request, so nobody needs a clone.
  • An issue form (showcase.yml, labeled showcase) is the alternative for whoever would rather fill in a form. Logos go in a PR comment or the form, and we commit them.

Also: CodeCard now sits on a shared CodeFile, the footer is its own component, and the header and footer link to /showcase.

Checklist

  • pnpm format:check and pnpm check pass
  • Tests cover the changed behavior: no new tests; the change is site UI and a build-time check I exercised by hand (empty template, unknown field, missing image, leftover // comments)
  • README.md and the matching docs are updated: CONTRIBUTING.md has a showcase section
  • A changeset if the published package changes: not needed, no published file changes

After merging

  • The issue form and its "Add on GitHub" link only work from main; the showcase label already exists.
  • The prefilled new-file link uses GitHub's filename and value query parameters, which its docs do not describe. Click "Add on GitHub" once on the deployed page to confirm.

🤖 Generated with Claude Code

kecan0406 and others added 2 commits September 30, 2026 10:35
The landing page ends with a Showcase section that features the first
site, and /showcase lists every site with a slot for the next one.

Each site is one file in www/showcase/, checked at build time by a Vite
plugin (virtual:showcase). A contributor who edits it on github.com
learns from CI what to fix, and two pull requests never touch the same
lines. "Add on GitHub" opens GitHub's new-file page with an entry
template, which forks the repository and opens the pull request.

hackers.pub is the first entry, with its cat motif (CC BY-SA 4.0,
credited on the card). The header and footer link to the page.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Add a showcase issue form for whoever would rather fill in a form than
edit a file, an "Add a site to the showcase" section in CONTRIBUTING.md,
and a line in the pull request template that skips the code checklist
for showcase entries.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@vercel

vercel Bot commented Sep 30, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
solid-route-progress Ready Ready Preview Sep 30, 2026 1:46am UTC

@kecan0406
kecan0406 merged commit 5eccb81 into main Sep 30, 2026
6 checks passed
@kecan0406
kecan0406 deleted the feat/www-showcase branch September 30, 2026 01:47

This branch was successfully deployed

1 active deployment
Preview — 51d37c4d Deployed Sep 30, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant