Going live — Compose Digi Astro
Before the Compose site goes public, replace the demo’s content and point the contact form at you; then build it, upload it to any host and check it again.
Replacing the demo’s content means its name, details, services, plans, projects, testimonials, team, job openings, posts, photos, client logos and video; pointing the form at you means giving it 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 template: write yours) | site in src/content/site.json; the share image’s description, shareImage.alt, in src/lib/meta.ts |
Contact details (hello@example.com, the phone number and the address are placeholders) |
contact in src/content/site.json; the jobs’ careers@example.com in src/content/collections/careers.json (Editing the content) |
Your booking link instead of https://cal.com/ (“Book a call”) |
hero.links in src/content/pages/home.json, the Support column of footer.columns in site.json |
| Social links (they open the networks’ home pages) | footer.columns in site.json, hero.socials in the page files, the team’s socials in about.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 (the demo’s is the original template’s preview, with a sample e-mail address) | public/opengraph-image.png, its description in src/lib/meta.ts |
Demo photos replaced, each with its alt |
src/assets/images/ and the content |
| The About video replaced with your own (it plays the original template’s promo) | video.youtubeId in src/content/pages/about.json (Editing the content) |
| The sample client logos replaced with your clients’ (or removed) | facts.logos in about.json, src/assets/images/client-logo-*.svg |
| Your own numbers (“4.9”, “500+ Brands”, “260+ Campaigns”, “98%”) | hero.rating in home.json, facts.items in about.json |
| The founder’s quote and its credit (“Davide Gotlieb, Founder of Compose”) | quote in home.json |
| Your services, with your plans and prices | src/content/collections/services.json |
| Your projects, with testimonials from your own clients and their permission | src/content/collections/projects.json |
| Your team | team.members in about.json |
| Your job openings (or the Careers page removed), with your own “How to Apply” | src/content/collections/careers.json (Pages and sections) |
| Your own posts (or the demo’s deleted) | src/content/collections/posts.json |
| Page titles and descriptions written for your work | The meta of each file in src/content/pages/ (careers.meta in careers.json) |
| A privacy page, if the law where you work asks for one (the template has none) | Pages and sections |
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 the sample e-mail and address, the sample numbers, testimonials and client logos, the template’s video, 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, services/branding-and-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)”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;
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 header’s links and the phone menu;
- the Home hero’s project ticker, the service rows and the custom cursor over the cards;
- a service page: its photo growing into place and the plan card’s Weekly / Monthly switch;
- Services: the process chart filling in, the testimonials changing;
- a project page: its photos moving as you scroll;
- “Load More” on Projects, Blog and Careers, a post with Prev / Next, a job opening;
- the About video and the client logos;
- the contact form.
- 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 project 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(at the top of the list, to show it 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 (the items behind “Load More” included);
- one
<h1>per page, and a title and description for every page; - canonical links,
sitemap.xml,robots.txtand share cards; - resized, lazy-loaded images that keep their space while they load, each with its
alttext.
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 first cards of the Home hero’s ticker load first. The About video loads from YouTube only when Play is pressed.