Skip to content
Sign inJoin waitlist

Going live — Catchup Astro

Before the Catchup site goes public, replace the demo’s content and point the form at you; then build it, upload the static files to any host and check it again.

Replacing the demo’s content means its name, details, numbers, awards, team, testimonials, posts, legal pages and photos; pointing the form at you means giving it a destination. Once the site is deployed, click through the live address once more.

Where
Your domain in site.url (until you change it, it is the demo’s address) src/content/site.json. Share links, sitemap.xml and robots.txt are built from it.
Name, title and description (they describe the demo studio and the template: write yours) site in src/content/site.json, and Home’s meta in src/content/pages/home.json; the share image’s description, shareImage.alt, in src/lib/meta.ts
Your studio’s name instead of “Catchup”: the copy, the legal pages, the footer’s copyright line Search src/content/ for “Catchup” (Editing the content)
Contact details (hello@example.com and the phone number are placeholders), your address and hours contact in src/content/site.json; location and hours in src/content/pages/contact.json
Your booking link (both “Book a 15-min call” buttons open https://cal.com/) bookingHref in src/content/site.json, serviceItemPage.pricing.action.href in src/content/pages/services.json
Social links (they open the networks’ home pages), and the team’s handles socials in src/content/site.json; team.members in src/content/pages/about.json
Logo replaced src/design-system/components/brand/Logo.astro (Making it look like your brand)
Browser icons replaced public/icon-light.png, public/icon-dark.png, public/apple-icon.png
Share image replaced and described public/opengraph-image.png, its description in src/lib/meta.ts
Demo photos and client logos replaced, each with its alt src/assets/images/ and the content
Your own numbers: brands, years, growth, rating, projects about in src/content/pages/home.json, philosophy.stats and the client count in about.json
Your own awards, with links to them (the demo’s point at awwwards.com), or the section removed awards in src/content/pages/about.json
Your team team in src/content/pages/about.json
Testimonials from your own clients src/content/collections/testimonials.json
Your projects, services (with your prices), posts src/content/collections/
Your own terms and privacy policy (the demo’s are samples) src/content/collections/legal.json
Page titles and descriptions written for your work The meta of each file in src/content/pages/ (workPage.meta, servicesPage.meta, contactPage.meta, …)
The contact form delivers to you, with your own notification title Forms
Style guide kept or deleted src/pages/style-guide.astro
npm run check and npm run build pass, and npm run preview looks right —

The demo content is there to be replaced. Leaving “Catchup”, the sample e-mail and address, the sample numbers, awards, team and testimonials, the sample legal pages or the template’s description on a live site is the most common mistake.

npm run build writes a complete static site to dist/: HTML files, one stylesheet, a few small scripts, the font files and optimised images. Any host that serves files can run it, with no Node.js needed on the server (unless you chose server-mode forms).

Vercel, Netlify or Cloudflare Pages (free for most sites)

Section titled “Vercel, Netlify or Cloudflare Pages (free for most sites)”
  1. Push the project to GitHub, GitLab or Bitbucket.
  2. Import the repository. Astro is detected: build command npm run build, output folder dist.
  3. Add your form variables (PUBLIC_FORM_ENDPOINT, …) in the host’s environment settings, then deploy.
  4. Add your domain in the host’s Domains settings and follow the DNS instructions.

Pages are built as files (about.html, work/liva-beauty-skincare.html) and served at clean addresses (/about). Netlify and Cloudflare Pages do that by default. On Vercel, add a vercel.json next to package.json:

{ "cleanUrls": true }

Any other host (shared hosting, S3, a VPS)

Section titled “Any other host (shared hosting, S3, a VPS)”
Terminal window
npm run build

Upload the contents of dist/ to the web root. For clean addresses, make the server try <path>.html:

  • Apache (.htaccess):

    RewriteEngine On
    RewriteCond %{REQUEST_FILENAME}.html -f
    RewriteRule ^(.+)$ $1.html [L]
    ErrorDocument 404 /404.html
  • nginx: try_files $uri $uri.html $uri/ =404; and error_page 404 /404.html;

If you set PUBLIC_FORM_MODE=server, add your host’s adapter first (npx astro add vercel, netlify, cloudflare or node). Only the form route runs on the server; every page stays static.

  1. Check the pages. Click through every page on a phone and a laptop:
    • the Home intro, the hero’s slides (point at the titles on a laptop, wait on a phone) and the header that comes back after the hero;
    • the menu and the phone menu;
    • the moving rows on Home, the testimonial carousel on a phone, the numbers counting up;
    • a project page with its stories and its client’s quote, and a service page with the Per Project / Per Month switch;
    • Blog loading more posts as you scroll, a post and its “More Blog”;
    • the Contact form and the legal pages.
  2. Send yourself a message from the live site and reply to it.
  3. Verify the share card. Paste the URL of the home page and of a post into https://www.opengraph.xyz or a chat window, and confirm the image and title.
  4. Tell Google. Add the site to Search Console, verify ownership and submit https://yourdomain.com/sitemap.xml. Bing has the same thing in Webmaster Tools.
  5. Analytics, if you want it. Add your snippet to the <head> in src/layouts/Layout.astro, or use your host’s built-in analytics (Vercel Analytics, Cloudflare Web Analytics, Plausible, Fathom). None of them need a cookie banner.
  6. Keep it current. A new post is one entry in src/content/collections/posts.json (the newest date shows first), a new project one entry in work.json; see Editing the content, and rebuild. Connect a CMS (Using a headless CMS) if someone else will publish.

The template ships with what search engines look for:

  • static HTML, with links in it to every page (every post of the Blog included);
  • one <h1> per page, and a title and description for every page;
  • canonical links, sitemap.xml, robots.txt and share cards (posts as articles);
  • resized, lazy-loaded images that keep their space while they load, each with its alt text.

Keeping the site fast is mostly about images. Astro resizes the photos, but export them at the size they are shown, not the size your camera produced: a 30 MB camera file still slows the build. The placeholders show the size each one was designed for, and the photos of the first screen of every page load first.