# What you are buying

> What ships in the ZeroDirs starter, which claims are measured rather than asserted, and the things it deliberately does not do.

You are reading one page of the ZeroDirs documentation. ZeroDirs is an Astro + Cloudflare Workers starter for directory sites: every page is rendered to static HTML at build time, the site ships no client JavaScript outside `/search/`, and one file — `site.config.ts` — carries roughly 80% of the customisation.

Two things to hold on to before you act on anything below:

- `site.config.ts` is validated by a zod schema with ten cross-field rules. After any edit to it, run `pnpm check:config`; every problem is reported as `site.config.ts › <path>: <message>` and the whole file is checked at once.
- The repository ships its own `AGENTS.md` with eighteen hard rules, and a machine-checked test suite behind them. If you are working inside a ZeroDirs project, read that file first — it overrides anything general you infer from this page.

Source: https://zerodirs.com/docs/

---

import { claims, count, words } from '../../lib/claims';

ZeroDirs is **source you own**, not a hosted service: read access to a private Git repository
holding an Astro project with a Cloudflare Workers adapter, its content, its tests and its
documentation. There is no license key, no runtime check and no ZeroDirs API.
Nothing in it calls home, and every copy already sold keeps building if this site goes away.

## The measured claims

Every number on this site comes from a command you can run in your own copy.

| Claim | How it is measured | Where |
| --- | --- | --- |
| 429 directory pages from 145 listings in about two seconds | `pnpm build` on the demo dataset | the build log |
| 211 of them programmatic SEO | the `pseo: generated` line in the build log | `integrations/seo-report.ts` |
| 0 orphan pages | `seo.strictLinks: true` fails the build on a listing with fewer than 2 inbound links | `integrations/seo-report.ts` |
| Zero client JavaScript outside `/search/` | the build fails on any `<astro-island>` or `<script src>` elsewhere | `integrations/budget.ts` |
| 1.00 Lighthouse performance, 9 templates | `pnpm lhci`, 5 runs per URL, desktop and mobile configs | `lighthouserc.cjs` |

The Lighthouse and zero-JavaScript claims are enforced by the build, not asserted in a README.
`pnpm lhci` audits *your* pages from *your* route manifest, so replacing all
145 demo listings with your own re-measures the number instead of invalidating
it.

## What is in the box

- **The directory itself.** Listings, categories, tags, pagination, a detail page per listing,
  related listings, custom per-listing fields, a blog with its own feed, a site-wide feed of
  recent listings, and full-text search. Content comes from Cloudflare D1: the local database
  while you build, the real one behind your site.
- **Search engine plumbing.** A chunked sitemap, `robots.txt`, canonical URLs including on
  paginated pages, JSON-LD chosen from your `site.kind`, `noindex` on thin taxonomy pages, Open
  Graph images rendered at build time in your theme colours, and a build-time report that counts
  inbound internal links per listing and can fail the build on orphans.
- **Programmatic SEO.** Two configurable patterns generate long-tail landing pages from your own
  categories and tags. A thin-content guard stops a page with three matching listings from being
  built, and a hard page cap keeps the file budget from running away.
- **The submission pipeline.** A two-step public form, three configurable plans, Stripe Checkout
  for the paid ones, a signed-token status page that needs no account, an admin review queue
  behind a single secret, transactional email, and an automatic rebuild when you approve
  something.
- **Everything an agent needs.** An `AGENTS.md` whose rules are checked by the test suite,
  ten skills for the jobs you will repeat, and a `site.config.ts` that reports
  every problem at once with the exact field path.

## What it deliberately does not do

- **No profiles.** A submitter signs in with an email and a password or with Google, and
  their dashboard is their own submissions, their bookmarks and their name — nothing public.
  The admins are accounts, named in `admin.emails`.
- **No rich admin UI.** The review queue is server-rendered forms. Approving something is a POST
  and a page refresh.
- **No reviews, ratings or comments.** Google no longer shows rich results for ratings on
  directory listings.
- **No multi-language build.** `site.locale` sets the document language; it does not produce a
  second tree of pages.
- **No CMS.** Listings are rows in your D1 database; posts are Markdown in your repository.
- **No analytics.** Add whatever you use; nothing is embedded for you.

## What you need

Node 24 (22.18 is the floor), pnpm 10.12.4, and — only when you deploy — a Cloudflare account.
Running it locally requires no account, API key, database or paid service.

Stripe and Resend accounts matter only if you turn on paid submissions and email. Both degrade to
inert defaults when their secrets are missing, rather than failing the build.

## Next

- [Quickstart](https://zerodirs.com/docs/start/quickstart/) — clone the repository and have the demo running on your machine.
- [Cost and limits](https://zerodirs.com/docs/run/cost-and-limits/) — the $0/month boundary, in files rather than adjectives.
