By Sunday you have a URL, not a plan for a website

Name it, claim an address that resolves, fill a catalog that argues rather than lists, and publish one page that does the persuading. Seven short trainings, each ending with something changed on a real screen.

See what's inside

3
Modules: 7
Practical lessons: Free
No card required: 1-to-1
A coach reviews your work

The gap between having material and having somewhere to send people

You have the material. Slides from a workshop you've run eleven times, a recording someone asked you to make, a document you keep sending to clients because you got tired of explaining it. What you don't have is an address.

So the plan becomes a website. And a website is a project — a designer to brief or a template to fight, pages that need copy you haven't written, a domain in a state of half-configured, and a launch date that moves twice. Three months in, the material is still in a folder.

The version that works is smaller and it fits in a weekend, because the thing you actually need is not a website. It's one address that loads, a catalog someone can understand the order of, and a single page with one job.

By Sunday evening

Your academy has a name and one line under it that tells a stranger whether they're in the right place
Your address resolves — you can open it in a private window and see your own school
Every course you have is deliberately Public, Unlisted or Private instead of on whatever it defaulted to
The five lines above your catalog are written and live, so nobody lands on a bare list
One page is built from four sections, published, and reachable by someone who has never signed in
Three people have opened it and told you the one sentence that only made sense inside your head

What you'll cover

1
Module 1 — Name it and claim it
The name, the line under it, and an address that resolves. About thirty minutes, and afterwards your academy is somewhere rather than an intention.
2
Module 2 — Fill it, then say who it's for
A catalog that argues rather than lists, the five lines that sit above it, and one page that does the persuading. This is the bulk of the weekend.
3
Module 3 — Capstone: publish it
Three settings decide whether anyone can actually reach your page. Then you send the URL to someone and watch what they do with it.

This is for you if

You have course material, a workshop, or a programme you've run before, and no place to put it
You've been meaning to build a website for somewhere between four months and four years
You'd rather have something live and imperfect this weekend than something perfect in the spring
You want to send one link when someone asks what you do, instead of three attachments
You've taken Course 1 and have an outline and a recorded training with nowhere to live

Why this one is different

You build it here, on this screen

Every training ends on a real setting in a real academy — your own. There is no worksheet and no hypothetical example: the thing you're learning on is the thing you're building.

One page, not a website

Four sections is a complete page and it takes an afternoon. The course is deliberately narrow about this, because the website is the project that eats the launch.

It names the settings that actually break things

Published but invisible. A half-finished course sitting Public. A hero that renders as nothing because one required field was blank. These are the real failures, and the course is mostly about them.

Questions

Do I need a course finished before I start?

No. You need something to put on a shelf — a course, a workshop you've run, or a single recording. If you have nothing at all, take Your First Course in 5 Days first; it produces an outline and one recorded training, which is enough to fill a catalog.

Does it really take a weekend?

Seven trainings, none longer than about ten minutes, and the work between them is maybe four hours in total. The longest single piece is building the page, which is an afternoon. All seven are open from the moment you join — nothing is scheduled, so if you have one free Saturday you can finish on Saturday.

I already have a domain. Should I use it?

Not this weekend. A subdomain resolves the second you save it; a custom domain involves DNS records and a wait where nothing is broken except that nothing works yet. The course covers why the order matters — get a working academy first, then spend fifteen minutes pointing the domain at it.

I can't write copy. Is that a problem?

The page can be drafted for you from a description of what you want, and then you edit it. But the parts that decide whether it works — the line under your name, your headline, your three credentials — are short and specific rather than well-written, and the course is mostly about making them specific.

What happens after the course?

You have an academy that doesn't notice anything. Someone joins, opens one training, goes quiet, and nothing follows up. That's the next free course. Or book twenty minutes and we'll look at your live academy together.

It's a weekend

Seven short trainings and a URL at the end of them. Everything is open the moment you join, so the only scheduling decision left is which Saturday.