github-samples / github-samples/tailspin-toys

Add a publisher page listing that publisher's games

Open
#5 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
8
Forks
53
Avg merge
20h 1m
Merged PRs (30d)
4

Description

When a backer likes a game, a natural next step is to see what else the same publisher has made. Adding a dedicated, prerendered page for each publisher that lists their games improves catalog navigation. The data model already links games to publishers, so this is a focused addition that follows the existing dynamic-route pattern used for game detail pages.

Acceptance criteria

  • Each publisher has a prerendered page (using getStaticPaths() + export const prerender = true) listing all of their games
  • The page shows the publisher name and description, and reuses the existing game card for the listing
  • Publisher names on the game card and/or game detail page link to the publisher page
  • The page follows the project's styling and accessibility guidelines and includes data-testid attributes
  • A data-access helper returns games for a given publisher with unit test coverage, and Playwright e2e tests cover the publisher page

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by finding the existing dynamic route for game detail pages, the game card component, and the publisher-linked data model. Add the prerendered publisher route with getStaticPaths(), implement and unit-test the publisher game lookup, then run the existing unit and Playwright test suites to verify links, accessibility attributes, and the complete publisher listing.

Written by the indexing model from the issue text.

Assessment

Tech stack
playwright, typescript
Domain
full-stack, testing-qa, web-dev
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.