← All projects
Freelance · Luxury travel

Otoctone

A new style for the Otoctone website, a collection of exceptional places to stay (a villa on Lake Geneva, a chalet on Mont Blanc, a house in Costa Rica, a catamaran in the Mediterranean).

View the live site

Role
Freelance frontend developer, on assignment for an agency
Period
2025
Stack
Tailwind.css, Sass, Slim, Stimulus.js
Environment
Ruby on Rails
Otoctone: the home page with the full-screen video, and the villa page on mobile
The home page on desktop and a destination page on mobile
Context

Changing the style of an existing website

The pages of the site are built in a back office from content blocks (text, images, key figures, FAQ, reviews…) that the client puts together themselves.

My assignment, as a freelancer for the agency that develops the site: change the style of the existing pages (header, footer, blocks, destination pages, contact), on desktop and mobile, from July to October 2025, up to the client's final feedback.

What I did

The new style of the site

  • 07.2025Navigation: menu, submenu, language selector, mobile header and footer.
  • 07.2025Content blocks: titles and links, media, partners, key figures, reviews, lists.
  • 07.2025Destination pages: parallax header and “Learn more” panel (HTML, CSS and a Stimulus.js controller).
  • 07.2025Header on scroll: it hides when you scroll down and comes back when you scroll up.
  • 09.2025Home page: full-screen video, “Learn more” button that follows the scroll.
  • 10.2025Client feedback: contact page, FAQ, cards, mobile menu, transitions.
Screenshots

A few screens

Screenshots of the live site (November 2026). Click a screenshot to enlarge it.

The interactions

  1. Home page: the header fades out when you scroll down
  2. Destination page: the photo scrolls more slowly than the title (parallax)
  3. Destination page: the “Learn more” panel opens from the side
Otoctone on mobile: menu open
Otoctone on mobile: Learn more panel open
Otoctone on mobile: contact page

On mobile: the menu, a destination page, the “Learn more” panel and the contact page

What I learned

Working in other people's code

On Otoctone, I joined a site already built by other developers. I first had to understand their code and how it was organized (blocks, templates, styles) to change the style without breaking anything. It is a situation I know well: taking over an existing project and making it evolve.

Since the client builds their own pages with the blocks, each style had to work whatever the order of the blocks and the length of the texts.