Carpool rota

Use with: build-website. Resume line when done: Built {project_name}, the driving schedule {n} families run their carpool on — live at {url}

Brief

Who drives to practice which day, this month and next, posted where every family can see it. The rota itself is agreed by the parents; your job is to make the agreement visible, current, and impossible to misremember. When a driver swap happens, the page changes the same day.

Personalize

• The carpool. A real recurring run: practice, rehearsal, weekend games. You know the families because you are in one of the cars.
• The parent in charge. One parent already coordinates this, probably by group text. They are your source for the schedule and they approve the page before other families get the link.
• What a row needs. Date, driver, pickup time. Ask the parents what else they always have to ask about, and include only that.

Milestones

1. Get the current arrangement from the coordinating parent and their yes to putting it at a URL. Agree what stays off the page; phone numbers and addresses likely stay in the group text.
2. This month's rota live at a URL, checked by the coordinator.
3. Next month added once the parents settle it.
4. A visible "last updated" date, so families can trust the page is current.
5. Link shared to the parents' group chat by the coordinator.
6. First swap handled: a driver changes, the page updates the same day, and the chat gets a one-line heads-up. Final README.

Done means

• Live URL responding; readable on a phone in a parking lot
• Coordinator's sign-off recorded in the README
• Parents received the link and at least one has checked the page instead of asking the chat, noted in the README
• A schedule change was reflected on the page the day it happened
• No phone numbers or home addresses on the page
• At least 8 commits across at least 5 distinct days, authored by you
• SESSIONS.md has an entry per session, written by you