F1ReplayTiming
Visualisation of real-time track data and telemetry synced to F1 replays.
A mayoral forecast, the polls behind it, and Toronto’s council and school-board races.
DataTypeScript · CSSGitHub @alexwolsonOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
Toronto 2026 municipal election poll tracker and ward model
Translation pending
Taken from the repository README
Loading the full README.
Read the full README ↗Static Next.js frontend for Toronto's 2026 municipal election guide. Production builds consume checksum-verified Results, Polling, and Backend GitHub Releases.
Install dependencies and run against the committed development fixtures:
npm ci
FEED_LOCAL_DIR=./fixtures npm run dev
Open http://localhost:3000 with your browser to see the result.
Run npm test, npm run lint, and npm run build before opening a pull request.
Fixtures are development/test artifacts and are never promoted to production.
For a design preview intended to reflect the current election, read the live
site's /data/source-manifest.json, then resolve its exact Backend tag with
BACKEND_RELEASE_TAG=backend-YYYY-MM-DD.N npm run vercel-build, then npm start.
This verifies and consumes the complete pinned release chain. A fixture preview
can omit newer polls and other released information; use it only for deliberate
offline or test scenarios. See the release guide below for provenance checks.
Do not deploy with a raw-GitHub URL or NEXT_PUBLIC_DATA_REVISION. Follow
the production release guide to resolve the immutable
release chain, verify its source manifest, deploy through Vercel, and roll back.