deploy-anywherelisted

# deploy-anywhere Take a static project that already exists on someone's machine and getting it served at a public URL, free. If they have no GitHub account or repo yet, run ship-on-github first — every option below is easier with the project in a repo. ## Picking a host Lay out the three and let them choose; all are free at this scale. - GitHub Pages: zero new accounts if ship-on-github is done. Deploys from the repo. Best default for a first site. - Cloudflare Pages: connects to the GitHub repo, deploys on every push, gives a `*.pages.dev` URL. Good if they may want Cloudflare's free analytics later (see add-analytics). - Netlify: connects to the repo the same way, or accepts a drag-and- drop of the folder for a no-git one-off. `*.netlify.app` URL. One host is enough. Do not set up two "to compare" — pick, ship, move on. Switching later is cheap. ## Wiring it 1. Confirm the project is truly static: an `index.html` at the root (or a build output folder). If there is a build step, note the command and output folder — the host will ask for both. 2. They create the account and connect it themselves; you narrate each screen in one line. Never handle their password. 3. GitHub Pages: repo Settings → Pages → deploy from branch → main. Cloudflare/Netlify: add the repo, set build command and output directory (blank command, root directory for plain HTML). 4. First deploy runs. If it fails, read the deploy log together — the error names the fix, usuall