Menu and navigation

Where: Content → Menu Setup

What appears in your site's header, and when.

What can go in the menu

• Built-in pages — leaderboard, achievements, FAQ and the rest.
• Custom pages you built.
• Custom URLs, including external addresses.
• Actions, such as registering or signing in.

Items can be dragged into order.

Showing items at the right time

Menu items can be conditional, so the navigation reflects the phase your event is in rather than showing everything always.

The available conditions include:

• After Registration Start
• After Event Start
• After Event End
• After Event Finalize
• Event Period and Custom Period
• Authentication — signed in or not

This is the most useful part of the screen. A leaderboard link before the event starts leads to an empty table; a register link after registration closes leads to a dead end. Conditions remove both without you remembering to edit the menu on the day.

A sensible default menu

Phase	Show
Before registration	About, FAQ
Registration open	About, Register, FAQ
Event running	Leaderboard, Achievements, FAQ, Register (while open)
After the event	Leaderboard, Results, Achievements

Keep it short

Header space is small and mobile space is smaller. Five or six items is plenty; a menu that wraps onto two lines on a phone reads as clutter.

Anything that is not a destination people actively look for belongs in the footer, not the header.

Authentication items

The sign-in and profile items can be shown based on whether the viewer is signed in, so participants see their profile and visitors see a way in.

Check both states before launch. It is easy to configure this while permanently signed in and never see what a visitor sees.