4 SOSNY. Mountain guesthouse website

4 SOSNY is a private vacation house at the foot of the Karkonosze mountains: 160 sq m, a view of Śnieżka through panoramic windows, a sauna, a jacuzzi, electric bikes. The house is split into two equal halves, so guests can rent the whole place or take just one side - it works for a big group of friends and for a single family alike.

The owners didn’t want to depend on booking aggregators and their fees. They needed a site of their own - one that presents the house and the area, takes booking requests by itself, keeps track of quotas and available slots, and instantly notifies the owners about every new enquiry so it can be handled right away.

We delivered the project in 3 weeks: designed everything in Figma, built a custom WordPress theme, wrote our own booking module with an availability calendar and hooked up Telegram notifications so the owners can manage requests right from their phones.

The design was created in Figma from scratch. The palette came straight from the landscape - the deep green of a pine forest and a warm cream, like the light in the windows of the house in the evening. Large typography, plenty of air and borderless photos: the site feels light, shows off the best of the property and sets the mood before you even arrive 🙂

The home page is built from the essential sections and answers pretty much every question a guest might have. There are prices, the surroundings with distances to trails and ski lifts, a gallery, a blog with tips from the hosts, an FAQ and a map with directions. Each section is a separate configurable block in the admin panel: the content can be rearranged without a developer.

Everything you see on the site is our work from start to finish. We came to the property and shot the house ourselves: the interiors, the sauna and wellness area, the bedrooms, the view of Śnieżka and aerial drone footage. No stock photos, nothing borrowed - just the real house in good light.

A special point of pride is the 360° virtual tour. We shot six panoramas of the key rooms and assembled them into an interactive walkthrough: guests spin the view in any direction, as if standing in the middle of the room, and jump between rooms from a list. The panoramas rotate right in the browser and work just as well on a phone. A tour like this answers half of the questions before booking - people see the house with their own eyes and arrive already feeling at home.

We've embedded one panorama from the tour right here - take it for a spin.

The house is split into two equal halves, so it can be rented in different ways: an apartment for a party of up to 4 guests, or the whole house - up to 8 people, four bedrooms, two kitchens and two bathrooms. We put this choice front and centre: two cards with price and details on the home page, and a format switcher in the booking form that changes both the available dates and the total price.

Off-the-shelf booking plugins for WordPress mean subscriptions, extra screens and someone else’s logic. A single house with two halves needed simple, honest mechanics, so we wrote the module ourselves.

• Requests are stored in the admin panel as their own entity - with the statuses “New”, “In progress”, “Confirmed” and “Cancelled”, a new-request counter in the menu, and filters by name, email, phone and check-in dates.
• A request is captured immediately through a hook that intercepts the form after validation but before any email goes out, and writes a record to the database - even if the mail server fails, no enquiry gets lost.
• Booking the whole house blocks both halves, while booking one half marks the day as partially occupied. The calendar on the site pulls availability via AJAX and shows confirmed bookings only.
• The system watches the number of guests and adjusts the booking to match. One half sleeps up to 2 adults and 2 children; if a request comes in for, say, 3 adults and 2 children, it automatically becomes a whole-house booking - the price recalculates on the fly, and the guest sees it right on the page.

The owners are usually on site with their guests, not at a laptop. So every new request instantly arrives in their Telegram group - a neat message in Polish with all the details: dates, format, party size, contacts and the total.

Right under the message there are three buttons: “Confirm”, “In progress”, “Cancel”. A tap goes to the site’s secret-protected REST webhook, the request status changes in WordPress, the calendar recalculates, and the guest optionally gets a status-update email. A booking gets confirmed in a couple of taps from a phone, and the site immediately stops selling those dates.

The bot token and chat ID are configured on the module’s page, and the webhook secret is generated automatically. The same toggle can also mirror quick questions from the contact form into the group.

The settings hold everything that changes day to day: the rental mode (whole house or halves), per-night prices for each format, the house rules text shown next to the form, and the calendar colors. Availability and occupancy are shown in the calendar just as clearly as on the site itself.

• Pages are marked up to schema.org standards - LodgingBusiness with all the property’s attributes, and FAQPage - to compete for rich snippets in Google.
• A strict heading hierarchy and meaningful alt texts on every image - the semantics are clean and clear to search engines.
• We removed links that pointed to themselves and proofread the whole structure against our internal SEO checklist.
• We met the GDPR requirements: a cookie banner with an honest choice, and the Google map loads only after consent - until then, not a single external request leaves the page.
• We tuned the speed following PageSpeed Insights recommendations until the scores reached the green zone: images are converted to WebP on upload, lazy load is in place, and unused code is gone.

The site lives on ordinary shared hosting - inexpensive for the client and zero administration. But we set up the development process like on “grown-up” infrastructure: a local Docker environment mirrors production exactly, and every push to main triggers GitHub Actions with an incremental rsync deploy over SSH - only the changed theme files, verified by checksums, travel to the server. Uploaded photos and the WordPress core are never touched by the deploy at all.

Any change appears on the live site automatically, in about a minute. In the site’s first ten days we shipped some fifty updates - including the GDPR banner and the Telegram notifications - without a single moment of downtime.