The mailing list, RSVPs and email activity below are the current event’s. They are not kept for each event, so any other event shows only its own registrations.
📦 Packs
⚖ Troops — Baldwin
⚖ Troops — Five Rivers
🌎 Out of Council / No District
🚢 Ships · Posts · Crews
Contacts are the mailing list, shared by every event — not the people registered for the event picked above. That event’s people are on the T-Shirts and Troops tabs.
| Name | Troop | City | Position | RSVP | Status | Actions |
|---|
Campaigns are the emails sent from this board, shared by every event — not only the event picked above.
| Name | Subject | Status | Sent | Date | Actions |
|---|
When it is built, a camp director signs in and is walked, step by step on a calendar counted back from the event date, through everything done for Ride of the Headless Horseman in 2026, with every email, troop card, guide and flyer already filled in from the event’s own details. No Claude account and no access to Mark’s computer needed.
Until then, this page is the process. Each step says what already works on this board and opens it; the rest is marked coming soon.
1Name the event
Year, season and title (for example 2027 Spring — Top Scout Camporee), then dates, location, registration link and prices.
works todayNew camporee puts it in the event picker, saves its profile, and can start its budget lines and sponsor list from an earlier camporee.
Still by hand: its public page and library card.
2Appoint the camp directors
Name and email for each director, tick the camporee they run, and email them a one-click sign-in link. They see only their own camporee.
works todaySettings → Directors → + Add director, tick the camporee, then Send invite.
3Set what each director may do
Per director: view · edit the event profile · upload files · edit the budget · import registrations · send email (with a daily limit) · publish to the public site, or have it approved first.
partlyToday: every director can view their camporee, and a director can be made a budget editor (Budget and Sponsors), as Ward is. Ask Mark for that.
Coming: the other permissions, as tick boxes on the Directors list.
The one place this camporee’s details are typed. The emails, troop cards and guide are to read them from here (coming soon), so a date or a phone number is changed once. It follows the event picked at the top of the page.
| Phase | Steps | Today |
|---|---|---|
| 1. Concept12–10 months before | Theme vote QR and results, pick the date, book the camp, fill in the event profile (the one place names, phones, dates and prices are typed). | partly |
| 2. Identity11–8 months before | Upload the patch (photo and vector), patch-maker request letter, flyer from a ready-made AI prompt, save-the-date, social graphics. | coming soon |
| 3. Registration set-up8–6 months before | Registration link and prices, flash-sale dates, the public event page and library card made from the profile. | coming soon |
| 4. Outreach6–2 months before | Import the Key-3 contacts, RSVP campaign and auto-drip, troop cards with the right message for each unit, call list, sponsor requests, staff recruiting. | works today |
| 5. Registration & money3 months before → close | Weekly registration upload, dashboard, budget with receipts and reimbursements, T-shirt order, patch count, supplies, close registration. | works today |
| 6. Program3 months → 1 week before | Stations and locations, colour groups, campsites, camp map, Leaders’ Guide (template → PDF → proof → publish), station leader guides, SPL packet, scoring. | coming soon done on Mark’s computer in 2026 |
| 7. Final weekthe last week | All-adults mailing with the guide, timed final reminder, printables (roster by unit, shirt and patch lists, check-in sheet), budget report to the team. | partly |
| 8. Afterafter the event | Sponsor thank-you letters, survey and theme-vote QR, photo upload, close reimbursements, archive to the library, roll over to the next camporee. | partly (thank-you status) · (reimbursements) |
A director sees the camporees ticked against their name — registrations, units, budget — and cannot change anything. Someone with nothing ticked sees nothing. They sign in with an emailed link; there is no password for them to choose or lose. Changes and revoking take effect immediately.
A complete backup is two downloads: (1) the database — all contacts, campaigns, recipients & email events — bundled with a full from-scratch RESTORE guide; and (2) all media & website content — every flyer, image, photo, video, PDF, page and source file, as one .zip. Together they are everything needed to rebuild from scratch.
The media & website .zip is the full repository (~760 MB — flyers, all camporee photos, videos, maps, patches, PDFs, the site pages and worker code). It downloads through this admin panel, so no GitHub sign-in is needed — just stay signed in here.
The database is copied to Cloudflare R2 (bucket mobilescouts) every day
at 5pm CT, keeping the last 30 days. This runs on its own — you don't need to
click anything. If a backup ever fails you get an email.
✅ Database backup (.json): the full D1 database — every table, every row (contacts, campaigns, recipients, email events). This is the only live state that exists nowhere else. Includes the embedded restore guide.
✅ Media & website backup (.zip): the entire GitHub repository — all flyers, photos, videos, maps, patches, PDFs, every site page, the admin panel and the worker code. This is all media and website content in one file.
🔗 Can't be exported (re-created from the guide):
- Cloudflare secrets (ADMIN_PASSWORD, RESEND_API_KEY) → write-only by design; guide says how to re-set them.
- Resend domain + DNS (DKIM/SPF/tracking CNAME/webhook) → every record listed in the guide.
Keep the database .json private (it contains everyone's contact info). Re-download it after any big change — e.g. before each campaign. The media .zip only needs re-downloading when you add new photos/flyers/pages.