Skip to case study
All work Miguel Clavel Senior Product Designer
Miami HEAT Homepage
Miami HEAT logo
Miami HEAT homepage redesign

A homepage built to move at game speed

I helped redesign the Miami HEAT homepage as a flexible publishing system for game days. The new structure put schedules and tickets first, gave marketing room for memberships and merchandise, and made live updates easier for the content team.

Role: UX and web design Focus: Live content and CMS components Experience: Responsive homepage Audience: Fans and content teams
Miami HEAT public website homepage · Legacy HEAT.com and FTXArena.com content stack · Approved production screenshots with code-drawn schematics for structure
The redesigned Miami HEAT homepage shown on a desktop monitor
The redesigned homepage put games, ticket actions, and an active campaign into one focused first view.
02 · Overview

One homepage serving fans, marketing, and game day operations

The homepage had to do more than introduce the brand. It was often the fastest route to a game, ticket, score, schedule, player, or jersey. At the same time, the content team needed to react to a live season without waiting for a custom page build.

I approached the redesign as a hierarchy and publishing problem. The interface needed stronger priorities for fans and a more flexible structure behind the scenes.

The production homepage shows how the strategy became a flexible system for ticketing, campaigns, merchandise, editorial stories, memberships, and arena content.

Surface
Miami HEAT homepage
Core journeys
Games, schedule, tickets, players, shop, membership
Operating rhythm
Pregame, live game, final, and next game
System need
Reusable and reorderable CMS components
03 · The challenge

The page looked static while the season kept changing

Inconsistent templates made the homepage harder to scan and slower to update. High intent actions competed with stories and promotions. During games, even a small content change could become a stressful publishing task.

The real design question was not simply what belongs on the homepage. It was what belongs first right now.

  1. Problem 01

    Fans had to work too hard to reach the next game, schedule, or ticket action.

  2. Problem 02

    Marketing had limited ways to introduce jerseys and memberships without crowding the hero.

  3. Problem 03

    Content teams needed faster patterns for game status, player updates, and postgame changes.

Season scale. Public context, not measured project impact.

53
Regular season wins
41 / 41
Home games and sellouts
804,761
Total home attendance
18
Playoff games to the Eastern Conference Finals

These figures describe the scale of the season, not the impact of this project. Public context from the official 2021 to 2022 season review.

04 · Product thinking

Let fan intent and game state control the hierarchy

  1. 01

    Now

    Show the current or next game, time, opponent, and most useful action first.

  2. 02

    Act

    Keep Buy Tickets and View Schedule visible before editorial content asks for attention.

  3. 03

    Follow

    Give scores, recaps, player stories, and team updates a dependable home.

  4. 04

    Belong

    Introduce memberships, jerseys, and HEAT culture after the immediate game need is clear.

This priority model kept the homepage useful through different moments of the season. The content changed, but the decision order stayed understandable.

05 · Homepage anatomy

Put the most time sensitive information closest to the top

The complete production Miami HEAT homepage from the campaign lead through the footer
Scroll inside the frame to see the full page. The production homepage balanced conversion, commerce, editorial content, and arena discovery within one modular page.
  1. 01

    Campaign lead

    High visibility storytelling with direct actions.

  2. 02

    Ticket Central

    Ticket options grouped into a clear decision area.

  3. 03

    Shop Court Culture

    Products introduced without taking over the opening hero.

  4. 04

    Flexible campaign modules

    Auditions, collections, and limited promotions could change independently.

  5. 05

    Editorial and trending content

    Stories and video kept the homepage connected to the team beyond game results.

  6. 06

    More HEAT

    Arena events, premium hospitality, food, and social channels extended the journey.

06 · Live operations

Design the homepage to change before, during, and after the game

The same game module carries three states. Scroll to move it from pregame to live to final. Neutral data is used throughout: MIA and OPP stand in for real teams, and no historical score is shown.

{{ activeLabel }} {{ activeMeta }}
MIA
{{ activeHome }}
{{ activeSeparator }}
OPP
{{ activeAway }}

{{ activeStatus }}

Module actions
{{ action.label }}

Game status module schematic, three states, desktop. Neutral team codes and no invented score.

The component structure reduced the need to redesign the page for every state. Editors could update the content and priority while the underlying pattern stayed familiar to fans.

07 · Content operations

Make every game update clear, fast, and reviewable

  1. 1

    Prepare

    Load game information, artwork, links, and fallback content before tipoff.

  2. 2

    Verify

    Confirm opponent, date, time, ticket destination, broadcast details, and player references.

  3. 3

    Publish pregame

    Move the game module into the primary position and confirm mobile behavior.

  4. 4

    Update live

    Change game status and supporting links without rebuilding the homepage.

  5. 5

    Close the game

    Publish the final state, recap, highlights, and related player content.

  6. 6

    Reset

    Move the next game into focus and remove expired live messaging.

Every time sensitive module needs an owner, a source, a publish time, and a fallback state.

08 · Roster and stories

Keep players current without making every update a custom design task

01 Current player image · approved photography slot
02 Name and number 00

03 Position or story label

04 Primary story, profile, or shop action
05 Publish control 05 Expiration control

Player content changes quickly across a season. The system needed dependable fields and review steps so an old image, outdated roster reference, or incorrect jersey link did not remain on the homepage.

Player quality assurance

  1. 01Confirm roster status and spelling.
  2. 02Use current approved photography.
  3. 03Check number, position, and linked destination.
  4. 04Remove or replace expired player promotions.
  5. 05Review crops on desktop and mobile.

Player card anatomy schematic. The image area marks where approved team photography is placed; no player photography is shown here.

09 · High intent actions

Shorten the path from homepage to seat selection

Utility bar Next game · MIA vs OPP · 7:30 PM ET Schedule
Game module · primary weight
MIA vs OPP Tonight · 7:30 PM ET · Kaseya Center
Buy Tickets View Schedule Game Details
Story rail · team news
Story rail · video
Story rail · player spotlight

Above the fold schematic, desktop. The game module carries more visual weight than the surrounding story rails.

Ticket Central section of the homepage with grouped ticket options
Ticket Central gave ticket choices a clear visual destination below the campaign lead.
The schedule page shown on a laptop
Schedule and game rows used a consistent scanning pattern for opponents, dates, and ticket actions.

Fans arriving with a clear purpose should not have to search through campaign content. A consistent game module and direct actions help them move from interest to the correct destination with less hesitation.

10 · Business modules

Add commerce without turning the homepage into a store

One focused product image slot

Shop Jerseys

Connect player stories and team moments to relevant merchandise using one focused image, a short label, and a clear shop action.

Shop jerseys

HEAT Membership

Give memberships a consistent place for benefits and sign up actions without competing with urgent game information.

See membership benefits
Homepage campaign blocks for auditions, collections, and a limited retail promotion
Reusable campaign blocks supported auditions, special collections, and time sensitive retail messages without rebuilding the page.

Each of these blocks used the same content, media, action, and timing fields. That is what allowed an audition notice, a City Edition collection, and a tax free weekend promotion to occupy the same slot on different days without a new page build.

The membership page shown on a laptop
The same visual system extended into a focused membership page with its own information and conversion needs.

The homepage did not need to explain every program in full. Its job was to establish priority, create interest, and hand visitors to focused destinations such as membership, tickets, and retail.

Commerce appears after the game need is answered. The modules should feel connected to the team story, not inserted as unrelated advertisements.

11 · CMS structure

Build flexible sections with predictable editing rules

Game status card

Content
Headline, supporting copy, labels, and metadata
Media
Image, video, focal point, and alt text
Actions
Primary link, secondary link, and destination validation
Timing
Publish date, expiration date, priority, and fallback state

Editorial hero

Content
Headline, supporting copy, labels, and metadata
Media
Image, video, focal point, and alt text
Actions
Primary link, secondary link, and destination validation
Timing
Publish date, expiration date, priority, and fallback state

Story rail

Content
Headline, supporting copy, labels, and metadata
Media
Image, video, focal point, and alt text
Actions
Primary link, secondary link, and destination validation
Timing
Publish date, expiration date, priority, and fallback state

Player spotlight

Content
Headline, supporting copy, labels, and metadata
Media
Image, video, focal point, and alt text
Actions
Primary link, secondary link, and destination validation
Timing
Publish date, expiration date, priority, and fallback state

Merchandise feature

Content
Headline, supporting copy, labels, and metadata
Media
Image, video, focal point, and alt text
Actions
Primary link, secondary link, and destination validation
Timing
Publish date, expiration date, priority, and fallback state

Membership promotion

Content
Headline, supporting copy, labels, and metadata
Media
Image, video, focal point, and alt text
Actions
Primary link, secondary link, and destination validation
Timing
Publish date, expiration date, priority, and fallback state

Consistency did not mean every section looked the same. It meant editors knew where to make changes, what needed review, and how the component would behave across devices.

12 · Quality

Fast game day content still needs to be inclusive and dependable

Accessibility

  • Semantic heading order
  • Keyboard accessible controls
  • Visible focus states
  • Sufficient color contrast
  • Descriptive alt text
  • Clear live status language that does not rely on color alone
  • Tap targets of at least 44 pixels

Performance

  • Responsive image sizes
  • Modern image formats
  • Lazy loading below the fold
  • Reserved image dimensions to reduce layout shift
  • Lightweight motion
  • Minimal blocking scripts
  • Content that remains usable when media is slow
13 · Across devices

Preserve the decision order on every screen

Desktop

A broad game and hero canvas with supporting rails.

Tablet

The game module stays primary and simultaneous content is reduced.

Mobile

Game information stacks in decision order with a full width primary action.

Responsive layout schematics drawn in code. Frames show structure and priority, not final pixels.

  1. Reflow components instead of shrinking desktop layouts.
  2. Keep ticket and schedule actions visible.
  3. Crop player photography intentionally.
  4. Avoid tiny carousel cards.
  5. Preserve content priority when the layout changes.

A homepage can feel energetic to fans and still remain practical for the people publishing it.

14 · Outcome

A homepage that supports both fan urgency and publishing speed

Clearer fan priorities

Games, schedules, and ticket actions gained a dependable place near the top of the experience.

Faster content changes

Reusable states and components gave the content team a more practical way to update the homepage during a live season.

More useful business moments

Merchandise and memberships could appear in the journey without overwhelming the main game message.

More consistent player content

Shared fields and review rules created a clearer process for keeping roster related content current.

Stronger cross device quality

Responsive, accessibility, and performance rules helped the same hierarchy remain understandable across screen sizes.

15 · What I learned

The best sports homepage is ready for the next moment

This project reinforced that live sports design is partly a content operations problem. A polished screen matters, but the system behind it determines whether the experience stays accurate when the game changes quickly.

The strongest improvement was designing for change from the beginning. A clear priority model, reusable game states, structured player content, and practical review steps gave the homepage a better chance to stay useful throughout the season.

Built for tipoff, the final score, and everything between

The final direction gives fans a faster route to what matters now and gives the content team a more flexible way to keep the Miami HEAT story moving.

Miami HEAT logo
NBA logo Team and league marks are shown for identification only. Miguel Clavel contributed UX and web design, homepage content strategy, CMS component structure, live content operations, and quality assurance.