Different problems call for different approaches.

The need: The existing website no longer represented Luisa’s work: its structure and journeys were unclear, and the mobile experience was weak.

The decision: Redesign the public website and later add, at Luisa’s request, a dedicated dashboard for managing events.

What I built: I reworked the structure, content and responsive journeys. The authenticated dashboard lets Luisa and her collaborators create, edit and delete tours, and manage images, text and descriptions, dates, times, prices, availability and capacity. New events are published automatically on the website. Supabase handles the database and authentication, with storage where used. The website also includes multilingual content, search and filters, maps, reviews and booking.

Outcome: Luisa can manage tours, content and availability without relying on Francesca; the website better represents her work and has a rethought mobile experience.

The need: Built from scratch, the project needed to bring wine, the winery, the local area, events and experiences together in clear journeys for an international audience.

The decision: Create a multilingual information architecture with distinct journeys and an on-site booking system for different reservation types.

What I built: I handled web design, UX/UI, technical architecture and frontend development. The site manages localized routes, metadata and hreflang, as well as localized forms and messages and dedicated experience pages. Booking handles reservation types, dates, times, party size, availability, prices and customer details; it includes confirmation and payment, and stores reservations in a database. I also worked on technical SEO, performance, accessibility and responsive behavior.

Outcome: Content and journeys for wine, the winery, events and experiences are available across languages, with bookings made directly on the website.

The need: The business needed a more representative website and a way to avoid manually updating availability across separate calendars.

The decision: Add two-way iCal synchronization between the website and Airbnb, with independent calendars for three or more properties.

What I built: I handled web design, UX/UI, frontend development and integrations on my own. The website displays prices and availability; when a booking arrives from Airbnb, the site calendar updates automatically. A headless WordPress CMS lets the client manage the blog and editorial content. The project does not include a complete on-site booking system.

Outcome: Availability stays more consistent between the website and Airbnb with fewer manual updates, while the client can manage editorial content in the CMS.