Liz McKean
Written byWill Pei YuanLiz McKean is a certified hypnotist and coach who sees clients on Zoom and in person around Tampa Bay. Her site replaced a Squarespace one in November 2026: a short public site she edits herself, with her two podcasts, prices on the page and booking through Acuity, and behind it a private studio where she writes session recaps, uploads recordings and invites clients to a page of their own.
- Role —
- Design and build, end to end, including the research on her old site and the move off Squarespace. A friend introduced us at a venue called Grassroots; I was curious about hypnotherapy, and we met in person after that.
- Timeline —
- October 2026 — ongoing. Research and a first prototype on October 15–16; the editor, new offer, blog and contact form by the end of October; lizmckean.com became the main address on November 13; the client pages followed on November 15–16.
- Stack —
- Astro 7, TypeScript, Keystatic (Keystatic Cloud), Markdoc, Vercel, Vercel Blob (private), Resend, Acuity Scheduling, GSAP, Lenis, Buzzsprout RSS, Vercel Web Analytics, Schema.org structured data
The problem
The brief was three lines: far fewer words, lose the giant-face hero, get off Squarespace. The old site ran past a thousand words on the homepage and showed no prices. Booking and payment already worked in Acuity and were to stay there. Liz also needed to change the site herself, without a developer and without a GitHub account.
What I built
The public site is five kinds of page: a homepage, Work with me, About, a blog, and her privacy policy and terms, which were carried over word for word. The homepage opens on type over an animated tide rather than a portrait, then moves through a "Sound familiar?" passage, a "Listen before you book" audio sample, the sessions and their prices, a plain list of what hypnosis is and is not, a short introduction, testimonials, her two podcasts, Instagram and a closing invitation to a free discovery call. Work with me explains the first session, repeats the prices, embeds the Acuity calendar, answers questions and ends in a contact form.
Everything on those pages is hers to edit. Keystatic gives her an editor at /admin that she signs into by email; each save becomes a commit, and the commit triggers a deploy, so a change is live well under a minute later. Prices, page copy, photos, the contact auto-reply and how each session books (an Acuity link, discovery call first, or not bookable yet) are all fields. The git history shows her saves from November 9 onwards.
The parts that come from elsewhere are pulled in rather than copied. The latest four episodes of each podcast are read from their Buzzsprout feeds at build time, and an audio player persists across page changes so an episode keeps playing while a visitor reads. The Instagram grid loads as a deferred island with a three-hour cache and falls back to photos she has picked if the feed fails. Booking and payment are Acuity throughout; there is no payment code on the site.
The second phase is private. At /studio, behind a password, Liz keeps a list of clients, writes a recap after a session, attaches recordings, and can email the client that it is ready. Each client signs in to their own page with an emailed link, no password: their recaps and recordings, a booking tab with their details already filled in, instructions for rescheduling, and a form that messages Liz. The page can be installed on a phone, and a recap can be read aloud by the device itself.
Design decisions
How it looks and moves, and why.
A tide that breathes, in place of a face
The hero is a dark plum gradient with three layered waves that rise for four seconds and fall for six, and the words "breathe in" and "and let it go" fade in time with them. The headline carries the page: "You can't shame yourself into change." Headings are set in Instrument Serif and body text in Figtree, over a palette named for what it looks like: night sea, podcast plum, lilac, sea glass.
Prices on the page, and a sample before the ask
The sessions and what they cost sit on the homepage and again on Work with me, and a visitor can listen to Liz before deciding anything. In place of a long FAQ, two short lists say what hypnosis is and what it is not. The footer states that she is not a licensed clinician and gives the SAMHSA helpline and 988.
Motion that steps aside
Headings and body text reveal line by line, photographs wipe in with a little parallax, and scrolling is smoothed. All of it is switched off for a visitor who has asked for reduced motion, and anything waiting to be revealed shows itself after a few seconds if the motion never starts, so nothing can stay hidden.
Decisions worth explaining
The engineering, for anyone who wants it.
Embed Acuity instead of rebuilding booking
Liz already took bookings and payment in Acuity. Bookings created through its API come back unpaid, so a custom booking screen would have split payment from scheduling. The site embeds her Acuity calendar and links each session to its Acuity page, and on a client's own page the calendar arrives with their name and email filled in.
Private pages cannot ship as static files
The public pages are static HTML. The studio and client pages must never be, so a small build integration forces every page under those paths to render on demand, where middleware checks the session and marks the response private and unindexed. A new studio page is protected by where it lives, not by remembering a flag.
Sign-in links that survive email scanners
Clients sign in from an emailed link. The links are signed and expire, but they are not single-use, because mail scanners often open a link before the person does and would burn it. A sign-in token is prefixed so it can never be accepted as a session, the login page answers the same way whether or not an address is on file, and a visit is recorded on the page, not on the link, so a scanner does not count as one.
Recordings go straight to private storage
A session recording can be large. It uploads from the browser directly into private blob storage, pinned to that recap's folder, and never passes through the site's server. Playback goes through a short-lived signed link issued only after checking the recording belongs to the client asking.
One folder per photo field, enforced at build
Early on, two pages shared a photo folder and overwrote each other, and one photograph ended up on every page. Each photo field now has its own folder, and a check runs on every build that fails the deploy if folders or files are shared, missing or out of place. An editor's mistake stops at the build instead of reaching the site.
The stack, and why
Each layer, what it runs on, and what it was picked over.
- Framework
Astro
Pages are static by default, which suits a site that is mostly words and photographs; only the editor, the forms and the private pages run on demand.
- Editing
Keystatic Cloud
She signs in by email with no GitHub account, and each save is a commit, so content has history and a deploy follows every change.
- Booking and payment
Acuity Scheduling, embedded
It already held her calendar and took payment. The site links and embeds it and carries no payment code of its own.
- Client data
Private Vercel Blob
Clients, recaps and recordings are files in private storage. There is no database to run for what is a short list of people and their notes.
Resend
Contact notifications, the auto-reply, sign-in links, invitations and "your recap is ready" all go out through one branded layout with a plain-text version.
← All work“My Squarespace hypnotherapy website had been a source of overwhelm for a long time- truly a barrier to growth. I'd been patching it as my business evolved, and people could get a sense of who I was but not what I do or how to work with me. Will saw the heart of my old site and built something brand new after just a couple of conversations, where he asked great questions and really listened. The result is beautiful, elegant, and as easy for me to edit as it is for the client to navigate. Now when I look at it I feel excited about my business instead of overwhelmed. He integrated my podcast in a way I didn't know was possible and built a client portal that will add enormous value for my clients! Will is a dream to work with. He's a brilliant communicator, patient and kind, full of great ideas, and lightening fast. I felt like I had a real partner in this project- he cares so much! This is more than a website, it's a turning point for my business, and I couldn't be more thankful.”