A bridge crossing a lake in the foothills near Angels Camp, California

WorldMark by Wyndham

Angels Camp, California

Senior Product Designer · 2020

I designed the path from discovering a WorldMark resort to booking and managing a stay. I also helped define the Adobe Experience Manager components that let WorldMark and Club Wyndham reuse that work across both sites.

From travel idea to resort choice

I designed the public site to help visitors find a place worth staying, see what made it different, and understand how WorldMark ownership fit into the trip.

Give visitors a place to start

The homepage had to serve people at different stages of planning. I gave news, featured resorts, and deals their own sections for visitors ready to explore, then used ownership benefits and an inquiry form for people still learning how WorldMark works. On mobile, those sections read in sequence.

Browse by location

I kept one resort catalog and gave visitors several ways into it. A location index served people who already knew where they wanted to go; the list and map supported comparison. Filters, favorites, and inventory specials helped people narrow the same set of resorts by what mattered to them.

Show what a stay would be like

Photos and amenities answered what a stay would feel like. Suite types, location, and reviews helped people judge whether it fit their trip. I put the availability action on that same page so they could move from evaluating a specific resort to checking dates.

From browsing to booking

Once owners found a resort they liked, they needed to know if the trip fit their dates and credit balance. I carried the resort, suite, and dates into booking so owners could keep the stay in view as they made those decisions.

How owners plan a trip

I used the family traveler persona to ask what the site needed to help an owner decide. A trip had to fit school calendars and work schedules, often at the same peak times other families wanted to travel.

That made availability and credit cost part of planning, well before checkout. The job continued after confirmation too: owners needed to find directions, revisit the details, or change or cancel a stay.

How owners book a stay

Booking involved more than picking a room and paying. An owner might use credits for the stay, a guest certificate for someone else to check in, or a housekeeping service. I designed the flow so those obligations became clear when they affected a decision, with the selected stay still visible through checkout.

Compare resorts

I kept the selected dates, filters, results, and map together so owners could compare locations without losing their search. In the Bonus Time design, the offer and its rules stayed with the results, where they could affect which resort an owner opened.

Resort search1 / 4

Original designs show different sample stays.

The owner journey

I connected account orientation, resort exploration, booking, and trip management so owners could pick up where they left off.

  1. Orient

    See account status, credits, and travel tasks that need attention.

  2. Explore

    Search resorts and dates and compare availability.

  3. Commit

    Review the selected stay before confirming it.

  4. Manage

    Return to upcoming and past trips to modify, cancel, or plan again.

Credits and account

I organized balances, guest certificates, and housekeeping services around what owners could use on a stay. Purchase, transfer, and education sat with those resources so owners could work out their options. Account settings kept personal information, password and two-step verification, and preferences together.

Managing a reservation

Upcoming trips lead with destination, dates, and confirmation details. Owners can revisit past stays, and modify or cancel actions stay with the booking they affect.

How two brands present a resort

The resort page was where browsing turned into planning. Club Wyndham had to answer many of the same questions there, so I defined a shared structure that let both brands use the same components with their own navigation, imagery, and booking prompts.

WorldMarkAngels Camp
Club WyndhamBonnet Creek

Shared page structure

Both pages answer the same questions: what the resort is like, which suites it has, and whether they’re available. The common structure includes the gallery, resort details, amenities, suite information, and availability.

Room for each brand

Angels Camp leads its booking card with rates and availability. Bonnet Creek uses a more direct booking prompt and offers a separate save action. Each brand can change the emphasis, imagery, and language while keeping the resort information in a familiar order.

Make the structure reusable in AEM

I defined reusable components and content fields for Adobe Experience Manager. The idea was that an author could update resort facts, amenities, or suite details within the same page structure, while each brand controlled its own photography, navigation, and offers. A new resort page could use that structure without starting from a blank layout.

Outcome

I delivered responsive designs that connect resort discovery, booking, and trip management, along with an AEM component model for both brands. The designs show how owners could carry the details of a stay into checkout and how both brands could reuse the resort page and search patterns.

The project records document the design work. They don’t include verified performance or business results.

Continue exploring

More selected work.

View all projects