Guide

From a folder of code to a live website

Scoutline hands you a finished front-end in a zip. Three things stand between that and a site a business can actually use: somewhere to host it, a domain to reach it at, and a contact form that really sends. Here is each one, in the order to do them.

Before you start

What is actually in the zip

Unzip it and you will find a complete static website: one .html file per page, a css/ folder with a single stylesheet, a js/ folder with one hand-written script, and an images/ folder holding whatever photographs you supplied.

Alongside those are three documents that are for you, not for the business: HANDOFF.md (what is finished and what is not), NOTES.md (every placeholder still to be filled in), and PROMPT.md (a briefing to paste into whatever AI you use next, written to stop it throwing the site away and rebuilding it in React). Delete all three before you hand the folder over.

You can open index.html by double-clicking it right now. It will look exactly as it will online — everything works from a local file except the contact form, which is covered in step 3.

Step 1

Put the folder online

A static site needs hosting, and for a site this size the honest answer is that it costs nothing. Vercel and Netlify both take a dragged-and-dropped folder and give you a working URL in about a minute. These steps use Vercel.

Deploying the folder 1. Create a free account at vercel.com.
2. On the dashboard, choose Add New → Project.
3. Pick the deploy a folder option and drag in the unzipped site folder — the one with index.html at the top level, not the zip itself.
4. Leave every build setting alone. There is no build step; the files are already the finished site.
5. Press Deploy. You get a URL ending .vercel.app.

Check it worked: open that URL on your phone, not just your laptop. Click through every page in the menu. If a link 404s, the build was incomplete — see the note in HANDOFF.md.
Loads from YouTube only when you press play. Open on YouTube instead.
Step 2

Get a domain and point it at the site

A .vercel.app address is fine for showing the owner. It is not fine for a real business. A .co.uk costs roughly £8–15 a year from Namecheap, Cloudflare or 123-reg.

Buy it in the business’s name, not yours. This is the single most important line on this page. A domain registered to you is a domain the owner cannot move if they ever stop working with you, and that turns a good relationship into a hostage situation. Register it to them, or transfer it to them the moment they pay. Charge for your time instead.

Connecting the domain 1. Buy the domain. Match the business name as closely as you can.
2. In Vercel, open the project, then Settings → Domains.
3. Type the domain in and press Add. Vercel shows you the DNS records it needs.
4. In the registrar’s DNS panel, add exactly those records — usually one A record for the bare domain and one CNAME for www.
5. Wait. DNS changes normally take minutes but are allowed to take up to 48 hours.

Check it worked: Vercel’s Domains panel shows the domain as Valid, and both example.co.uk and www.example.co.uk load over https with no certificate warning.
Loads from YouTube only when you press play. Open on YouTube instead.
Step 3 — do not skip this one

Make the contact form actually send

The generated form is marked up correctly and deliberately submits nowhere. Scoutline has no way to receive mail on a stranger’s behalf, so rather than pretend, the form is left unconnected and the shared script blocks it and shows a notice saying so.

That notice is a stopgap, not a finished state. An owner whose enquiries silently vanish is the worst thing this product can cause, and it is invisible — nobody complains about a message they do not know was lost. Wire it up before anyone sees the site.

Wiring the form 1. Create a free endpoint at Formspree or Web3Forms. Both are built for exactly this and neither needs a server.
2. Open contact.html and put the endpoint URL in the form’s action, with method="POST".
3. Add data-form-endpoint to the same <form> tag. That is the switch that tells the built-in script the form is real now, so it stops blocking the submit and removes the notice.
4. Remove the <p data-form-note> element, or leave it — once the endpoint attribute is present it stays hidden either way.
5. Point the endpoint at the owner’s inbox, not yours.

Check it worked: send yourself a real message through the live form and confirm it arrives. Do not assume — this is the one step where a silent failure costs the owner money.
Step 4

The things left after it is live

The site being up is not the same as the job being done. In rough order of how much they matter to a local business:

  • Fill in every placeholder. NOTES.md lists them. Anywhere the owner told you nothing, there is visible placeholder copy — it must be filled in or removed before this runs under their name.
  • Real photographs. If none were supplied, the layouts use empty labelled frames. For a trade site this is usually the highest-value thing left.
  • Google Business Profile. For a local business this matters more than the website does. Claim it, and make the name, address and phone match the site exactly — character for character.
  • Search Console. Add the domain and submit the site so Google knows it exists.
  • A privacy notice, if the form collects a name or an email. In the UK that is a real obligation rather than a formality, and it is about an hour of work.
  • Payments, only if they need them. Nothing on the site takes money. If they want deposits or bookings, Stripe Payment Links need no backend at all — one link per product. Build a real checkout only if they genuinely need one.
One last thing

Read the whole site before the owner does

Everything on a generated page comes from the business’s real listing or from what you supplied. Nothing is invented — but “not invented” is not the same as “correct about this business”. Read every page as though you were the owner. It takes ten minutes and it is the difference between a handover and an apology.