First Deploy
A marketing site, built and deployed in one sitting
Session three is the biggest step in the program and it's budgeted as a room: setup happens together, out loud, with the slowest laptop setting the pace. Then the site — structure first, copy from the one-pager you already wrote, pages generated from data you already have — and a deploy on screen. Watching is fine. This is the night where following along pays for itself.
Session one is Tuesday Aug 25 at Workuity Biltmore and Wednesday Aug 26 at Workuity Chandler, evenings at 6:00 PM. Same session — pick the room that works. Nights two through four announced soon; watch Discord and the Meetup calendar.
Venue sponsor: Workuity. Format: the host builds live on screen. Bring a laptop and work along, or just watch — nobody is put on the spot.
Why this session
The site is the one thing every channel points at, and "I'll do it when I know how to code" is the sentence that keeps most builders in the chat window permanently. The agent handles the typing. The judgement — one CTA, proof instead of adjectives, whether a page deserves to exist at all — is what the evening is actually for.
What we cover
- 01
The chat, in your files
What changes when the model can read your project and write to it. No more copy-paste, and an error message stops being the end of the evening and becomes something you paste back.
- 02
Setup, together
Install and authenticate as a room, at the pace of whoever's stuck. This is the slowest fifteen minutes of the program and we plan for it rather than pretending it takes two.
- 03
The one-pager becomes the hero
Your positioning from session one, above the fold, in the customer's words. If it doesn't survive contact with the page, the positioning was the problem — not the design.
- 04
Structure that converts
Section order, one CTA, and proof where the adjectives were. Real sites pulled apart on screen first, so you can see the pattern before you build yours.
- 05
Pages at scale, without the spam
One dataset, many pages. The doorway test comes first: if the only difference between two pages is a swapped noun, it's spam and the whole domain pays for it. Ship a sample of five before you generate five hundred.
- 06
Your articles get a home
The draft from session one goes somewhere real — a canonical, internal links, and a place in the content map rather than a lonely /blog nobody links to.
- 07
Deploy
Git, a deploy account, and a real URL on screen before the night ends. If a build fails, that's the useful part — we read the error and fix it in front of everyone.
You leave with
A live URL with your own positioning on it, plus five programmatic pages that survive a stranger reading them.
To follow along
A laptop with Node installed, a GitHub account, and a deploy account you can log into. Access to Claude Code or the Codex extension — both need a paid plan or an API key with a few dollars on it, so sort that out beforehand. Exact setup steps go in Discord the week before. Not set up in time? Sit next to someone and watch: the template is public and it'll still be there tomorrow.
Afterward
Nothing is required. It compounds if you run the same work on your own product. The suggested output:
03-site/ — if you want somewhere to put it: your deployed URL, the site structure, five sample programmatic pages, and an OG image that renders when someone shares the link.
Everything is open source. Missed the session? It's archived in Discord.
The session kit
Slides, a follow-along guide and skill files. Free to download, room or no room.
.claude/skills/.Download (7) ↓Install this session's skills
curl -fsSLO https://www.shipai.club/skills/day-zero-03-first-deploy.zip
unzip -o day-zero-03-first-deploy.zip -d .What's in the bundle
/site-structureSKILL.mdPlan a marketing site: sections, order, and the job each one does. Use before writing any page copy.
/landing-copySKILL.mdWrite marketing site copy from the positioning brief and apply it to the actual page. Use once the section order exists.
/site-scaffoldSKILL.mdScaffold or extend a Next.js marketing site — routes, metadata, sections. Use when the copy needs somewhere to live.
/content-mapSKILL.mdWork backwards from what the ICP searches to the first twenty pages worth writing. Use before drafting any article.
/programmatic-pagesSKILL.mdDesign a templated page set that is genuinely useful rather than a doorway. Use when one page shape times real data covers many queries.
/og-imageSKILL.mdGenerate Open Graph images so shared links preview properly. Use once routes exist, before anyone shares one.
/perf-passSKILL.mdMeasure Core Web Vitals and fix only what moves a number. Use when the site is deployed and feels slow.
Every program skill is on the skills page.
The community online
Recaps, archive links, questions between sessions, everyone else's work in progress.