Skip to content
Sign inJoin waitlist

Going live — Semono Astro

Before the Semono site goes public, replace the demo’s content and point the forms 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, figures, photos and videos; pointing the forms at you means giving all three 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 template: write yours) site in src/content/site.json; the share image’s description, shareImage.alt, in src/lib/meta.ts
Your firm’s name instead of “Semono”: the copy, the footer, the testimonials’ quotes, the posts, the careers and the legal texts Search src/content/ for “Semono” (Editing the content)
Contact details (hello@example.com, the phone number and the address are placeholders) contact in src/content/site.json
Business hours contactPage.info.hours in src/content/pages/contact.json
Your booking link (“Book a free consultation” on Home opens https://cal.com/) process.book in src/content/pages/home.json
Social links and the team’s LinkedIn links (they open the networks’ home pages) footer.socials in src/content/site.json; linkedin of each member in src/content/collections/team.json
The line about the firm and the taglines in the footer footer in src/content/site.json
Logo replaced src/design-system/components/brand/Logo.astro (Making it look like your brand)
Browser icons replaced public/icon.svg, public/apple-icon.png
Share image replaced and described public/opengraph-image.png, its description in src/lib/meta.ts
Demo photos, portraits and client logos replaced src/assets/images/
The two videos and their posters replaced (or removed) Editing the content
Your own figures: projects, partners, satisfaction, reach facts in src/content/pages/home.json and about.json
Testimonials from your own clients, with their logos and results src/content/collections/testimonials.json
Your services, team, posts and open positions src/content/collections/
Legal texts of your own (the demo’s Privacy Policy and Terms of Service are samples) src/content/collections/legal.json
Page titles and descriptions written for your work The meta of each file in src/content/pages/ (contactPage.meta in contact.json)
The Contact form’s service choices match your services contactForm.fields.service.options in src/content/pages/contact.json
The three forms deliver to you 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 “Semono”, the sample e-mail, the sample figures, the testimonials, the legal texts, the stock videos or the sample client logos 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, service/business-strategy.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 menu, the phone menu, the header over the Home photo that turns light at “About Semono”, and the page change when you follow a link;
    • the accordion of “Why Choose”, the process tabs and the questions of Contact;
    • Services, Testimonial and Blog loading more as you scroll;
    • a service page and a career page, each with its form;
    • the two videos, which should play when pressed;
    • the Contact form.
  2. Send yourself a message from each of the three forms on the live site and reply to it.
  3. Verify the share card. Paste the URL of the home page and of a service 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 (at the top of the list), a new position one entry in careers.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 (the later rows of Services and Testimonial and the later cards 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;
  • resized, lazy-loaded images that keep their space while they load.

Keeping the site fast is mostly about images and videos. Astro resizes the photos, but export them at the size they are shown, not the size your camera produced: a 12 MB camera file still slows the build. The placeholders show the size each one was designed for. Keep your videos short and small, because they loop: a clip is only fetched when a visitor presses play, so it costs nothing until then. The demo’s clips play from a stock site whose servers set cookies of their own; your own video files from your own domain don’t.