TunnelFlight Internal Docs

Documentation for the International Bodyflight Association platform — the system that manages members, skills, training, currency, bookings, and external integrations across the IBA’s wind-tunnel ecosystem.

This site is internal-only. If you can read it, you’ve already passed the access gate.

New here? Start at the Getting started zone

If you’re joining the team and have never opened a PR against this repo before, work through Getting started →. Four short pages covering local setup, the PR + commit conventions, the deploy-preview labels, and the docs-update flow. Designed for day-1 reading; ~1 hour from clean laptop to a merged PR.

Already onboarded? Skim the zones below to find what you need.

Where to start

Pick the section that matches what you’re trying to do.

Overview →

For anyone — staff, partners, new joiners, anyone evaluating an integration. Plain-English descriptions of what the platform does: members, skill levels, currency, bookings, safety training, the FuzeMetrix integration, and how the three runtime apps fit together. No code, no jargon.

Business logic →

For anyone reasoning about the rules — engineers, product, ops. The rules and lifecycle the platform enforces: skill levels, currency cycles, approval levels, logbook state, fees, tunnel booking rules. Framework-agnostic — “how the platform thinks” rather than “how a specific service implements it”.

Component zones — API · WWW · Tools · Admin · Mobile · Assistant

For the internal engineering team building each component. Implementation notes per deployable: architecture, auth, deployment, gotchas. Tools is the standalone disaster-recovery member- directory app — deliberately decoupled from api and www so tunnel staff can verify membership even when the main platform is down. Admin / Mobile / Assistant zones are reserved but not yet populated — they ship when their first doc lands.

Integrations →

For engineers working with our third-party connections — Fuzemetrix, Convergence, Tunn3l. Technical integration notes. Audience-level intros live under /overview/; business rules under /business-logic/integrations/.

Common tasks →

Operational runbooks. Step-by-step “I need to do X right now” guides — adding a supported country, rotating credentials, etc.

Infra →

Cross-cutting platform engineering. CI workflows, data storage conventions, request patterns, architecture (C4) diagrams.

Conventions →

Meta-docs about how we work. Page naming, doc-update process, authoring guidelines.

Knowledge graph →

Visual map of every page on this site + the code paths each one documents via the covers: / owns: frontmatter convention. Useful for “what’s connected to what” exploration and spotting gaps in business-logic coverage.

How this site is organised

Audience zones — /overview/ (non-technical) and /business-logic/ (rules and lifecycle).
Component zones — /api/, /www/, /admin/, /mobile/, /assistant/ — one per deployable.
Cross-cutting zones — /integrations/, /common-tasks/, /infra/, /conventions/.

Search (top of any page, or Ctrl/⌘ K) covers the whole corpus. New to authoring? Read the page naming convention first.

Maintenance

This site is built with Nextra and deployed to Cloudflare Workers. Source for every page lives under docs/app/... in the main monorepo — hit “Edit this page” on any page to send a PR.