Africa Blockchain Festival

The launch date could not move, so I completed the page structure, responsive layouts and important states in Figma before development began. That gave the team a clear view of the site early and reduced changes during the build.

Sponsors and attendees needed different information. The sponsor route focuses on audience, previous partners and commercial opportunities. The ticket route focuses on the programme, access levels, travel and payment. Both routes remain visible without competing for the same call to action.

I built the main site in WordPress around the festival’s content. The team can update speakers, sponsors, ticket tiers, travel information and translations without editing templates.

The ticket journey covers selection, registration, payment and travel. I planned the sequence before designing the screens, then kept the calls to action and page states consistent from one step to the next.

Passes are presented by level of access, which makes the difference between workshop, general and VIP options easier to compare. One recommended option is visually prominent, while sponsorship remains available as a separate route.

The payment page also handles the case where someone arrives without choosing a pass. It explains that no charge has been made and sends the visitor back to ticket selection instead of leaving them at an error.

I also built a separate event dashboard with Next.js, TypeScript and Supabase. It brings registrations, payment data, campaign links, coupons and engineering requests into one place for the event team.

Google Sheets remains the team’s source of truth. The dashboard synchronises those records and shows whether each source is up to date. Edited rows update, deleted rows are retained as inactive records and restored rows are not duplicated.

Campaign reporting follows individual share links through to checkout and payment. That lets the team compare the links given to different partners instead of relying only on broad channel labels.

Coupon values are set on the server and redemptions are counted only after payment. Loading states are included on each route so slower services do not make the application appear frozen.

The screens below run on the application’s own preview data rather than live festival figures, because the dashboard sits behind a login and holds real registrant details.