Going live — Cerette Astro
Before the Cerette 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, booking links, video, figures, awards, team, testimonials, posts, legal pages and photos; pointing the forms at you means giving them a destination. Once the site is deployed, click through the live address once more.
Before you deploy
Section titled “Before you deploy”| 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 “Cerette”, and your founder instead of Adrian Varell: the copy, the quotes, the legal pages, the footer’s copyright line | Search src/content/ for “Cerette” and “Varell” (Editing the content) |
Contact details (hello@example.com, the phone number and the address are placeholders), in both places |
contact in src/content/site.json (the footer); email, phone, address and hours in src/content/pages/contact.json (the Contact page) |
Your booking links (every “Book a call” and “Schedule Consultation” opens https://cal.com/) |
home.json, about.json, projects.json, services.json and cta.json in src/content/pages/ (Editing the content) |
| Social links (they open the networks’ home pages) | socials in src/content/site.json |
| Your own video in Home’s hero (the demo’s is a file hosted elsewhere, not part of the template), and its poster | hero.video in src/content/pages/home.json (Editing the content) |
| Logo replaced | src/design-system/components/brand/Logo.astro (Making it look like your brand) |
| Browser icon and home screen icon replaced | public/icon.svg, public/apple-icon.png |
| Share image replaced and described | public/opengraph-image.png, its description in src/lib/meta.ts |
Placeholder photos replaced, each with its alt |
src/assets/images/ and the content |
| Your own figures and awards (the demo’s are invented), or the rows removed | about and achievement in src/content/pages/home.json, figures and awards in about.json |
| Your team | src/content/collections/team.json |
| Testimonials from your own clients | src/content/collections/testimonials.json |
| Your projects, services and posts | src/content/collections/ |
| Your own privacy policy and terms (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/ (blogPage.meta in blog.json) |
The forms deliver to you, with your own notification titles |
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 “Cerette”, the sample e-mail, phone and address, the cal.com links, the demo video, the sample figures, awards, team and testimonials, the sample legal pages or the template’s description on a live site is the most common mistake.
Deploy
Section titled “Deploy”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)”- Push the project to GitHub, GitLab or Bitbucket.
- Import the repository. Astro is detected: build command
npm run build, output folderdist. - Add your form variables (
PUBLIC_FORM_ENDPOINT, …) in the host’s environment settings, then deploy. - Add your domain in the host’s Domains settings and follow the DNS instructions.
Pages are built as files (about.html, project/aureline-house.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)”npm run buildUpload the contents of dist/ to the web root. For clean addresses, make the server try <path>.html:
-
Apache (
.htaccess):RewriteEngine OnRewriteCond %{REQUEST_FILENAME}.html -fRewriteRule ^(.+)$ $1.html [L]ErrorDocument 404 /404.html -
nginx:
try_files $uri $uri.html $uri/ =404;anderror_page 404 /404.html;
One demo project has an accented slug (elvaré-studio, the file project/elvaré-studio.html). Hosts that serve files by
their UTF-8 name handle it; if yours doesn’t, give the project a plain slug (elvare-studio).
Server-mode forms
Section titled “Server-mode forms”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.
After it is live
Section titled “After it is live”- Check the pages. Click through every page on a phone and a laptop:
- the Home video and its text appearing, and the header turning the page colour as you scroll;
- the menu and the phone menu;
- the services switcher on a laptop, a tablet and a phone (tabs, then an accordion);
- the team on About (pointing at names on a laptop, cards loading as you scroll on a phone);
- a project page with its sticky photos, and a service page;
- Blog loading more posts as you scroll, a post and its “Similar posts”;
- the forms on Contact and a service page, and the legal pages.
- Send yourself a message from the live site and reply to it.
- 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.
- 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. - Analytics, if you want it. Add your snippet to the
<head>insrc/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. - 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 inprojects.json; see Editing the content, and rebuild. Connect a CMS (Using a headless CMS) if someone else will publish.
Performance and SEO
Section titled “Performance and SEO”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.txtand share cards (posts as articles); - resized, lazy-loaded images that keep their space while they load, each with its
alttext.
Keeping the site fast is mostly about images and the video. 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. The Home video starts loading with the page: keep it short and compressed.