What's next?
Your local copy is live. Here's how to make it yours — then how to put it online.
Make it yours
Point an AI coding agent at the repo, or edit it by hand — all of these work well here.
Claude Desktop can read and edit files in a folder on your computer through a built-in extension. It'll ask you to approve each change before saving it.
Codex now lives inside the ChatGPT desktop app. A “local environment” points it at a folder on your computer so it can edit files there directly.
Open a terminal in the folder the install script created, and start Claude Code there.
cd ~/projects/opensource/gravity claude
Same idea — start Codex in the repo and describe what you want changed.
cd ~/projects/opensource/gravity codex
app/controllers/page logic — pulls data, calls theme_render()app/routes/URL → controller wiringviews/<theme>/Jinja2 templates for the active themepublic/themes/<theme>/main.cssthe entire design system, one fileTell it about your site
Pick what you're building — the questions and prompt below tailor themselves to it.
Try these first
Three real prompts that show you how the pieces fit together. Copy one in, watch what changes.
The fastest way to see the agent work — ask for something you'll see change immediately in the browser.
Update the homepage hero headline, subtitle, and eyebrow badge to describe my business instead of Gravity.
Blog posts are stored separately from the theme, so this works the same no matter which theme is active.
Write and publish a new blog post announcing the launch of this site, then show it to me at /blog.
The best way to learn how Gravity fits together — one prompt wires up a route, a controller, and a template.
Add a new /pricing page: a route, a controller, and a template that extends this theme's base.j2, with three pricing tiers.
Ship it
One command deploys to Google Cloud Run, Vercel, or Cloudflare. Pick a platform below.
make deploy-gcp
make deploy-vercel
make deploy-cloudflare
All three prompt for anything missing (like SECRET_KEY) the first time, save your
answers to .env, and print the live URL when done. Every platform's filesystem is
stateless — if you're using the Visual Editor, set GRAVITY_SITE_BUCKET so page
edits and uploads survive redeploys.
Useful commands
./scripts/install.sh --statusis it running?./scripts/install.sh --logstail the server log./scripts/install.sh --theme=NAMEswap themes and restartmake editorrebuild with admin unlocked, seed sample contentmake theme-listlist available themes