Static Marketing Site

Requirement The site build MUST write every page as a static file that needs no server at request time.

Rationale A file needs no application server, no database, and no per-request rendering. The host serves bytes, so the failure surface is the file set itself.

Example

dist/index.html
dist/pricing/index.html
dist/nl/prijzen/index.html

Requirement A page MUST NOT ship a client script unless the site records the interactive need that script serves.

Rationale A reader reads a marketing page rather than operating it, so each script needs a named reason to exist. The named need lives beside the script, such as a theme switch kept across pages.

Example The theme switch is the one script: /assets/theme.js, named in the layout as the reader-chosen scheme.

Requirement The site MUST serve every client script from its own origin.

Rationale A script from another origin runs with the authority of the page while living outside the release. Serving each script locally keeps the release self-contained.

Requirement The site MUST publish a content security policy naming every source its pages load.

Rationale The policy is the enforceable form of the loading rules on this page. A source nobody named fails closed in the browser rather than loading on trust.

Example

Content-Security-Policy: default-src 'self'; script-src 'self'; style-src 'self'

Requirement A page MUST NOT load fonts, scripts, styles, images, or analytics from a third-party origin.

Rationale A third-party load trades reader privacy for convenience and fails when that party fails. Fonts, icons, and screenshots ship with the site instead.

Requirement Every page MUST carry exactly one top-level heading and landmark elements for its regions.

Rationale One top-level heading names the page for a reader and a crawler alike. Landmark elements expose the header, navigation, main content, and footer to assistive tools.

Example

<header>...</header>
<nav aria-label="Site">...</nav>
<main id="main-content"><h1>Pricing</h1>...</main>
<footer>...</footer>

Requirement Every page MUST state a title element and a description its search result shows.

Rationale The title names the tab and the search result, and the description summarizes the page beneath it. Both come from the page frontmatter, so each page states its own.

Requirement Every page MUST carry a canonical link with the absolute address of that page.

Rationale One absolute address tells a crawler which address to index when several serve one page. A relative address leaves the host to guesswork.

Example

<link rel="canonical" href="https://example.test/pricing/" />

Requirement Every page on a site with more than one language MUST link each language alternate with its language tag and a default fallback.

Rationale The alternates tell a crawler which address serves which language, and the default tells it where to send an unmatched reader. A single-language site carries no alternate links.

Example

<link rel="alternate" hreflang="en" href="https://example.test/pricing/" />
<link rel="alternate" hreflang="nl" href="https://example.test/nl/prijzen/" />
<link rel="alternate" hreflang="x-default" href="https://example.test/pricing/" />

Requirement The site build MUST generate a sitemap listing every page with the language alternates of that page.

Rationale The build generates the sitemap from the pages that exist, so it cannot drift from them. Each entry carries the alternates, so a crawler finds every language from one file.

Example

<url>
  <loc>https://example.test/pricing/</loc>
  <xhtml:link rel="alternate" hreflang="nl" href="https://example.test/nl/prijzen/" />
</url>

Requirement The site MUST publish crawler rules pointing to the sitemap address.

Rationale Crawlers read robots.txt first, so the file points to the sitemap from the site root. Access rules for crawler-only paths live in the same file.

Example

User-agent: *
Allow: /
Sitemap: https://example.test/sitemap.xml

Requirement The site build MUST generate a page list naming every page with its address and description.

Rationale The llms.txt file summarizes the site and groups every page with the address and description a model needs to cite it. The build generates it from the pages, so it lists what exists.

Example

# Example
## Pages
- [Pricing](https://example.test/pricing/): What each plan costs.

Requirement The site build MUST generate a full-text file with the text of every default-language page.

Rationale The llms-full.txt file carries the plain text of the default-language pages for a model that reads the whole site at once. Non-default languages stay out, so the file holds one language.

Requirement Every page MUST link a Markdown copy of its own text served beside that page.

Rationale The Markdown copy gives an agent the page without layout, styles, or scripts. The page head links it, so a reader finds the copy from the page itself.

Example

<link rel="alternate" type="text/markdown" href="https://example.test/pricing/index.md" />

Requirement Every page MUST carry JSON-LD structured data for the organization, the site, and the page with breadcrumbs, offers, questions, or article body where each applies.

Rationale One graph per page describes the organization and the site once, then the page with its breadcrumb trail. Price pages add offers, question pages add questions with answers, and articles state their article body.

Example

{"@context": "https://schema.org", "@type": "Organization", "name": "Example"}

Requirement A repeated fact MUST live in one data source every page reads, as a Term record with labels per language for a product word.

Rationale One source means one edit reaches every page, and two pages cannot disagree. Pages read facts by reference rather than repeating them.

Example The footer and the imprint page both read company.legalName from the site data.

Requirement Each language MUST supply only text into one page structure the site holds once.

Rationale One layout renders every language, so a structural change touches one file. A language adds wording, never markup, so translations cannot fork the page.

Requirement A page whose owner has not supplied a fact MUST carry a visible placeholder naming that fact.

Rationale A visible placeholder tells a reviewer what is missing instead of publishing a guess. The placeholder names the fact, so the owner knows what to supply.

Example A page awaiting its final price carries [[FILL: launch price]] where the price stands.

Requirement A release build MUST fail while a visible placeholder remains on any page.

Rationale A published placeholder is a false statement to a reader. The release gate refuses it, while a development build warns and finishes.

Requirement Every price and claim on the site MUST come from the consumer records the site convention names.

Rationale The site repeats commercial facts it does not own, so it reads them where they are owned. A price changed in the record reaches the site on the next build. The named records carry their own owner and status.

Requirement A consumer selecting this extension MUST declare each static site with its name, path, and generator.

Rationale The paths.sites entry tells tools where the site lives and which generator builds it. A site nobody declared is a site no check reads.

Example

{"name": "marketing", "path": "sites/marketing", "generator": "astro"}