Skip to main content

Settings

Color Mode

Theme Skin

Background

Appearance preferences are saved in this browser only.

Environment

Current Environment Production

Built with JEKYLL_ENV=production. Changes require deployment.

Quick Links

Theme & Build

Theme
Jekyll v3.10.0
Last BuildOct 18, 02:30
Changelog Docs Jekyll

Page Info

Layout welcome
Collection none
Path index.md
URL /

Source Code

Set repository: USER/REPO in your _config.yml to enable source-code shortcuts.

zer0-mistakes remote theme

Welcome — your site is live!

GitHub Pages built this page from just three files in your repository. The layout, styles, and this entire onboarding screen are served by the remote theme.

Use the wizard below to generate a personalised _config.yml, drop it into your repo, and your site will look like your site instead of this welcome page.

Start the wizard Minimal starter
Your repository right now
  • _config.yml required
  • Gemfile required
  • index.md required
  • pages/ optional
  • assets/ optional
Everything else — layouts, styles, navigation, search — is provided by the remote theme.

The 3-file starter

The only files you need in your repository for GitHub Pages to render a full site through the bamr87/zer0-mistakes remote theme.

The minimum viable configuration:

# _config.yml
title:        "My Site"
description:  "A site rendered by the zer0-mistakes remote theme."
url:          ""
baseurl:      ""

# Pull layouts/includes/assets from the published theme
remote_theme: bamr87/zer0-mistakes

# GitHub Pages whitelisted plugins
plugins:
  - jekyll-remote-theme
  - jekyll-feed
  - jekyll-sitemap
  - jekyll-seo-tag

# Hide this welcome screen once you're configured
site_configured: true

Use the wizard below to generate a richer file with collections, analytics, and social links.

Required when building locally; GitHub Pages installs these for you in CI.

# Gemfile
source "https://rubygems.org"

gem "github-pages", group: :jekyll_plugins
gem "jekyll-remote-theme"
gem "webrick", "~> 1.7"

While the site is unconfigured, layout: welcome shows this onboarding screen. Once you set site_configured: true in _config.yml, the same file renders your own home-page content. 

---
layout: welcome
title: Home
---

# Welcome to my site

Replace this with your own content. The setup wizard
will disappear automatically once `site_configured: true`
is set in `_config.yml`.

zer0-mistakes

Site Builder

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

Draft saved

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
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.
Sent with every request; the proxy can pin one with CHAT_MODEL / XAI_CHAT_MODEL.
Renders hero, logo and post images straight into the project's assets/.
How do you want to work?

How to connect (once, on your machine)

  1. 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
  2. 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
  3. 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.

0 of 0 required ready
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.

The brief is not published; it steers the drafts.
Shown in the navbar, browser tab and feed.
Meta description for search and social cards. Aim for 120–160 characters. 0/160

GitHub & URLs

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

Also the project folder name in the Build step.
How will the theme be loaded?
Empty for user.github.io; /repo for project sites.

Structure

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

Kind of site
Collections
Navigation style
Landing page
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
Applies theme_skin in _config.yml.
Palette layered over the skin
The quick brown fox jumps over the lazy dog. Headline weight.
Corners

Voice & first content

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

Tone

Integrations

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

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.

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.
…/
Created beside the theme checkout. Must be new or empty unless you allow overwriting.
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
  1. Download Bundle from the preview panel and run it: bash zer0-site-bundle.sh my-site
  2. Start the dev server: cd my-site && docker compose up
  3. Open http://localhost:4000/. Edit a file — the page reloads by itself.
  4. Publish: gh repo create my-site --public --source=. --push then enable Pages in the repository settings.
Copied

Next steps

Add content

Create a pages/ folder with collections like _posts/, _docs/, or _about/. Enable them in _config.yml.

Content guide
Customise styles

Drop an assets/css/user-overrides.css file in your repo to override theme styles without forking.

Customisation
Source & issues

File issues, submit PRs, or fork the theme on GitHub. Contributions welcome.

Repository