zer0-mistakes

Site Builder

Answer a few questions — or just talk to Claude or Grok — and leave with a running site.

Draft saved

Step 1 of 9

Connect your AI

The builder runs entirely in your browser. Connect Claude or Grok through the local dev proxy with your own token and it can fill in these forms, check your machine, read the theme's source, write or modify your project, generate images and start Docker — in the order you choose.

Looking for the dev proxy…

Checking

AI provider

Claude Anthropic proxy offline Claude Code OAuth token (Pro/Max, from `claude setup-token`) or an Anthropic API key.

Grok xAI proxy offline xAI API key — Grok for the session, Grok Imagine for images.

Token for Claude

Mint one with claude setup-token. The token goes once to the local proxy and stays in its memory — never in this page or your browser storage.

Also save it to .env (mode 600) so the proxy remembers it next time

Model

Sent with every request; the proxy can pin one with CHAT_MODEL / XAI_CHAT_MODEL.

Image generation

Renders hero, logo and post images straight into the project's assets/.

How do you want to work?

Guided steps Walk the nine steps; the assistant suggests values and fills each one in.

Open session Just talk: build from a brief, open an existing site, edit files, generate images, rebuild — in any order.

How to connect (once, on your machine)

Start the dev proxy next to the site

Node 20.6+. It starts without any key and waits for the token you paste above; --env-file=.env loads keys you saved earlier.

node --env-file=.env templates/deploy/chat-proxy/dev-proxy.mjs
Get a token from the provider you picked

Claude: a personal OAuth token from the Claude Code CLI (Pro/Max) or an API key from console.anthropic.com. Grok: an API key from console.x.ai.

claude setup-token
Paste it above — or keep it in .env

Pasting keeps the token in the proxy's memory for this run (tick the switch to save it). Or put it in the git-ignored .env yourself and restart the proxy.

CLAUDE_CODE_OAUTH_TOKEN=sk-ant-oat01-… # or XAI_API_KEY=xai-…

What the proxy is allowed to do

Hold the token you paste in memory only; write it to .env (mode 600) only when you tick the switch; report it masked.
Run a fixed list of read-only version checks (Docker, Git, gh, VS Code, Node, Claude CLI).
Read text source files inside the theme checkout — never .env, keys or build output.
Write generated files into a folder beside the theme (never inside it), and read, edit, add or delete text files inside a site you open there — each change behind a confirmation card.
Save generated images (PNG/JPEG/WebP only) under that site's assets/.
Run docker compose up / ps / logs / down / build and git status / diff / log / init in that folder — nothing else.

No proxy? Continue anyway. Every step still works and the Build step gives you the files and the commands to run yourself.

Prerequisites

Docker runs Jekyll for you, Git and the GitHub CLI publish it. Connected? Press Run checks. Otherwise tick each item as you install it.

macOS Windows Linux

0 of 0 required ready

Docker Desktop required not checked

Runs Jekyll in a container so you never fight Ruby versions.

Install & verify

Install
brew install --cask docker

Verify
docker --version && docker compose version

Docs

Done
Docker engine running required not checked

The compose commands need the engine up, not just installed.

Install & verify

Install
open -a Docker

Verify
docker info --format '{{.ServerVersion}}'

Docs

Done
Git required not checked

Version control for your site and the theme's release flow.

Install & verify

Install
brew install git

Verify
git --version

Docs

Done
Git identity configured required not checked

Commits need a name and email; use your GitHub no-reply address.

Install & verify

Install
git config --global user.name "YourGitHubUsername" && git config --global user.email "ID+username@users.noreply.github.com"

Verify
git config --global --list | grep user

Docs

Done
GitHub CLI required not checked

Creates the repository and enables GitHub Pages from the terminal.

Install & verify

Install
brew install gh

Verify
gh --version

Docs

Done
GitHub CLI signed in recommended not checked

Needed to push and to turn on Pages; the local build works without it.

Install & verify

Install
gh auth login

Verify
gh auth status

Docs

Done
VS Code recommended not checked

Recommended editor with Jekyll, Liquid and Docker extensions.

Install & verify

Install
brew install --cask visual-studio-code

Verify
code --version

Docs

Done
Node.js 20.6+ recommended not checked

Runs the local Claude dev proxy (node --env-file) that powers this wizard's AI.

Install & verify

Install
brew install node

Verify
node --version

Docs

Done
Claude Code CLI recommended not checked

`claude setup-token` mints a Claude OAuth token for the session (an xAI key from console.x.ai works instead).

Install & verify

Install
npm install -g @anthropic-ai/claude-code

Verify
claude --version

Docs

Done

On macOS you can install everything at once: brew install git gh node && brew install --cask docker visual-studio-code Full guide: Machine Setup.

Site identity

Describe the site in your own words first — the assistant uses that brief to draft everything else.

What is this site about, and who is it for?

The brief is not published; it steers the drafts.

Site title *

Shown in the navbar, browser tab and feed.

Subtitle (optional)

Tagline (optional)

Description

Meta description for search and social cards. Aim for 120–160 characters. 0/160

Author / owner

Contact email

GitHub & URLs

Where the code lives and where the site is served from.

GitHub username

Repository name

Also the project folder name in the Build step.

How will the theme be loaded?

GitHub Pages (remote theme) Zero-install hosting; the theme is pulled from GitHub at build time.

Ruby gem + Docker Pins jekyll-theme-zer0 in the Gemfile; builds anywhere Docker runs.

Site URL

Base path

Empty for user.github.io; /repo for project sites.

Permalink style

Dev port

Remote theme

Structure

Pick a starting shape, then fine-tune the collections and the top navigation.

Kind of site

Blog Documentation Portfolio Digital garden Blog + docs Cookbook

Collections

Posts Dated articles listed newest-first; the blog.

Docs Evergreen guides with a sidebar tree.

About Who you are, contact, and site settings pages.

Notes Short Obsidian-style notes with [[wiki-links]] and backlinks.

Quickstart Ordered onboarding steps with prev/next navigation.

Notebooks Rendered Jupyter notebooks.

Quests Gamified learning paths with levels and badges.

Recipes A cookbook: structured recipes with serving scaling and unit conversion.

Navigation style

Flat Grouped

Sidebar

Landing page

Minimal Title, one paragraph, latest posts. No hero.

Hero + features Big headline with calls to action, three feature cards, a closing CTA.

Showcase Hero, a card grid of highlights, a pull quote, and a CTA. Portfolios and cookbooks.

Docs hub Hero with a primary Read-the-docs CTA, three getting-started steps, topic cards, FAQ.

Editorial Left-aligned hero, the latest writing, a short manifesto, a subscribe CTA.

Example pages 0

Each row becomes a real file with front matter. Bodies come from the assistant, or are drafted from the title.

Main navigation

Appearance

Seven skins re-colour every component and background layer. Preview any of them on this page.

Skin

Air Light, calm, airy blues

Aqua Deep ocean blue with bright cyan

Dirt Earthy browns and sand

Neon Hot pink and electric blue

Mint Forest green and fresh mint

Plum Royal purple and violet

Sunrise Warm orange and cream

Applies theme_skin in _config.yml.

Colour mode

Lock the colour mode (hide the toggle)

SVG background layers (gradient, pattern, noise)

Palette layered over the skin

Skin colours Ocean Forest Sunset Graphite Berry Sand Midnight Citrus Custom

Primary

Secondary

Accent

Fonts

The quick brown fox jumps over the lazy dog. Headline weight.

Corners

Sharp Soft Round

Navbar icon (Bootstrap icon name)

Voice & first content

Set the tone, then let the assistant draft the welcome post and about page — or write them yourself.

Tone

Friendly Technical Editorial Playful Formal

Audience

Welcome post title

Welcome post body (Markdown)

About page (Markdown)

Integrations

Everything here is off-by-default safe: nothing sends data until you add a key, and keys never go in _config.yml.

AI chat assistant Page assistant answered by Claude or Grok through the chat proxy. Needs the proxy deployed before it shows.

Chat provider

Written as ai_chat.provider; the site's chat proxy needs the matching key (.env.example lists it).

Improve-this-page widget Readers file well-formed GitHub issues from any page. No token needed.

Giscus comments Comments stored as GitHub Discussions. Needs repo + category IDs from giscus.app.

Repo ID

Category ID

Get both from giscus.app after enabling Discussions on the repo.

PostHog analytics Consent-gated, production-only analytics.

PostHog project key

Obsidian wiki-links [[wiki-links]], embeds, callouts and a local graph on every page.

Google Analytics 4 ID (optional)

X / Twitter

Preview-image renderer (optional)

Pre-configures preview_images in _config.yml for the theme's preview-image generator; the key goes in .env.

Build & launch

Every file is in the preview on the right. Write the project and start Docker from here, or take the files and run the commands yourself.

Modify an existing site

Any site under the target root — one this builder wrote, or one you copied there. The assistant can then read, edit and add files, generate images and rebuild it.

Project folder

…/

Created beside the theme checkout. Must be new or empty unless you allow overwriting.

Allow replacing files that already exist there

Open site

Connect the dev proxy (step 1) to write and run from here. Without it, download the bundle and run the commands below.

Run it yourself

Download Bundle from the preview panel and run it: bash zer0-site-bundle.sh my-site
Start the dev server: cd my-site && docker compose up
Open http://localhost:4000/. Edit a file — the page reloads by itself.
Publish: gh repo create my-site --public --source=. --push then enable Pages in the repository settings.

AI session

guided

offline

Not connected. Start the dev proxy and connect Claude or Grok on step 1. The assistant can then read your answers, fill in the forms, check your machine, read the theme's source, write or modify your project, generate images and run the build.

Everything else on this page works without it.

Message the assistant

The assistant sees every answer on this page. Actions ask for confirmation first.

Generated files

live

Loading…

Copied

Layout	`default`
Collection	`none`
Path	`pages/setup.html`
URL	`/setup/`

Settings

Language

Color Mode

Theme Skin

Background

Environment

Theme & Build

Admin

Page Location

Page Info

Source Code