For whoever runs the board
Everything on this site is driven by one file. You do not need to know how to code — you need to be able to type carefully between quote marks.
| What | Where |
|---|---|
| Meal sign-ups, game notes | Manage page → Meal sign-ups |
| Games — add, edit, remove | Manage page → Schedule |
| Home page announcements | Manage page → Announcements |
| Phone list | Manage page → Contacts |
| Email, social links, deadlines | Manage page → Links & dates |
| Instructions and sponsor wording | Manage page → Page wording |
| The organizer passcode | Netlify → Environment variables |
| The web address | Netlify → Site details |
Add /admin.html to the site address, or use the
“Manage the site” link in the footer of any page.
You stay signed in until you close the browser tab.
Each section has its own Save button. A green bar confirms it worked.
Manage → Backup → Download backup saves one file containing the entire site — schedule, sign-ups, announcements, contacts, wording. If something goes wrong, Restore puts it all back. Worth doing before a big edit and again at the end of the season.
Manage → Backup → Clear all sign-ups empties every meal slot while keeping the schedule, contacts, and wording. Then use the Schedule tab to put next year’s games in. Do this in the summer, not mid-season.
Two families can’t claim the same game — whoever submits second is told it’s taken. Blank names are rejected. Contact details are stored but never shown on the public board, only in the organizer’s download. And if the server is ever unreachable, the site falls back to its last known copy and says so rather than showing an empty board.
Every page has a Print button that strips the navigation and prints clean. The Schedule and Team Meals pages also have a Download button that saves a spreadsheet of every game, who’s covering it, and what they’re bringing — handy for the cooler-side clipboard or for handing off to whoever takes this over next season.
Why this one needs a real deploy: the sign-up board runs a small piece of server code, and Netlify has to install it. A plain drag-and-drop of the folder publishes the pages but leaves the board offline — you’d see “the live board isn’t reachable”.
The reliable way: put this
folder in a GitHub repository and connect it to Netlify (Add new site →
Import an existing project). Netlify then rebuilds automatically every time
anything changes. Build command npm install, publish directory
. — both already set in netlify.toml.
Or from a terminal:
npm install -g netlify-cli, then netlify deploy --prod
from inside this folder.
ADMIN_KEY
environment variable and deploy once more. Until you do, Organizer mode will tell
you no passcode has been set.