Independent project · 2026

Mountain guideA website he can run
without touching code.

I designed and built a services website, a content manager and a first automation for a mountain and climbing guide.

My role
Design, front-end code and automation
What I built
Website, content manager, enquiry alerts
Status
Working prototype
Website homepage with a full-screen mountain photoContent manager editing a route and its altitude profile
01 / The brief

A guide should spend his time in the mountains, not in code.

He needed to show his services, routes, booking and payment, then keep all of it up to date alone.

Show

What he offers

Services, routes, difficulty and prices in one clear place.

Update

Without help

Change titles, dates, places and photos without touching code.

Respond

To every enquiry

Make sure a message from the website never gets lost.

02 / The website

Make the next step obvious on the first screen.

The headline and both actions fit the first screen on desktop and phone. Below them, each section answers one question a client has.

Upcoming departures board with dates, remaining places, prices and booking buttons

A departures board

Date, difficulty, remaining places and price sit on one line, so people can compare quickly.

The mountain’s shape

Every route shows its altitude profile, because climbers read a route by its shape.

Honest scope

Alpine routes came out because they’re outside his qualification.

03 / The content manager

Every section of the website became a simple form.

I chose a custom panel over a generic CMS. He edits, saves, and the website updates.

Numbers became something you can drag.

The first version asked for altitudes as a list. I replaced it with a chart where he can drag a point, add one, or import a GPX file from his watch.

Before

1830, 1905, 2020, 2130, 2290, 2428, 2300, 2150, 2120, 2040, 1930, 1830

After

Drag a point

1.7002.1002.5002.428 m

Save with confidence

Success messages offer a clear choice: keep editing or go back to the list.

Hard to lose work

Leaving with unsaved changes asks him to save first.

Hard to break things

A range with routes can’t be deleted, and renaming it updates its routes.

04 / The automation

Every enquiry is saved and flagged.

My first automation turns the contact form into a simple lead list. It needs no paid tools or new inbox.

Step 1

Form

A client sends a message.

Step 2

Google Sheet

It’s saved as a new contact.

Step 3

Email alert

He replies from his inbox.

Tested end to end with a real message. It also filters simple spam and limits messages per hour.

05 / Speed

The data was slow, so the page stopped waiting for it.

Testing showed long pauses. Now text appears first, and only prices, places and booking wait for live data.

Before

Blank page until the data arrives

After

Page visiblePrices and places load in place
06 / What comes next

Test cheaply first. Build for launch later.

Google Drive let us prove the idea with no purchases. It’s a deliberate stepping stone, not the final setup.

Now / Prototype

Google Drive

Shared content, one password and photos by link. Good enough to test with the guide.

Next / Launch

Supabase, bookings and a domain

Individual sign-in, photo uploads, faster loading, real payments and automatic places.