---
import Base from '../layouts/Base.astro';
import StructuredData from '../components/StructuredData.astro';
import { brand } from '../lib/brand.mjs';

import Hero from '../components/home/Hero.astro';
import DataPath from '../components/home/DataPath.astro';
import WhatItLooksLike from '../components/home/WhatItLooksLike.astro';
import SelfHosted from '../components/home/SelfHosted.astro';
import Capabilities from '../components/home/Capabilities.astro';
import GetStarted from '../components/home/GetStarted.astro';

/**
 * The homepage — PLAN.md §13 phase 3.
 *
 * Ordered as an argument rather than as a brochure: what it is (hero), how the hard part
 * works (the data path), why you would want it on your own hardware, what you actually get,
 * and how to start. The data path comes second on purpose — it is the claim in the tagline,
 * and a visitor who does not believe it has no reason to read the feature list.
 *
 * The page itself holds no copy and no facts. Each section reads versions from
 * `platform.json` and brand text from `brand.mjs`, so nothing on this route can go stale
 * without a check going red first (§12).
 *
 * `bareTitle` because the hero's own <h1> is the tagline: the default suffix would render
 * "Runic Gateway — Put your … — Runic Gateway".
 */
---

<Base title={`${brand.siteName} — ${brand.tagline}`} description={brand.tagline} bareTitle>
  <StructuredData slot="head" />

  <Hero />
  <DataPath />
  <WhatItLooksLike />
  <SelfHosted />
  <Capabilities />
  <GetStarted />
</Base>