ryan
d005080aca
Hosts can optionally cap total attendance (RSVPs + plus-ones) when creating an event. Capped events require guests to log in via the existing email code flow; RSVPs are tied to accounts and deduped per user. The event page shows spots left and replaces the form with a full notice when the cap is reached; the server rejects over-cap RSVPs and edits with 409 as a race backstop. Also threads a safeNext-validated ?next= param through the login and name-setup flow so guests land back on the event after signing in. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
26 lines
831 B
HTML
26 lines
831 B
HTML
{{template "layout" .}}
|
|
|
|
{{define "title"}}bbq — your name{{end}}
|
|
|
|
{{define "content"}}
|
|
<div class="event-header">
|
|
<div class="event-tag">Account</div>
|
|
<h1 class="event-title">What's your name?</h1>
|
|
<p style="font-family:'DM Mono',monospace;font-size:0.8rem;color:#555;margin-top:8px;">
|
|
This will be used to autofill your name when you RSVP or claim a slot.
|
|
</p>
|
|
</div>
|
|
|
|
<div class="claim-form-wrapper">
|
|
<form method="POST" action="/account/name">
|
|
{{if .Next}}<input type="hidden" name="next" value="{{.Next}}">{{end}}
|
|
<div class="form-row">
|
|
<label>Name</label>
|
|
<input type="text" name="name" placeholder="Your name" required autofocus
|
|
value="{{if .User}}{{.User.Name}}{{end}}">
|
|
</div>
|
|
<button class="btn-submit" type="submit">Save ↗</button>
|
|
</form>
|
|
</div>
|
|
{{end}}
|