{% extends "mobile/base.html" %} {% load i18n lucide %} {% comment %} M2 -- design_handoff_rosterchief_platform/README.md's M2 section, "answer for several". See EventDetailView's own docstring (mobile/views.py) for the judgment calls: no event photos, no Kit/dressing-room fields (the Event model has none), squad response is counts-only (never who answered what). The hero's background is the club's own generic event photo (Club.event_background, set on the identity page) shown in black & white under a dark gradient -- individual events have no photo of their own, so this is the one club-wide stand-in -- falling back to a plain dark background when the club hasn't uploaded one. The per-person In/Maybe/Out forms below are hx-boost="false" -- Alpine owns the toggle between this row's two sibling forms (buttons vs. the Out reason prompt), and having htmx *also* intercept the submit broke both. A real navigation for a write action is a fine trade; hx-boost's value is in link-to-link browsing, not every POST on the page. {% endcomment %} {% block content %}
{% trans "You're confirmed to referee this game." %}
{% else %}{% trans "You're eligible to referee this game -- are you in?" %}
“{{ answer.attendance.note }}”
{% endif %} {% endwith %} {% endif %}{% trans "No one you manage is invited to this event." %}