Setup guide
Get your site live in six steps
Your site is already working — these steps make it yours. Do them in any order; nothing here is a barrier to going live.
1 · Make it yours
Set your name, tagline, brand color, and the words on your pages. Your site starts as a working template — this turns it into your brand.
Where: Dashboard → Settings, and the Getting Started checklist
2 · Connect your details
Add your contact info so the contact form routes to you, and paste your analytics IDs so you can see your traffic. Tracking and security settings wire up automatically once an ID is saved.
Where: Settings → Business details · Settings → Analytics
3 · Add your content
Fill in your services, About page, blog posts, and FAQs. Every word on the public pages is yours to edit — no design work required.
Where: Settings → Content, and the marketing pages
4 · Turn on what you sell
Switch on the features you need — a member portal for your customers, events, a giveaway, the built-in games — and hide the ones you don’t. Each one works the moment it’s enabled.
Where: Settings → Features · Settings → Member portal
5 · Go live
Run the launch-readiness check, connect your own web address when you’re ready, and invite your team. When the checklist is green, you’re open for business.
Where: Dashboard → Getting Started → Launch readiness
6 · Keep getting updates
Your site is a copy of a template that keeps improving — new features, fixes, faster pages. You get them by merging, and it stays easy as long as you edit in the places marked as yours. Do it whenever you like; nothing expires.
Where: In your own repo: UPGRADING.md — the merge ritual, start to finish
Staying on the upgrade path
Updates arrive by merging, and one habit keeps that merge boring: change the values, keep the shape. Every file says at the top who owns it — LANE is yours to edit freely, CORE and FRAMEWORK are ours to maintain. Put your words, colours and pages in the lanes and an update is usually a no-op. Edit our files to change content and every future update becomes a merge you have to referee.
When a merge does stop on a conflict, it is almost always a file you customised that we also improved — your side wins for content, ours wins for a page that has graduated into the framework, and UPGRADING.md walks through both plus the one file where neither answer is right. Run pnpm install before you build afterwards, and pnpm verify tells you the contract still holds.
Want to reshape the site itself?
The whole front end is yours to customize with an AI assistant — new pages, new sections, a different layout. The build guide walks through how.
Read the build guide →Once it is live: getting found
Being online and being findable are two different jobs. Six free steps decide whether search engines and AI assistants can see you at all — including the one that decides whether ChatGPT can recommend you.
Read the getting-found guide →Signed in already? Your live checklist tracks these steps for you on the Getting Started page. You can always come back to this guide from there.