{% comment %} The club page's event list: upcoming events, then a little recent history. Shared by both the tabbed (BAP enabled) and untabbed layouts of club_detail.html so the two can't drift apart. Expects: upcoming_events, past_events, has_any_events, can_manage_auctions, club, club_ical_subscribe_url, club_ical_google_url, club_events_embed_path. Only ever use {% templatetag openblock %} comment {% templatetag closeblock %} blocks in here. Django's {% templatetag openbrace %}# … #{% templatetag closebrace %} form is single-line only; spread one over two lines and it renders straight onto the page for members to read. {% endcomment %}
{% if can_manage_auctions %} Add event Auctions are added automatically {% endif %}
{% comment %} Both buttons subscribe, so the club page keeps updating itself in the member's calendar. The one-time .ics download used to sit alongside them and was never the right answer — nobody wants a frozen snapshot of events that have already happened. One Google button: the club's own calendar when it's shared, otherwise Google's add-by-URL screen pointed at our feed. Two would be the same events twice. {% endcomment %} {% if has_any_events %} Google Calendar Apple Calendar or Outlook {% endif %}
{% if can_manage_auctions %} {% include "auctions/partials/club_events_embed_snippets.html" %} {% endif %} {% if upcoming_events %} {% else %}

No events coming up. {% if can_manage_auctions %}Add one so your members know what's next.{% endif %}

{% endif %} {% if past_events %}
Recently
{% endif %} {% if can_manage_auctions and unpromoted_auctions %}
Not promoted — only you can see these
{% endif %}