Launch checklist

Everything in the theme as shipped is placeholder content for a fictional product. Work through this list before you publish.

1. Name, address and images#

• Site config (src/site.config.ts). Set name, tagline, description, contactEmail and url. url is the address visitors will use:
  ts

  export const siteConfig: SiteConfig = {
    name: 'Your product',
    tagline: 'Your one-line summary.',
    url: 'https://example.com',
    // ...
  };

• Header and footer links. Check nav, cta, footer.columns and social.links in the same file. The social links point at the home pages of three networks: replace them with your profiles or remove them.
• Announcement bar. Rewrite announcement.message, or set announcement.enabled: false.
• Icons (public/). Replace favicon.svg, favicon.ico (32 x 32) and apple-touch-icon.png (180 x 180) together.
• Logo. Replace the SVG in src/components/chrome/Mark.astro, or set logoImage in src/site.config.ts to a file in public/ (for example logoImage: '/logo.svg').
• Social image (public/og-default.png). Replace it with your own 1200 x 630 image. For another size, update seo.imageWidth and seo.imageHeight; update seo.imageAlt too.

2. Forms and links#

• Contact form. As shipped it is a preview that sends nothing. Give it the address of your form service in .env (PUBLIC_CONTACT_FORM_ACTION) or in form.action in src/data/contact.ts, then send yourself a test message. To show the contact cards only, delete the form block in src/data/contact.ts.
• Footer newsletter field. As shipped it is a preview with a “Not connected yet” line under it. Give it an address in .env (PUBLIC_NEWSLETTER_FORM_ACTION) or in footer.newsletter.action.href in src/site.config.ts. To remove the field, empty both footer.newsletter.text and footer.newsletter.action.label.
• Contact addresses (src/data/contact.ts). Replace the example.com addresses in routes with inboxes you read, and rewrite or delete the response line.
• Sign-in, sign-up and plan buttons. cta.header and cta.primary in src/site.config.ts and the cta of each plan in src/data/pricing.ts point at example.com. Replace them with your own addresses.

See Service integrations for the details of each.

3. Content#

• Home page (src/data/home.ts, src/data/faq.ts, src/data/closing.ts). Replace the text of every section you keep and remove the lines of the others from src/pages/index.astro.
• Logos and testimonials (src/data/proof.ts). The companies, people and quotes are invented. Replace them with your own, with permission, or remove <Logos /> and <Testimonials /> from src/pages/index.astro. Delete note once the content is real.
• Pricing (src/data/pricing.ts). Plans, prices, the comparison table and the questions.
• About page (src/data/about.ts). The story, facts and values are invented. The team section is on as shipped, with four invented people: replace them in team.members, or set team.enabled: false.
• Blog (src/content/blog/). Delete the three sample posts and write your own. A post can have a cover picture (coverImage, with coverImageAlt) and an author picture (author.avatar); without them a post has no cover and the author gets initials.
• Documentation (src/content/docs/). These articles describe the theme. Replace them with documentation for your product, and rewrite src/data/docs.ts, which holds the text of the documentation index. Then update the links to deleted articles that you keep by hand: footer.columns in src/site.config.ts links to two of them.
• Changelog (src/content/changelog/). As shipped, these entries record the theme’s own release history. Replace them with release notes for your product, or delete them.

4. Legal pages and cookies#

• Privacy and terms (src/content/legal/). The shipped text only shows the layout. It is not legal advice. Replace both with your own, and say what your forms and any analytics collect.
• Cookie banner (src/data/consent.ts). The banner collects a choice and does nothing else until you connect a script to it. Keep it and rewrite its text if your site needs consent, and delete its note. If nothing on your site needs consent, set enabled: false: the banner and the footer button are left out. Which applies to you is a legal question this page cannot answer.

5. Search engines and sharing#

• Sitemap and robots. After publishing, open /sitemap.xml and check that your pages are listed with your own address, then /robots.txt and check the sitemap line.
• Ownership tags. A search engine’s verification tag goes in the head slot of the layout, on the home page:
  astro

  <meta slot="head" name="google-site-verification" content="your_verification_string" />

• Link previews. Share a link to the home page and to one blog post in a private message, or use the preview tool a network provides, and check the title, text and image.

6. Last checks#

npm run check
npm run build
npm run preview

npm run check reports type errors, npm run build writes the site to dist/, and npm run preview serves that folder locally. Click through every page, with the keyboard as well as the pointer.

The pause buttons on the hero background, the timeline and the logo strip need nothing from you.