Skip to content

Post-Event Mode

Transition your event from active operations to a post-event archive where attendees can still access photos, documents, and polls.

Quick outcome

After your event ends, switch to post-event mode to preserve shared content while removing operational features. Photos, documents, and polls remain accessible. RSVPs, payments, schedule, and announcements are hidden from the public site. Admin access remains full for organizers.

Setup

Switching to post-event mode

Two ways to activate:

  1. Event admin: Navigate to /admin/settings and change Mode from active to post-event
  2. Platform UI: Navigate to /platform/events/[id] and update the lifecycle settings

Changes take effect immediately — no redeploy needed.

What changes

FeatureActive modePost-event mode
HomepageFull content, hero, sectionsRedirects to photos or post-event landing
ScheduleVisible with full agendaHidden from navigation
RSVPForm availableHidden from navigation
PaymentsPay page availableHidden from navigation
PhotosGallery accessibleGallery accessible
DocumentsAvailable to authorized usersAvailable to authorized users
PollsOpen for votingResults visible, no new votes
AnnouncementsEmail and bannersExisting banners remain
Admin dashboardFull accessFull access
Write operationsAll allowedPOST/PUT/DELETE return 503

Read-only enforcement

In post-event mode, the lifecycle gate in hooks.server.ts blocks all write operations:

Non-GET request → 503 "Event is in read-only mode."

This applies to all non-admin routes. Admin routes still allow writes so organizers can manage the archive (moderate photos, update permissions, etc.).

Day-to-day management

Post-event checklist

Before switching:

  1. Confirm all payments are reconciled — check /admin/payments for pending items
  2. Export RSVP data — download attendee records for your records
  3. Review photo gallery — moderate any inappropriate content
  4. Verify document permissions — ensure the right people can access files
  5. Close polls — finalize any open polls
  6. Send a final announcement — let attendees know the site is transitioning

After switching

  • The site serves the post-event experience automatically
  • Attendees with existing sessions can still access protected content
  • New users can still sign in (if on the allowed list) to view photos and documents
  • Organizers retain full admin access

Reverting

To return to active mode:

  1. Change Mode back to active in /admin/settings
  2. The full site becomes available again immediately

This is useful if you need to reopen RSVPs or accept additional payments.

Attendee experience

After the transition:

  • Homepage: Shows a simplified landing pointing to photos and documents
  • Photos: Gallery remains fully functional — browse and upload
  • Documents: All accessible documents remain downloadable
  • Polls: Results visible but voting is closed
  • Sign-in: Still works for accessing protected content
  • Other pages: Navigation items for RSVP, schedule, and payments are removed

Other lifecycle states

Beyond active/post-event mode, the platform supports additional states:

StateBehavior
draftEvent exists but isn't publicly routed — for setup before launch
suspendedAll non-admin routes return 503 — for emergency maintenance
archivedRead-only, not publicly routed — for long-term storage

These states are managed through the platform UI at /platform/events/[id], not the event admin.

Troubleshooting

SymptomFix
Old site still showing after mode changeSettings are cached for 5 seconds — refresh the page
Attendees can't access photosVerify they're signed in and on the allowed list
Write operations still workingConfirm the mode is set to post-event in settings
Admin can't make changesAdmin routes bypass read-only mode — check for other errors
Banner still showingEdit or deactivate the banner in /admin/announcements

Next steps

Released under the MIT License.