Hazem Azzam.

CASE STUDY — E-COMMERCE / STOREFRONTThe Super Bowl

YEAR
2026 — Present
ROLE
Solo Frontend Engineer & Architect
TEAM SIZE
1 person

Case study by Hazem Azzam

01 — OVERVIEW

What it is

A Next.js storefront powering branded online-ordering experiences, with The Super Bowl as its flagship brand.

02 — CHALLENGES

Key challenges

  1. 01Keeping brand branches mergeable — required strict file-boundary rules separating business logic (skeleton) from visuals (brand) so auto-sync rarely conflicts.
  2. 02Making one storefront serve three store topologies without leaking topology conditionals across every feature.
  3. 03Resolving delivery eligibility across store-wide flags and per-branch backend rejections, which surface through different channels.
  4. 04Achieving genuine RTL rather than a mirrored LTR layout — logical Tailwind properties, directional icon handling, and no hardcoded left/right anywhere.
  5. 05Modelling multi-section catalog responses so each consumer filters by section type instead of creating phantom entities.

03 — ACHIEVEMENTS

Key achievements

  1. 01Built The Super Bowl design system end-to-end: custom palette, licensed display typefaces, and reusable pattern components, with Egyptian-dialect Arabic copy.
  2. 02Implemented guest-capable ordering with online VISA payment, including redirect handling and a polled payment-result page.
  3. 03Designed a backend-driven dynamic checkout form that renders arbitrary field configurations and embeds either standalone or namespaced under a parent form.
  4. 04Delivered full English/Arabic RTL support using logical-direction styling throughout, with locale as a URL segment and translation-forced component APIs.
  5. 05Built a single feature set that adapts at runtime to three store topologies (one store, one store with branches, multi-store) without per-topology forks.
  6. 06Architected a skeleton-plus-brand-branch model that lets one codebase serve multiple branded storefronts, with automated main-to-brand sync via GitHub Actions.

04 — STACK

Technologies used

  • React
  • Next.js
  • TypeScript
  • Tailwind CSS
  • shadcn/ui
  • React Query
  • React Hook Form
  • Zod
  • ESLint
  • Vitest
  • GitHub Actions
  • REST API design
  • i18n (next-intl)
  • Google Maps
  • Clean Architecture
  • Modular Component Design
  • RTL/Arabic interfaces
  • SSR