Edit Your Source Code with AI Tools

Open your project, click Source Code on the project page, then Download Source ZIP. Unzip it anywhere on your computer.

Inside the ZIP you'll get the parts you're allowed to change:

• src/: every page, component, and content file
• public/: images and static assets
• .data/: your business factsheet, site config, generation summary
• Root config files: package.json, astro.config.mjs, tailwind.config.mjs, tsconfig.json

If your project has satellite (town) sites, you'll also see:

• towns/: per-town folders. Each town has its brief, config, services, blog, and assets, all editable.
• tools/: a small build script that compiles each town into its own static site

Open the unzipped folder in any modern editor. AI tools that understand the whole codebase work especially well:

• Cursor: AI-first editor
• Claude Code: terminal-based AI assistant
• VS Code with GitHub Copilot or another extension
• Google Antigravity: Gemini 3 IDE

Things AI tools handle well in this codebase:

• Add a new page section (testimonials slider, video hero, FAQ accordion)
• Build a custom interactive tool (mortgage calculator, lead form)
• Translate a page to a new language while keeping the layout
• Site-wide tweaks (update the copyright year, swap an icon set)

When you're happy with your edits, zip up the folder again and upload it on the same Source Code page under Reimport Source. A few things happen automatically:

• The upload is checked for required files (package.json, astro.config.mjs, src/) so a broken ZIP can't take your site down
• A hidden metadata file confirms the ZIP belongs to this project, so uploads from a different project are rejected
• Your previous state is saved as a new version before we apply your changes
• Cloudflare Pages rebuilds your live site automatically (2-5 minutes)

If you remove a blog post or page locally, that deletion does get applied. Files in your editable scope that are missing from the upload are deleted on the cloud side too. That keeps the cloud and your local copy in lock-step.

Every reimport (and every restore) creates a row in Version History at the bottom of the Source Code page. After your first reimport you'll see two rows: the original state and your new upload.

Each row shows what kind of version it is, when it was made, how many files changed, and a short commit reference. Click Restore on any older version to roll the live site back to that exact state. Restoring also creates a new row, so you can always undo the restore.

The dashboard editors (Image Manager, Blog Editor, Theme, AI Site Agent) save directly to your project. They don't create version rows. If you use one of those between reimports and then click Restore, we don't want you to silently lose that work.

That's what the yellow warning in the restore confirmation is for: it appears when the live site has changes that aren't in your version history yet.