BikeControl (SwiftControl)
使用 Zwift Click、Zwift Play、Shimano Di2 或任何藍牙控制器，搭配 MyWhoosh、Rouvy、Zwift 等。iOS、Android、Windows、macOS 均可免費試用。
AI 翻译
尚未检测到更新。GitHub 发布版本后会显示在这里。
按最近已完成的 8 小时观测回合间的 GitHub 星标增量排序
使用 Zwift Click、Zwift Play、Shimano Di2 或任何藍牙控制器，搭配 MyWhoosh、Rouvy、Zwift 等。iOS、Android、Windows、macOS 均可免費試用。
AI 翻译
个人 GitHub 账号下公开仓库的所有者可以登录并验证所有权，自行管理介绍，无需管理员批准。
登录并生成验证文件，在 30 分钟内将其提交到此仓库的默认分支。其他分支或分叉仓库中的文件无效。然后在下方检查文件，即可无需管理员批准直接管理项目。请保留文件以维持管理权限。
如需登录，将前往登录页面。登录后请回到此处，再次点击所选的验证按钮。
在项目文件夹中运行 /nomorevibe verify，即可验证所有权并自行管理介绍。
一分钟完成验证正在加载完整 README。 以下为已保存的摘录。
The frontend of PodiumCall: a website that predicts the podium for every discipline at the 2026 Wanda Diamond League Final. It draws the predictions, standings, and athlete analytics that come from the Python API in a separate repo, athletics-predictor.
A read-only React app. Every number on it (podium probabilities, qualifying standings, head-to-head records, season form) is fetched live from the API. The frontend works nothing out for itself and stores no data of its own. It predicts podium membership (top 3), not the winner.查看完整 README ↗The frontend of PodiumCall: a website that predicts the podium for every discipline at the 2026 Wanda Diamond League Final. It draws the predictions, standings, and athlete analytics that come from the Python API in a separate repo, athletics-predictor.
Live: https://podiumcall.vercel.app
A read-only React app. Every number on it (podium probabilities, qualifying standings, head-to-head records, season form) is fetched live from the API. The frontend works nothing out for itself and stores no data of its own. It predicts podium membership (top 3), not the winner.
Landing · Dashboard (the surest calls) · Track & Field (per-discipline tables) · Discipline detail (field depth + head-to-head) · Athlete profile (career, form, rivalries) · Qualifying (DL standings vs the cut) · Stats (performance index) · Projections · Schedule.
You'll need Node.js and the API running (see the athletics-predictor repo).
npm install
npm run dev # http://localhost:8080
By default the app calls the API at http://localhost:5000. To point it somewhere else, use an env var (below).
All of these are optional and get baked in at build time (VITE_*), so changing one means a redeploy. Copy .env.example to .env.local to set them locally.
| Var | Purpose |
|---|---|
VITE_API_BASE_URL | Where the API lives (default http://localhost:5000) |
VITE_SITE_URL | The site's public origin. Turns on canonical URLs, JSON-LD, and the sitemap |
VITE_GOOGLE_SITE_VERIFICATION | Renders the Search Console verification tag |
Auto-deploys from main. Two things here are specific to Vercel:
NITRO_PRESET=vercel has to be set as an env var. The platform overrides the nitro build target in vite.config.ts, and this env var is what actually picks the Vercel output.vercel.json holds the security headers and the Content-Security-Policy. (public/_headers is Cloudflare-only, and Vercel ignores it.) The CSP is a whitelist, so any new external origin (a new font, an image host, analytics, a moved API) has to be added there or the browser blocks it.DESIGN.md (the "Track at Golden Hour" tokens and rules)Not affiliated with World Athletics or the Wanda Diamond League.