Editing and testing sessions

Why this matters

Changes are made in your staging environment. Publishing a session updates the staging experience so you can review changes safely before pushing anything live.

Overview

You can edit sessions at any time. Changes are published to staging so you can review them, and then pushed to live as part of your wider release when you are ready.

Steps

• Open the session in the CMS
• Update fields such as time, location, content or links
• Click Publish to update the staging version
• Preview the session in your experience
• When your release is ready, push changes to live

Best practice

• Treat Publish as updating staging, not going live
• Review changes in context, not just in the CMS
• Check sessions on mobile and desktop
• Validate links, times and filters before pushing live

Common checks

• Session appears in the correct sections
• Filters are working as expected
• Dates and times are correct
• Join links or embeds work correctly

Testing scheduled sessions

When testing on the staging site, sessions will follow their real status (scheduled, live, ended).

To fully test join links, embeds and live behaviour, you can force sessions into a live state.

• Open your staging experience in a browser (press Ctrl + Alt + Shift + S or T to switch to staging)
• Press Ctrl + Alt + Shift + L

This will force all non-ended sessions to display as Live for your browser only.

Best practice

• Use this shortcut to test embeds, join links and Q&A behaviour
• Remember this only affects your browser session and resets on page refresh
• Always test both scheduled and live states where possible