Skip to content
Sign inJoin waitlist

Going live — Denzel Astro

Before the Denzel site goes public, replace the demo’s content and point the newsletter box at you; then build it, upload it to any host and check it again.

Replacing the demo’s content means its name, description, e-mail, posts, categories, authors, the posts it features and the 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 and description (they describe the template: write yours) site in src/content/site.json; Home’s title and description in meta of src/content/pages/home.json; the Blog’s in blog.meta and the “on Denzel” descriptions in src/content/pages/blog.json; the share image’s description, shareImage.alt, in src/lib/meta.ts
Your e-mail (hello@example.com is a placeholder) footer.email in src/content/site.json
Social links (they open the networks’ home pages) socials in src/content/site.json; each author’s social in authors.json
The footer’s text, “Join 89,000 subscribers!”, the note under the box and the copyright line footer in src/content/site.json
Logo replaced src/assets/images/logo.svg (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 replaced, each with its alt src/assets/images/ and the content
Your posts, categories and authors (or the demo’s deleted) src/content/collections/posts.json, categories.json, authors.json
The menu’s category links and its “Author” link navigation in src/content/site.json
Home’s picks, the sidebar’s Recent and topics, the footer’s two posts point at your posts home.json; sidebar and footer.posts in site.json (Editing the content)
The newsletter box delivers 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 “Denzel”, the sample posts and authors, the placeholder e-mail, the subscriber count 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 (blog.html, category/business.html) and served at clean addresses (/blog). Netlify and Cloudflare Pages do that by default. On Vercel, the vercel.json next to package.json does it with "cleanUrls": true. It also holds "git": { "deploymentEnabled": false }, which stops Vercel from deploying on every push: remove that entry if you want each push to your repository to publish the site.

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 header, the phone menu and the current page’s link;
    • the search: type a word, use the arrows and Enter, press Escape;
    • Home’s slider moving, Editor’s Pick, Trending and Latest;
    • the Blog, a category, an author and a post, with its Related Posts and More Articles by;
    • the sidebar’s Recent and Explore Topics;
    • the newsletter box.
  2. Sign up from the newsletter box of the live site, and check that the address arrives.
  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 with its date; it goes first on the Blog and in Latest by itself. Feature it on Home or in Recent by its slug (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 post, category and author;
  • one <h1> per page, and a title and description for every page;
  • canonical links, sitemap.xml, robots.txt and share cards (a post shares its cover and is marked as an article);
  • 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. The Blog lists every post on one page, so with hundreds of posts, consider splitting it into pages (Astro’s pagination).