Spartisan: a multilingual website for an immersive spa.

The saved homepage fills the opening view with warm interior imagery. Large white typography sits over the scene, while the navigation remains in a horizontal bar above it. Violet accents distinguish actions from the warm background. The first screen already includes a booking control in the header and another invitation further down. The visual approach is atmospheric, but it does not postpone every practical action until the visitor has read the entire page.

The lower part of the saved view places a programme preview beside an explanation of the experience. This gives a person two ways to continue: examine a specific option or understand the general format. The site does not need to reproduce the physical experience on a screen. It needs to introduce its character and help someone understand the offer well enough to decide whether to explore it further.

For a comparable venue, the opening composition should use imagery that belongs to the actual experience. A striking photograph of an unrelated space can create expectations the venue cannot meet. The project records that Spartisan's visual selection was rebuilt twice using the venue's own photographs. That describes selection and composition work; it does not mean HeadPills organised two new photo shoots or designed the physical interiors.

An immersive experience can be difficult to describe with a single service label. The recorded site includes programmes so visitors can move from the broad idea to a more specific option. The useful question is what distinguishes those options for a guest. Names and photographs introduce them, while approved descriptions provide the practical context needed before booking. The page should not depend on evocative names alone to communicate those differences.

For a similar build, the venue would supply the description, duration, participation conditions and current price for each programme. The web team would organise this information consistently so a visitor could compare the options without assembling details from several unrelated sections. The programme content belongs to the operator. A design agency should not invent health effects, attendance recommendations or suitability conditions to make the descriptions feel more complete.

The case therefore focuses on the structure of the presentation rather than repeating the venue's wellness claims as independently established facts. The website can show what the operator says a programme includes and direct questions to the team. It cannot assess an individual guest's suitability. This distinction keeps the portfolio relevant to web design while leaving the venue responsible for its service information and guest guidance.

The project records a step-by-step explanation of the ritual. That is useful because a guest may want to know how the visit unfolds before making a reservation. A chronological structure can answer this more directly than scattered paragraphs about atmosphere. It also gives the venue a place to explain what happens before the central experience and how the visit ends, without forcing every detail into the first screen.

For a comparable website, we would agree how much operational detail is useful publicly. The goal is to explain the guest journey, not publish an internal instruction manual or imply that every session is identical. If the sequence varies between programmes, the page should state that distinction. The operator remains responsible for confirming timing, participation and the guidance given to guests at the venue.

On a phone, the order needs to remain obvious. Short stage titles and a clear reading direction help preserve the explanation when columns stack. Images should support the stage they accompany rather than interrupt the sequence with unrelated decoration. These are acceptance questions for a new implementation: they let the team evaluate whether the story still works at a smaller size instead of judging only a large desktop screenshot.

The recorded presentation includes a booking route and information about a club application. The consumer site links guests to those services; the project description does not establish that HeadPills developed the app or the external reservation platform. Maintaining that boundary is important when estimating a similar brief. A promotional website, an app and a booking system are different products even when they appear within one customer journey.

The currently inspected consumer page links booking to FareHarbor. That observation identifies the visible destination, not a completed reservation test or a guarantee of current availability. For a new project, we would agree what information is retained at the transition and how the visitor recognises the selected programme. Club offers should also remain distinguishable from a one-time reservation so people understand which action they are taking.

Spartisan's consumer site addresses the person considering a visit. The separate Spartisan Global presentation addresses partnership questions and is described in its own case. The two can share a brand and imagery while needing different information structures. A guest should not have to interpret an investment presentation to understand a visit, and a partner needs more than a programme card to evaluate a conversation.

This case demonstrates the consumer side: atmosphere, programme choice, a visit sequence and routes into booking across three languages. It does not publish measured booking growth or attribute the venue's wellness results to the website. For a similar commission, the useful starting point is the real offer, approved guest information and the systems that handle reservations after the visitor leaves the presentation.