case study · ski slope website
A ski slope site that tells you at a glance whether to go today
A new website for Sport Dolina Bytom, a ski slope in the middle of the Silesian metropolis. Live lift status and weather, a slope webcam, a price list with a visit cost calculator and two animated header variants for the client to choose from. Everything is edited in a simple CMS, in Polish and English.
01 / starting point
A skier has one question: can I ski there today?
The previous site was WordPress with a theme and plugins. The content was there, but answering the key questions meant piecing things together from several places, and the page loaded far more than it showed.
- 01A heavy home page
About 96 requests on desktop, including 17 stylesheets, 18 scripts and 18 font files.
- 02Jumping layout on phones
Layout shifts during loading at CLS 0.22, above the “needs improvement” threshold of Core Web Vitals.
- 03Conditions, not news
Is the lift running, how much snow is there, what's the weather: this should be visible on the first screen, not in the latest post.
- 04Prices to add up
A lift pass, rental, sledging and a lesson for several people means a dozen line items. A family should be able to work out the cost of a visit without pen and paper.
- 05Content to keep and to clean up
Descriptions, photos and prices were migrated. A post full of SEO-spam style links was not migrated, and its URL redirects to the news section.
- 06Run without a developer
Slope staff need to change the status, prices and news from a phone in seconds, without assembling pages from blocks.
02 / metrics
More features, four times fewer requests on phones
Home page measured in Chromium (Playwright): the old sportdolina.pl and the new test version, desktop and phone.
- 98 → 21
- requests on phones on the home page
- 2.3 → 1.0MB
- transfer on phones on first visit
- 17 → 2
- stylesheets on desktop
- 0.22 → 0
- CLS on phones (layout shifts during loading)
- 25
- price items in the CMS, 17 of them feed the calculator
- 10min
- weather refresh from Open-Meteo, no API key
- ~130KB
- 3D scene (gzip), loaded only when needed
- 2
- languages shared routing and field translations in the admin
21
1.0 MB
32
1.6 MB
Median of two runs, measured from the server. Load times are left out, because from a single location they aren't meaningful. Desktop transfer is mostly high-resolution photos.
03 / header
Two header variants, and the choice is the client's
Instead of arguing for a single vision, two complete variants were built. On the test version a button in the header switches between them. The default variant is chosen in the admin, where the switch can also be turned off.
3D slope three.js · procedural scene · camera fly-through on scroll
Cinematic drone photo · falling snow in 2D canvas
04 / live
Status, weather and webcam in one place

Status set with one click
Staff pick a mode: automatic by opening hours, open, closed or off-season. Plus the status of the lift, sledging, rental and ski school, snow depth and a note of the day. The status bar stays on screen while moving between pages.
Weather with no key and no waiting
Temperature, feels-like and wind come from Open-Meteo. The server keeps the response in memory for 10 minutes and refreshes it in the background, so the page never waits for an external API.
Third-party services only on demand
The webcamera.pl stream and Google Maps load after a click. Until the visitor needs them, the page doesn't fetch their scripts or send them any data.
05 / prices
The visit calculator uses the same price list
A price item in the admin just needs a calculator key, e.g. “2 h pass” or “full set rental”. Changing a price in the CMS instantly changes the calculator's result too.



06 / admin
A CMS organised around running a slope, not building pages
Payload CMS with an admin grouped the way slope staff think. Saving in the admin immediately purges the site cache, so a status change shows up on the next refresh.
Slope
- Live status: mode, attractions, snow, piste, lights, note of the day
- Price list in groups, linked to the calculator
- Opening hours that drive the automatic status
Content
- News, pages and home page sections
- Header variant and test switch
- Google reviews: imported via the Places API daily and on demand, with older ones added by hand
Settings & languages
- Contact, Booksy lesson booking, webcam, rules, map, SEO
- “Polski / English” switch in the admin
- An empty English field falls back to Polish, so nothing disappears before translation
07 / rest of the site
Offer, directions and mobile


08 / delivery
From the old site to the test version
Architecture
Three services in Docker: a server-rendered Astro frontend, Payload CMS and Postgres on an internal network. Caddy routes the admin and API to the CMS and everything else to the frontend, and blocks internal endpoints.
Content migration
An import script moved descriptions, photos, news and prices from the existing site. Old URLs lead to their new counterparts via 301 redirects.
Motion in moderation
GSAP and Lenis for scrolling, page transitions without full reloads. With “reduce motion” enabled, the 3D scene, snow and pinned sections give way to static views.
Backups & maintenance
A database dump and the media go into the server's daily backup. The frontend rebuilds with a single script, and CMS migrations run on their own.
Before launch
Left for the client to decide: the header variant, real slope status instead of sample data, and replacing a few stock photos with their own.
stack
Test version ahead of the move to sportdolina.pl. The slope status in the screenshots is sample data, and some photos are stock images to be replaced. The Google reviews section isn't shown in the screenshots because it contains reviewers' personal data. Measured in November 2026.
next step
Facing a similar challenge?
Tell me what you want to achieve. I'll come back with a concrete proposal, a quote and a delivery plan.