Hackathon night · 2026-08-27

Logistics — work tracking board

Same idea as the Automatica kanban. Every card is a releasable increment — the site should still look working when the card lands. Push to main deploys the site and the API. To-do and done lists have their own pages (to do, done) so this board stays short. Filter by person with the chips, the hour cards, or a row in Who’s who. Click a card for the full brief (or share #t-04). Board edits: python scripts/update_board.py.

Showing everyone.

📋 Site + API deploy from push to main. Reeve, Lewis, and Noah have the front end locally; Reeve and Noah have the API too. Connor still proves the GitHub loop, then the map cards.
To do13 · 17.5h
13🌱
Lewis: get the back end running locally
clone api · venv · uvicorn · /health
1hLewis
14🌱
Lewis: GitHub edit → run → push (site repo)
Tyneside-Software/hackathon-site
0.75hLewis
17🧭
Reeve: GitHub edit → run → push (API repo)
Tyneside-Software/hackathon-api
0.75hReeve
21🧭
Reeve: start script for front end and back end together
one command, two processes, no asking the AI
1hReeve
13
All to-do cards

9 more · all 13 →

In progress0 · 0h

Empty on purpose. Pull a Ready card and ship it.

Done11 · 13.5h
11
All done cards

11 cards · 13.5h · archive →

Who’s who

Hours are every card attributed to that person, whichever column it sits in. Click a row to filter the board.

OwnerClaimed workHours
🧭 Reeve Reeve: get the front end running locally (0.5h, done) · Reeve: get the back end running locally (1h, done) · Reeve: GitHub edit → run → push (API repo) (0.75h) · Reeve: start script for front end and back end together (1h) · Demo seed: 5 Tyneside waypoints + named run (1.5h) · Map with clickable / draggable waypoints (3h, ready) · Run the API locally and hit /health (1h, done) 8.75h
Connor Connor: get the front end running locally (0.5h) · Connor: GitHub edit → run → push (site repo) (0.75h) · Job list beside the map (seed Howden-shaped jobs) (2h) · Route calculation between waypoints (3h, ready) · finished push and pull (0.5h) 6.75h
🏗️ Michael Site + API deploy on push to main (2h, done) · Cloud Run API live + CORS for Pages (4h, done) · Michael: GitHub edit → run → push (both repos) (0.75h) · Persist routes on the API (replace localStorage) (4h) 10.75h
🌱 Lewis Lewis: get the front end running locally (0.5h, done) · Lewis: get the back end running locally (1h) · Lewis: GitHub edit → run → push (site repo) (0.75h) · Save routes in the browser (localStorage) (2h) · Local “who am I” account (name in the browser) (2h) · Serve the site locally (0.5h, done) · Desktop home in Tyneside style (2h, done) 8.75h
🔧 Noah Noah: API version on / and /health (0.5h, done) · Noah: get the front end running locally (0.5h, done) · Noah: get the back end running locally (1h, done) 2h

How a card ships

  1. The increment is visible on the running site (not a branch of theory).
  2. Home, Map, and Board still load if the new thing is half-finished — fallbacks, never a blank page.
  3. Move the card to Ready to demo when someone else can click it without a briefing. The brief on the card is that briefing.
  4. Move a card with python scripts/update_board.py done 12 (or move 07 doing) — do not hand-edit the kanban HTML.
  5. LocalStorage is still the persistence story until card 11. The live API deploys from main.

GitHub loop (cards 14 · 17 · 19 · 20)

Do this on the Tyneside-Software repos, not personal forks unless you have been told otherwise. Full clone-and-run steps (and the usual Windows fixes) live on Onboarding.

  1. Clone (or pull) hackathon-site and/or hackathon-api as sibling folders.
  2. Run both: .\start.ps1 in the site repo (or .\serve.ps1 for the site only, and uvicorn on :8080 for the API).
  3. Make a tiny visible change (your name in a comment, README line, or a harmless label).
  4. Confirm it still runs.
  5. git add · git commit · git push origin main.
  6. Check the commit on GitHub. Then move your card to Done.