The QR one-pager

Use with: build-website. Resume line when done: Built the QR landing page for {club}'s recruiting table — scanned by visitors at {event}

Brief

Your club gets a table at the fair, and the table gets a QR code. This is the page the code opens: one screen that says what the club does, when it meets, and how to join. It has to work on a stranger's phone in the three seconds before they lose interest, and it has to be live before the fair starts.

Personalize

• The club and the fair. A real club with a real tabling date: the school activities fair, an open day, a community event. The deadline is fixed, which is the point.
• The sponsor's sign-off. The club sponsor or president approves the page and the QR code before either is printed. Build it with the club so members recognize it as theirs.
• The one action. Decide what a visitor should do: fill the interest form, join the chat, show up Thursday. One action, made obvious. Everything else on the page supports it.

Milestones

1. Agree the content and the one action with the club's leadership.
2. One screen live at a URL: what, when, where, how to join. No scrolling required for the essentials.
3. The join action wired up and tested end to end from a phone.
4. QR code generated, test-scanned from three different phones, printed on the table sign or flyer.
5. Sponsor and president sign off; page is live before fair day.
6. Fair day: the code gets scanned by visitors. Afterward, record how many joined or signed up. Final README.

Done means

• Live URL responding; essentials visible without scrolling on a phone
• Sign-off from the sponsor or president recorded in the README
• The QR code was printed, displayed at the fair, and scanned by people outside the club
• At least one person joined or signed up through the page, noted in the README
• Any photo on the page was taken with the consent of the people in it
• At least 8 commits across at least 5 distinct days, authored by you
• SESSIONS.md has an entry per session, written by you