Central Park Throughikers
Published since March 2026 · five of six routes have a maintainer · what a hiker sees is below, exactly as your own org's page would look.
The view that matters most
This is what a volunteer actually opens. Every admin screen in this tool exists to produce this one. Sam is a Throughiker who looks after the Ramble — she never sees a registry or a pull request, only her own paths, what hikers said about them, and the three things she can do today.
- No second login. She signed into the Throughikers' own site and arrived here.
- No jargon. Her section has a name, not an OBJECTID.
- Works with no signal. Reports queue and go when she gets back — on her laptop or her phone.
Lives at /my/tread — its own address, so the welcome
email and the org's own members area can both link straight to it.
Their sections
Their hikes, filterable, exactly as a visitor to their own site would get them — one widget, one behaviour. Narrow by region or length; the lengths are theirs, drawn from the sections they published.
Their workdays
Upcoming work, as their own visitors see it. A workday mirrored from an org's own calendar sends its signup to their form and says so — an org with a working calendar is not asked to abandon it.
Their coverage badge
One snippet, two shapes — a strip for a footer and a card for a donate page. Every figure comes from what they published and confirmed: miles from their registry, volunteers from their roster, and hours from the ones a supervisor signed off.
Three counts, and never a list. It does not say which sections nobody is holding — a hiker reading that would make a routing decision out of an organization's staffing problem. The coverage report that does say is inside the console, for the people who can act on it.
Everything above is one paste each. A div and a script tag, on the org's own page, reading the registry they already signed off. No cookies, no tracking, no OurHike branding they cannot remove, and it inherits their fonts and colours. If our servers are down their page still renders — the embed just does not appear.