Everything you need to know
Your shortcut to the mission, who runs the platform, how data flows, and the tech powering the #NightTrainsForFuture movement.
Mission & Movement
What is the mission of this platform?
Back-on-Track built this hub to turn community night-train dreams into policy-ready evidence. Every action funnels people from Dream ➜ Community ➜ Pyjama Party so that #NightTrainsForFuture stays laser-focused on winning better sleeper routes across Europe.
Who is behind #NightTrainsForFuture?
The platform is stewarded by Back-on-Track Action Group volunteers and station coordinators across Europe. Strategy, data review, and press briefings are aligned with the wider Back-on-Track network and partners. You can read more on the About page.
Where does coordination happen?
All livestreams, safety updates, and last-minute decisions run inside our Discord HQ—look for the #nighttrainsforfuture channels. Join directly from the banner or head to the Community Hub.
Operations & Data
Is registration open?
Not yet—our CRM form is offline while Back-on-Track finalises the Europe-wide activation plan. The placeholder button on the Pyjama Party page explains the flow, and Discord announcements go out the moment HQ reopens the form.
Where does the reality layer data come from?
We use the official Back-on-Track night-train dataset to show current services. Dream routes are anonymised, aggregated in Supabase, and surfaced via theImpact Dashboard for advocacy.
How often is the data refreshed?
Dream submissions sync in near-real time; impact metrics refresh hourly; station readiness updates are reviewed nightly with station leads. If you spot an issue, drop a note in Discord or use the contact form.
Technology & Access
What is the tech stack?
The platform runs on Next.js 14 with the App Router, TailwindCSS, Supabase, Mapbox GL, and Playwright + Vitest for testing. Monitoring is handled via Sentry and custom analytics events.
Is the repository public?
Not yet—we are finishing stability and accessibility work before opening the repository. The plan is to make it public later in 2025 so local groups can fork or contribute more easily.
What about accessibility and localisation?
We follow WCAG 2.2 AA guidelines, provide keyboard-first navigation, and keep motion optional via reduced-motion settings. Internationalisation support is built with the t() helper and more locales will roll out closer to launch.