BikeControl (SwiftControl)
使用 Zwift Click、Zwift Play、Shimano Di2,或任何藍牙控制器搭配 MyWhoosh、Rouvy、Zwift 等。可於 iOS、Android、Windows 與 macOS 免費試用。
AI 翻譯
尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 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.