Skip to content

FTC-23511/website

Repository files navigation

Seattle Solvers — Team Website

Public website for Seattle Solvers, FTC Team 23511 (Sammamish, WA). Live at https://ftc-23511.github.io/website/.

Built overnight as a one-shot by Claude (Fable 5) from the spec in docs/SPEC.md — see PR #1 for the full build record and fact sources.

Stack

  • Next.js (App Router) + TypeScript strict + Tailwind CSS 4 — no other runtime dependencies, no backend, no database.
  • Static export (output: 'export') deployed to GitHub Pages by .github/workflows/deploy.yml on every push to main. The workflow runs the full verify gate first — a red verify blocks the deploy.
  • basePath/assetPrefix are "/website" (Pages sub-path). If the site moves to a custom domain, set both to "" in next.config.ts.

Working on it

pnpm install
pnpm dev       # http://localhost:3000/website (note the /website prefix)
pnpm verify    # the gate: typecheck + lint + format check + build

pnpm, not npm. Run pnpm verify before pushing; CI runs the same gate.

Where things live

What Where
Every word and fact on the site content/ — one file per page, source-commented. Edit content here, never in pages. See docs/UPDATING.md.
Class signup open/closed toggle content/classes.ts (registrationState)
Pages (one folder per route) app/about/, classes/, robots/, outreach/, sponsors/, resources/
Design tokens (colors, accent, motion) app/globals.css
Shared components components/ (Nav, Footer, Reveal, primitives)
Spec / design intent docs/SPEC.md
Non-programmer update guide docs/UPDATING.md
Work queue + status docs/BACKLOG.md
Automation rules docs/ROUTINE.md + CLAUDE.md

Content rules (important)

Nothing on the site is invented. Facts come from public sources (FTCScout, the team's own published pages) and are cited in the content/ files. Gaps are marked PLACEHOLDER in source. Pending human input: member photos + full roster, robot imagery, sponsor logos, sponsorship packet PDF link, interest-form URL confirmation — search the repo for PLACEHOLDER to find every slot.

Picking up where this left off

  1. Read CLAUDE.md, then docs/BACKLOG.md — the top of "Next up" is the next task. docs/SPEC.md is the quality bar.
  2. The repo works with Claude Code out of the box: /run-routine ships the top backlog item end to end; /prep-backlog queues work; /human-task-list lists what needs a person.

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors