Role: Front-end

Context: Simpler Trading — webinar launches

The decision

After someone registers, the confirmation has to put the right event on their calendar, the live URL has to become the replay when the webinar ends, and the next webinar has to take that URL on a set date. Those three have to stay in agreement.

What I owned

• The campaign spec as the source of truth. A date, a slug, or a URL that is not in the spec does not go on the page.
• The redirect. Before the event, the URL is the registration page. After the replay time, that same URL sends people to the replay. At the handoff time, it sends them to the next webinar. A query flag holds the page for QA, and a tab left open rechecks the clock.
• The confirmation calendar. One config builds the Google Calendar link and the .ics file from the title, the time, and the bullets.
• The modules. The pricing matrix renders the desktop table and the phone cards from one object. The carousels fill from that campaign copy. A member who already owns a product can have that tier hidden.
• The intake and the preflight. Marketing fills the record. The pages ship after that checklist.

How someone else reuses it

Marketing fills the intake. The build copies the spec into one config block at the top of each script. The next webinar starts as a new spec. The visit itself is the registration path: the UTM survives the redirect, and the dataLayer records the view and the signup for that same campaign.

In React and Next.js

The spec is one campaign object. A client check compares the clock with the replay time and the handoff time. The calendar is a component that receives the event. The pricing matrix is the offer table already on this site, fed by that same object. The dataLayer events for the view and the signup carry the campaign, so the page someone lands on and the event that records it belong to the same launch.