GitLab had event webpages that needed to be updated manually by engineers for several months per event. I was able to streamline and automate the process by predictively swapping out reusable modules created in advance.

Examples of different phases of event websites include:

  • Initial placeholder page.
  • Either a rough location or a timeframe is announced.
  • Both location and timeframe are solidified.
  • Call for papers (CFP).
  • Call for sponsors.
  • Call for volunteers / ambassadors.
  • A list of speakers is identified and will continue to grow.
  • A list of sponsors is identified and will continue to grow.
  • Generalized tracks/workshops are proposed.
  • CFP closed.
  • Partners and plans for travel & lodging are announced.
  • FAQ are updated.
  • Scholarships applications are open.
  • Registrations have begun.
  • Scholarship applications are closed.
  • Event content is finalized & locked in place (excepting any unexpected changes).
  • Event timings are announced & registerable (ie be here at 4PM, there at 7AM...).
  • Registrations have ended.
  • Event is in progress.
  • Photo, social, and other resources are gathered (an ongoing process).
  • Blog posts are created (an ongoing process).
  • Event is over, thanks for coming.
  • Genericize the landing page until the next event cycle is ready to begin.
  • Recap page is created.
  • Video is ready & pages are updated accordingly (not sure where this goes in the order of things).