## The short version

An AI-generated website can be published directly from its local project. Give your coding agent the Ample setup snippet, let Ample identify whether the site is static or server-rendered, and deploy the result. You keep the source in your existing repo and receive a public URL when the release passes its health checks.

## WHO THIS IS FOR

This guide is for designers, founders, and developers who used an AI coding tool to create a website and now need to share it publicly.

## How to do it

1. 1

### Check the local production build

Ask your agent to run the project's existing build command. A site that only works in a development server may still need a production build fix.

2. 2

### Copy the Ample setup snippet

The homepage snippet installs Ample and authenticates the agent with a one-use onboarding key. Paste it into the agent while the website project is open.

3. 3

### Plan the deployment

Ample inspects the repo and distinguishes a static output from a Node or other server runtime. Writing the plan records that structure for later releases.

```
ample plan --write
```

4. 4

### Publish the site

Apply the plan and wait for the final result. Public web and static services receive a generated URL by default.

```
ample up
```

5. 5

### Share or add your own domain

Use the generated URL immediately. Add a custom domain later if you want the site to use your brand's hostname.

## What this supports

### Good fit

- Static HTML and common static-site generators
- React and Vite frontends
- Server-rendered JavaScript applications
- Repeated releases from the same local repo

### Know the limits

- A hosted editor project must be exported to a local repo before Ample can inspect it
- Client-side secrets must never be embedded in the website bundle
- A site with a backend may require more than one planned service

## Common failure modes

### The deployed site shows a blank page

Check the browser console and confirm the production build uses correct asset paths.

### API requests still point to localhost

Link the frontend to its backend or pass the correct public API URL during the build.

### A route works locally but returns 404

Confirm the project is detected as a single-page app and that its production fallback is configured.