The arena website homepage shown on a laptop, with a featured concert, its date, and a Buy Tickets action. — The homepage during the transition, desktop. It led with the next event, its date, and a single ticket action, the pattern that had to survive the change of name and domain.

01 · Arena website rebrand and CMS migration

Keeping a live arena website accurate through a full rebrand

I helped move FTXArena.com to KaseyaCenter.com while events, ticket links, premium offerings, and visitor information stayed current. The work combined content migration, quality assurance, reusable CMS components, and clearer fan journeys.

Role: Web and UX designer
Focus: CMS migration and content operations
Platform: Responsive web
Outcome: Clearer discovery and easier updates

02 · Project snapshot

A redesign that had to keep moving

The arena was changing its name, domain, brand, and content system. At the same time, the public website still had to support upcoming events, ticket sales, premium hospitality, food, parking, and venue planning.

My job was to help move the content safely, make high intent tasks easier to find, and give internal teams components they could update without rebuilding pages from scratch.

Migration: FTXArena.com to KaseyaCenter.com
Content: Events, visitor planning, premium hospitality, dining, promotions
Integrations: Ticketmaster destinations and event links
Deliverables: Migrated pages, reusable modules, popup campaigns, quality assurance

03 · The challenge

The site could change. The event calendar could not stop.

A live venue website behaves more like an operating service than a finished brochure. Dates move, ticket links change, event artwork arrives, premium offers evolve, and visitors need accurate answers before they travel.

The venue seats 19,600 people and hosts more than 100 events each year, so a broken link or stale event detail can affect many different fan journeys.

The goal was to complete the migration without losing the speed and accuracy that daily publishing required.

Keep event content current during the migration.
Protect ticket and planning paths.
Make future updates easier for internal teams.

04 · My contribution

I connected design decisions with daily content work

Migration and quality assurance

I moved and reviewed content across the new CMS, checking page structure, links, images, labels, and responsive behavior before launch.

Live event publishing

I updated concerts and tours as information changed, then verified that every ticket action reached the right Ticketmaster destination.

Reusable premium content

I built flexible sections for Bacardi Ocho Lounge and Loge Suites so teams could update copy, photography, pricing, and calls to action without a custom rebuild.

Promotions and announcements

I implemented campaign popups for season tickets and special announcements, with clear messaging and controlled placement.

05 · Experience strategy

Organize the site around what fans are trying to do

The navigation and homepage modules were shaped around intent. A fan should not need to understand the arena's internal structure to find the next useful action.

Step 01 Find an event
Step 02 Check the date and details
Step 03 Buy tickets or plan the visit
Step 04 Explore food, parking, or premium options

06 · Events and ticketing

Make every event easy to scan and act on

Full length capture of the arena homepage showing the featured concert, event cards with dates and ticket actions, the Upcoming Events list, visit shortcuts, news, and a mini calendar. — The homepage capture is shown at its native width of 458 pixels. Open it to read the full length without enlarging the file.

Consistent event cards

Dates, titles, artwork, and actions follow the same order so people can compare events quickly.

One clear ticket label

Buy Tickets stays consistent across the experience, reducing hesitation at the most important action.

Useful paths beyond tickets

More Info supports visitors who need event details before they are ready to purchase.

07 · Wayfinding

Put common visit questions close to the event journey

All Events

A complete view for people who want to browse beyond the featured list.

Food and Beverage

A direct path for visitors planning what to eat and where to meet.

Directions and Parking

Practical arrival information that reduces uncertainty before the event.

08 · Reusable CMS components

Build once, then let the content change safely

Bacardi Ocho Lounge and Loge Suites needed polished presentation, but they also needed to stay easy to maintain. Reusable components created a dependable structure while leaving room for new copy, pricing, and imagery.

Premium page component

Field 01 · Headline and description

Bacardi Ocho Lounge

One short paragraph of editable positioning copy.

Field 02 · Photography

Gallery slot filled by the editor.

Field 03 · Pricing or package details

Editable rows for inclusions, capacity, and price or inquiry details.

Field 04 · Primary call to action

Request information

Bacardi Ocho Lounge

Same component, lounge content. Copy, gallery, and price details change without touching the layout.

Loge Suites

Same component, suite content. Availability and package details stay current because they live in fields, not in a one off page build.

The point of the structure was practical. When a premium package changed, the team edited fields instead of asking for a new page.

09 · Campaign support

Give announcements a clear place without taking over the experience

Promotional components gave the team a faster way to support season tickets and special announcements. The pattern kept the message focused, the action clear, and the rest of the page available when the visitor was not interested.

Announcement A short banner carries timely venue news without interrupting the page. Learn more

Closes with Escape, the backdrop, or the close control.

10 · Process

A careful loop for high change content

01Inventory existing content
02Map content to the new CMS
03Migrate copy and media
04Connect and verify ticket links
05Review desktop and mobile
06Publish, monitor, and correct

Quality assurance checklist

Every item was reviewed in context, not in isolation.

Event name and date
Venue details
Ticketmaster destination
Image crop and sharpness
Call to action label
Mobile layout
Navigation and internal links
Expired promotion removal

11 · Mobile behavior

Keep dense event content readable on a smaller screen

The arena website photo galleries page on a phone, showing a grid of event photos with dates, titles, and View Gallery links. — The supplied capture shows the broader mobile visual system rather than a specific moment in the migration.

On mobile, the priority is clarity. Event artwork, dates, titles, and actions need enough space to remain readable without turning the page into a wall of small cards.

Preserve readable type and tap targets.
Stack information in decision order.
Keep images sharp and purposeful.

12 · Outcome

A clearer public experience and a more manageable content system

The transition stayed active

The team could make rapid content changes during the rebrand with minimal downtime.

Fan paths became easier to read

Events, tickets, planning information, and premium offerings gained a clearer information scent.

Updates became more repeatable

Reusable CMS components reduced one off page work and gave teams a dependable structure for future changes.

Quality checks became part of publishing

Link, content, image, and responsive reviews helped reduce the risk of stale or mismatched information.

13 · What I learned

For a live venue, content operations are part of the user experience

This project reinforced that a redesign is not finished when the interface looks right. For a venue, the experience depends on what happens after launch: how quickly an event can be updated, how confidently a link can be verified, and how easily a visitor can find the next useful step.

The strongest design decision was creating structure for change. Clear event patterns, reusable premium modules, and a practical review process helped the website stay useful while the organization moved through a major transition.

14 · Closing

Designing for the show and the work behind it

The final experience supports two groups at once: fans who need clear answers and internal teams who need to publish accurate information quickly.

Back to work