Skip to content
Sign inJoin waitlist

Going live — Lookis Astro

Before the Lookis 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, testimonials 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 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 name and town instead of “Daniel Mercer” and “Asheville”: the copy, the projects, the testimonials, the footer’s copyright line Search src/content/ for “Daniel” and “Asheville” (Editing the content)
Your place and time zone for the header’s clock owner in src/content/site.json
Contact details (hello@example.com and the phone number are placeholders) contact in src/content/site.json
Your booking link (the demo’s “Book a session” and both “Schedule a call” buttons open https://cal.com/) bookingHref and footer.action.href in src/content/site.json, hero.primary.href in src/content/pages/home.json
Social links and the Instagram button (they open the networks’ home pages) socials in src/content/site.json; showcase.instagram in src/content/pages/shared.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 replaced, each with its alt src/assets/images/ and the content
Your own numbers: clients, projects, cities, countries facts in src/content/pages/home.json and about.json
Your own awards, with links to them (the demo’s point at a placeholder site), or the block removed awards in src/content/pages/about.json
Testimonials from your own clients testimonials in src/content/pages/shared.json
Your projects and services, with your prices src/content/collections/
The questions of Services answered for your work servicesPage.questions in src/content/pages/services.json
Page titles and descriptions written for your work The meta of each file in src/content/pages/ (portfolioPage.meta, servicesPage.meta, contact.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 “Daniel Mercer”, the sample e-mail, the sample numbers, awards and testimonials, 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, portfolio/downtown-vows.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 and the clock in the header;
    • the name running across Home and the introduction appearing word by word;
    • Portfolio’s tabs, and more projects loading as you scroll;
    • a project page with its gallery and related projects, and a service page with its lists;
    • the testimonial slideshow and its arrows, and the questions of Services;
    • the Contact form.
  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 project 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 project is one entry in src/content/collections/portfolio.json (at the top of the list, to show it first); 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 projects of Portfolio 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, 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.