👇 After this module

The right pages for your business, customised to your brand. The auth flow. The email sequences. The course release pattern. The dignity of a clean account section. You pick what fits. Less is better. Everything else waits in the bundle, brand-neutral, ready for when you need it. Owned by you. No SaaS rent.

Choose the pages your business actually needs

You do not need 27 pages. You need the right pages for your business, and for most solopreneurs that is four to eight to start. A clear homepage. An about page that lets someone trust you. A way to contact you. A way to pay you. That is already more than most solopreneur businesses have online today.

Every page on your site does a different job. Your homepage decides whether someone stays. Your about page decides whether they trust you. Your services page decides whether they buy. Your contact form decides whether they reach out. The fastest way to lose someone is to confuse those jobs, or to bury them under pages you did not really need.

What the bundle gives you, grouped by job

Each page is in the library. You pick what your business needs right now. Most solopreneurs ship 4 to 8 pages and add the rest as they grow.

Pick few, ship well

Build only what your business actually needs today. A coach starting out may only need a homepage, about, services, contact. A consultant adding a paid newsletter adds two more. A course creator adds member area pages later. The bundle is a library, not a checklist.

The point of having all of them brand-neutral and ready: when you do need a privacy page or a password reset flow, it is already in your repo. No scramble. No new tool. Switch it on.

Mark complete Next Lesson

Your brand, in one place

Open most solopreneur sites two years in. The homepage uses one shade of your colour. The contact page uses a slightly different one. The newsletter looks like it was put together by a different person. Tiny drifts, almost invisible one by one, and yet the cumulative feeling is "this person did not quite finish."

The fix is not a design system tool or a brand audit. The fix is one file that holds your brand, and every page reads from it. Edit a colour there, every page picks it up. Add a font, every page picks it up. The drift becomes structurally impossible.

The pattern

Your template ships with one folder for brand and one folder for shared markup.

brand/
  intake.md       your filled-in brand profile
  tokens.css      CSS variables, generated from intake
  typography.css  font loader
  logo.svg
  images/         hero, avatar, og-default

_shared/
  header.html     the nav, edited once
  footer.html     the footer, edited once
  styles.css      global stylesheet, reads from tokens
  site.js         loads partials into every page

Every page on your site has the same skeleton.

<link rel="stylesheet" href="/brand/tokens.css">
<link rel="stylesheet" href="/_shared/styles.css">

<header data-include="header"></header>

<!-- page content -->

<footer data-include="footer"></footer>
<script src="/_shared/site.js" defer></script>

Change a colour in tokens.css, every page you have shipped updates. Add a nav item to header.html, every page picks it up.

The intake mechanism

You do not edit tokens.css by hand. You fill in brand/intake.md with your brand details (logo, fonts, colours, voice notes), and Claude generates tokens.css from it. When your brand evolves (new accent colour, new font), you update intake.md and re-generate. The intake is the source of truth.

Mark complete Next Lesson

What you give, what you sell

Most online businesses have one tier: pay or do not access. Some have three: free, paid, premium. Almost none of them think about what each tier is actually offering.

A tier is not "how much content." A tier is the relationship you offer at that price. Free is a hand-shake. Paid is a working agreement. Premium is a partnership. If you set up tiers without that frame, you end up giving away too much (and resenting it) or charging too much (and confusing people).

Three relationships, three sentences

Before any code, write the relationship for each tier in one sentence. If two of them could be confused, the tiers are wrong.

• Free. What does someone get for the cost of an email address? Enough to be useful, not enough to replace the paid thing.
• Paid. What does someone get for a sustainable amount? Usually the bulk of your work, the thing you would feel proud to charge for.
• Premium. What does someone get at the highest tier? Almost always access to you in some form. Calls, priority support, real attention.

How it works once it is set up

The bundle ships with a small database migration that creates three tiers by default. When someone signs up, they land on Free automatically. When they buy, the Stripe webhook moves them to Paid or Premium and unlocks the right pages. You do not maintain a spreadsheet. You do not flip switches by hand.

Every gated page asks one question: "is this person at this tier or higher?" One line of code, the same shape on every page. If you add a new tier later (say, between Paid and Premium), every existing page still works. You do not refactor.

Mark complete Next Lesson

How members sign up and log in

The four most-touched moments in your business: someone logs in, signs up, resets their password, confirms their email. They are not sexy lessons to build. Nobody notices when they work. Everybody feels it when they break.

This is one of the quiet places where solopreneur businesses lose paying members. Not because of pricing. Because the password reset link timed out, or the confirmation email never arrived, or the login button said "Sign In" on one page and "Log In" on another. Small things. Members read them as "this person is not really running a business yet" and they leave.

The five pages, what each does

• Login. Email and password. That's it. Magic link is tempting but adds an SMTP setup most people skip; password works everywhere on day one.
• Signup. Name, email, password. Triggers a confirmation email. Auto-creates the profile and assigns the free tier.
• Reset password (request). Email field. Triggers a reset email with a one-hour token.
• Reset password (confirm). Where the reset link lands. New password and confirm. On success, redirect to login.
• Email confirm landing. Where the "confirm your email" link lands. Three states: loading, success, error.

What a login actually protects

Worth understanding once, because clients will ask you. Every page of your site is readable code: anyone can fetch a URL and view the source, with or without logging in. That is how the entire web works, your bank included, and it is safe by itself. The login check on a page runs after the page has already arrived in the browser, so treat it as navigation for honest visitors rather than a vault for the page itself.

What login DOES protect is data. After sign-in, Supabase ties every request to the member's session, and Row Level Security decides what that session may read, enforced by the database on each request (Module 5 covers this). So the rule that keeps the whole build safe: pages carry presentation, the database carries everything personal, behind server-side rules. Keep secrets and client data out of pages and the visible code stays a feature of the web instead of a risk.

Why magic link looks easy but breaks

"Email me a link to log in" feels modern. It needs your SMTP configured for transactional email, your domain verified, your link expiry tested. Most people skip these and ship magic link without realising it works for them but not for the customer in Outlook with strict filters. Password is boring and works.

Why a confirmation email matters

The confirmation email is the first email someone receives from your business. It is also the email most people half-design. Three things to nail:

1. It lands in inbox, not promotions (depends on your sender domain, your DKIM/SPF, and the List-Unsubscribe header)
2. It loads on mobile (inline styles, table layout, 600px wide)
3. The button works (you tested it after deploy, on a real device)

Mark complete Next Lesson

Email as a relationship, not a funnel

A funnel narrows people down toward a buy button. A relationship widens, slowly, into trust. When someone gives you their email, you have been handed something rare. The sequence that follows is the first conversation between you and them. Treat it like one.

Most "email funnels" feel cold because they are written to convert, not to connect. People can feel the difference in the first line. A relationship-shaped sequence reads like a letter from someone who is genuinely glad you are here. Five short notes, each landing one specific thing, no pressure to buy anything.

The shape of the first week

Five touchpoints over seven days. Each one short. Each one a different kind of warmth.

• Day 0. Welcome. One useful thing they can use today. One question you genuinely want them to answer. The reply is the start of the relationship.
• Day 1. A story. A specific moment from your work, told in your voice. Not a case study. A real moment.
• Day 3. Something you got wrong. The mistake you learned from. Honesty is the fastest way to trust.
• Day 5. Something they can use. A small tool, technique, or question that helps them today.
• Day 7. Where to next. Not a pitch. A gentle "if this resonated, here is more of the work."

200 to 400 words each. Subject lines that name the specific thing inside, not "Day 3 of your sequence."

The four languages inside one sequence

A funnel speaks only Mind: logic, value, action. A relationship speaks all four. Day 1's story is Heart. Day 3's honesty is Soul. Day 5's tool is Mind. Day 0's "reply and tell me what you are working on" is Body, the human on the other side typing back. When all four show up, the sequence stops feeling like marketing.

What you should never promise

The fastest way to break a new relationship is to promise something you have not actually built. Some specific traps:

• Do not promise "we will send a reminder the morning of the event" unless something actually sends it.
• Do not promise "weekly emails" unless you have written four in a row recently.
• Do not promise "join our community" unless the community exists at that link today.

Every promise is a small debt. Pay it back, or do not make it.

Mark complete Next Lesson

Release your course

Before you build the third lesson page, there is one quiet decision to make: how do members actually get access to your modules? Most people skip this and let the platform decide for them. The default is rarely the right answer for the kind of course you are building.

The three patterns

All-at-once.

Member buys, gets the whole thing today. Best for small courses, expert audiences, or content people are meant to pace themselves through. Lowest support load. Easiest to refund.

Drip.

Member buys, gets module 1 today, module 2 next week, and so on. Forces pacing. Best when overwhelm is the failure mode of your topic (it usually is). Members refund less, because they have not seen the whole thing in 24 hours.

Cohort.

Everyone in this group gets module 1 on the same day, module 2 a week later, and so on, together. Best for live-taught courses with weekly sessions. The shared rhythm is what makes a cohort feel like a cohort. Highest support, highest engagement.

How a release date works in your bundle

Every module page has a quiet line near the top: a release date. If today is before that date and the visitor is not you (the admin), the page sends them back to the part overview with a kind "Available [month]" note. If today is on or after the date, the lesson opens. That is the whole gate.

For drip you set a different release date on each module. For cohort you change the date on each new round. For all-at-once you remove the line. Three patterns, one place to edit, no platform vendor in between.

You always see everything as the admin. The bundle uses a small is_admin() check (set up in Module 5) so you can build and review without ever pretending to be a student.

The dashboard, as a soft landing

After login, members do not land in a course catalogue, they land in their dashboard. A welcome with their name. A "continue where you left off" card pointing to their current lesson. A grid of modules with progress, the locked ones gently dimmed. Nothing fancy.

The "continue" card is the small thing that does the most. Half the value of a course is showing up the second time. People come back two weeks later, see their last lesson, click resume. Without that card, most of them bounce, not because the course was bad, because they could not remember where they left off.

Mark complete Next Lesson

Your account area, with care

The account area is a Heart space. It is where the people who pay you go to manage themselves. Their name. Their photo. Their plan. How they cancel if their life changes. Whether they keep getting your emails. The whole thing speaks loudly about how you see them, even if no single page is visible from the outside.

The fastest way to lose someone who has been paying you for two years is to make it hard for them to leave gracefully. The fastest way to keep someone who is having a hard month is to let them pause without an awkward conversation.

The two sub-pages everyone needs

• Profile. Name, bio, avatar URL. Nothing complex. Saves to a profiles table. Email is read-only here (changes go through the auth flow for security).
• Password. New password, confirm, save. Different from the reset flow because the user is already logged in.

These two work the moment you wire up Supabase auth. They are the floor.

Two more sub-pages, only if you actually wired them up

The bundle ships with two more cards, both commented out by default. Only switch them on once the thing behind them really works. A page that looks like it manages something it does not actually manage is worse than no page, because members think they cancelled or unsubscribed when they did not, and you get angry emails six months later.

• Membership. Only enable if you have Stripe Customer Portal wired up. The page becomes one button: "Manage subscription," which redirects into Stripe's hosted portal where Stripe handles plan changes, card updates, billing history and cancellation. If you sell lifetime or one-time access (no subscriptions), you may not need this card at all, the dashboard already shows what they own.
• Email preferences. Only enable if your audience emails are sent from your own Supabase + Resend setup. If your newsletter lives on Beehiiv, Mailchimp, ConvertKit, Substack or any other platform, do not add this. Toggling it would not do anything, and members would still receive emails from the other platform. Link them to the unsubscribe in that platform's footer instead.

Let Stripe handle billing

Do not build your own billing UI. For subscriptions, the membership page has one button: "Manage subscription." It calls a small edge function that creates a Stripe Customer Portal session and redirects there. Stripe handles plan changes, card updates, invoice history, and cancellation, all on their hosted page, with their compliance and their support flows. You skip a month of work and a long list of edge cases you would have to maintain forever.

For lifetime or one-time purchases, there is nothing to manage. The page just confirms what they own. If something goes wrong, they email you. Most one-time customers will never visit this page; that is fine.

If you sell to people in the EU, GDPR matters

If any of your customers are in the EU, the law gives them rights to access their data, correct it, delete it, export it, withdraw consent. You do not have to build buttons for any of it on day one. A line on the account page like "to export or delete your data, email support@yourdomain" is a reasonable, respectful way to start, and it lets you handle the rare request by hand instead of maintaining a deletion flow you have not actually written yet. Consider buttons later if the volume justifies it. Email preferences with proper opt-in defaults are the one piece worth doing regardless of where your customers are, because it is just kinder.

Mark complete Next Lesson

Lessons that breathe

A lesson is not a wall of text. The lessons that land are the ones with rhythm. 🎥 A short video at the top so members hear your voice. A line of code they can copy. A soft callout for the thing easy to miss. A worksheet to download. An image that shows, not tells. A resource card that points to where to go next.

The bundle gives you a small library of these elements, all reading from your brand, all copy-paste ready. You decide which ones each lesson needs. Some lessons are pure text. Some are mostly video. Some are a single audio file with a transcript. The structure adapts to the content, not the other way around.

The elements you have

• Video. Four hosting options with pros and cons (self-host, YouTube unlisted, Vimeo, Loom). Pick one and stick.
• Audio. A pill-shaped player for meditations, podcast clips, voice notes. Same hosting rules as video.
• Callouts. A soft cream box with a title, for the "one thing to watch for" moment in a lesson.
• Code blocks. Both inline (a single command word) and block (multi-line, copy-paste).
• Images with caption. A figure with a muted italic caption underneath.
• Resource cards. Icon + title + description + chevron, for linking to docs, tools, or external pages.
• Downloads. A button that saves a worksheet or PDF instead of opening it.
• Generic embeds. Tally form, Cal.com booker, Notion page, Figma frame, anything iframe-able.

Where they live

Two reference points in the bundle:

• body/website/_shared/lesson-elements.html — every element rendered with the exact HTML snippet underneath. Open in a browser, copy what you need.
• body/website/course/module/example/index.html — the example module ships with five lessons, each demonstrating ONE element type in context (Lesson 1 video, Lesson 2 audio, Lesson 3 callouts and code, Lesson 4 images and embeds, Lesson 5 resources and downloads).

The video decision

The biggest call inside lesson elements is where to host video. Four real options, each with real tradeoffs.

Self-host on your hosting (Hostinger, etc).

Plays on your domain, no platform branding, no monthly fee. Slow seek on big files, no adaptive bitrate, downloadable unless you proxy. Best for small cohorts, files under 200 MB.

YouTube unlisted.

Free, fastest globally, captions auto-generated, adaptive bitrate. YouTube branding visible, "Up next" suggestions, can be flagged for music. Best for public-facing or marketing content.

Vimeo Pro (~€10/mo).

Clean player, domain locking (a soft tier-gate), no ads. Paid every month, still on Vimeo's domain. Best for paid courses where you want some protection.

Loom.

Easiest recording flow on the planet, free tier covers a lot. Loom branding prominent, transcripts public on free, not built for course delivery at scale. Best for office hours and quick walkthroughs, not production lesson video.

Mark complete Next Lesson

Turn one recording into many

✨ You ran a live session. A Q&A, an AMA, a workshop, a podcast appearance. The recording is sitting on your drive. Most of the value is locked in there until someone presses play on the whole thing, and almost no-one does.

The recap page turns one recording into a navigable little archive. Filter by topic. Click a question, the audio jumps straight to that answer. One audio file, many clips. Cheap to host, fast to load, easy to share. The same hour of work, gently re-given to the people who were not in the room.

When this format earns its keep

• Q&A or AMA sessions where listeners want to jump to a specific question
• Live cohort calls or workshops with clear topic shifts
• Podcast appearances you want to host on your own site
• Office hours or community calls worth keeping

When to skip it

If your session was scripted and linear, skip this format. Upload the recording, link to it, you are done. The recap pattern earns its keep through navigation. If there is nothing to navigate, the extra work is not worth doing.

How it gets made

The bundle ships with a small skill called /session-recap. You drop the recording in, name the questions, the skill handles the rest: it tidies the audio, transcribes it locally on your machine (no upload, no third party), matches each question to where it lives in the audio, and writes the page. You walk away with one HTML file you can ship.

Live example on this site: /ama-faq. 32 questions, one audio file, the full session as a podcast and a clip per question, all from the same recording.

Watch a recap page get built from one recording.

Mark complete