[LeeroyHannigan]

Summary

Adds a documentation site built from docs/ with Docusaurus 3.10, under website/. The Markdown files stay where they are and keep rendering on GitHub; the site adds navigation, search, a landing page and a theme matching extenddb.org.

Today the "Documentation" link on extenddb.org, llms.txt and the repository's index.html send readers to the GitHub directory listing of docs/ (68 files, about 160,000 words, with ledgers and drafts beside Getting Started).

What the site contains

• Getting started: a new entry page (docs/start.md) that runs the development image, makes the first requests and connects an SDK, then an Install group (development image, Docker Compose, Linux, macOS, quick start from source, full walkthrough from source).
• Guides: using, administering, deploying, securing and upgrading a server, a new overview of the four storage backends (docs/storage-backends.md), and the event ticketing demo.
• Reference: differences from DynamoDB, limits, the configuration reference, troubleshooting.
• Contributing: the developer and test guide, the test strategy, local database setup notes, the storage trait and the two backend RFCs.
• Architecture: the architecture and design guides, 13 component designs, 19 decision records, 4 RFCs.

Excluded from the site: the backlog, todo index and technical debt ledgers, templates, the design directory index, the high availability draft, demo assets and build inputs.

How it builds and publishes

.github/workflows/docs-site.yml builds the site on every pull request that touches docs/, website/, Cargo.toml or the workflow. The build fails on a broken link, a missing anchor or a Markdown parse error. A push to main publishes to GitHub Pages. The repository variable DOCS_CUSTOM_DOMAIN selects the hosting: unset builds for extenddb.github.io/extenddb/; set to docs.extenddb.org it builds for the root and writes a CNAME file.

A remark plugin removes each file's License section and NOTICE blockquote at build time; the footer carries the licence and trademark statement once. Code blocks use two Prism themes (website/src/prism/themes.ts) whose token colours are at least 4.5:1 against the block background in both modes. Search is a local index over the user-facing pages.

Content changes in docs/

Made for the site and kept in the files so GitHub readers see them too:

• Links that pointed at files outside docs/ use the GitHub URL; three dead links fixed.
• Product name written ExtendDB in prose and headings on user-facing pages; binary, container, file and configuration names stay lowercase.
• Page titles equal their navigation labels; design document titles read "Component design: X"; ADR titles carry their file number; the ADR index lists 0017 and 0018 with the status their records state (Draft).
• MongoDB setup page: server port 18443 (was 8000 in two places). Quick start: public clone URL, wait table-exists before the first write. Full walkthrough: Cassandra listed with the other backends; first requests put before delete; section 5 states how endpoint, certificate and credentials differ for the development image, Compose and a source build, and names AWS_ENDPOINT_URL_DYNAMODB.
• Docker Compose page: a step to fetch docker-compose.yml, a table of the variables the file reads with their defaults, what docker compose ps -a shows while the server starts.
• Admin, deployment, troubleshooting, security model and usage guide agree on the backend list, TLS being always on, the backup operations that exist and the PartiQL status. The security model gains a Development image section.
• Internal ticket identifiers, draft markers and "last updated" lines removed from user-facing pages; dashes replaced with plain punctuation on those pages.
• Front matter descriptions on every page that appears as a card.

Verification

• Strict build: 71 pages, 0 broken links, 0 missing anchors, 5,298 internal hrefs checked by a crawler, 61 edit links resolve on main.
• Every command on the home page, /start/, /dev-image/ and /local-dev-docker-compose/ run in order in a fresh directory with fresh containers; exit 0 throughout, output matching the page where the page shows output, and the table landing on the local container.
• axe-core on the home page, /start/, /getting-started/, /manuals/usage-guide/, /local-dev-docker-compose/ and /differences-from-dynamodb/ in light and dark mode: 0 violations.
• Each factual claim on the two new pages checked against crates/bin/Cargo.toml, crates/bin/src/main.rs, the three Dockerfiles, docker-compose.yml and the README.
• Search for streams, TTL, IAM policy and PartiQL returns a guide first.

After merge (repository settings, not in this PR)

1. Settings, Pages: set the source to GitHub Actions.
2. DNS: a CNAME for docs.extenddb.org pointing at extenddb.github.io, then set the repository variable DOCS_CUSTOM_DOMAIN=docs.extenddb.org.
3. extenddb.org: point the Documentation link and llms.txt at the new site.

Follow-ups filed separately

Merging the eight installation pages, finishing the high availability design, a configuration reference generated from extenddb.sample.toml, the image upgrade path in the upgrade manual, the dash sweep across the architecture documents, a feature status table owned by the Differences page, and aligning the 48 per-file License sections and NOTICE.md with the README's affiliation statement.

Rebase on #412

Rebased onto main at 1d0d8f4a2. Since the previous base, main gained #412, which documents the experimental Cassandra backend in getting-started.md, the architecture, design and deployment guides, the ADRs and a new docs/cassandra-setup.md. The other commits on main since then (#638, #511, #680) do not touch docs/ or website/.

Four files conflicted. In each one the text from #412 stays and this PR's formatting is applied to it: the ExtendDB spelling, links in place of file paths, and no dashes in the lines this PR changes; the em dash in the design guide's Catalog line is older than both changes and goes in #530.

• docs/getting-started.md: the prerequisites keep the SQLite and Cassandra entries from docs: document the experimental Cassandra storage backend #412. The Cassandra entry reads 4.1+, links to cassandra-setup.md and names the cassandra:4.1 image CI runs. The Cassandra backend section from docs: document the experimental Cassandra storage backend #412 is unchanged apart from punctuation, and its closing pointer to docs/cassandra-setup.md is now a link.
• docs/manuals/01-architecture-guide.md: the overview, crate list, storage backends section, process lifecycle, streams and deployment models are the docs: document the experimental Cassandra storage backend #412 text, which names all four backends and states that on Cassandra a stream record is generally not written atomically with its item.
• docs/manuals/02-design-guide.md: the Catalog and Data Separation section from docs: document the experimental Cassandra storage backend #412 replaces the old Dual-Database Architecture heading.
• docs/manuals/11-deployment-guide.md: the layout from docs: document the experimental Cassandra storage backend #412 is kept (the backend-specific note, Managed Database, and the PostgreSQL connection settings moved under Configuring PostgreSQL). The checklist keeps this PR's lines on TLS being always on, on bind_addr and on the reverse proxy re-encrypting to the server. The firewall line names the storage backend port. The overview keeps this PR's statement that ExtendDB connects to the storage backend it was built with. It says running more than one instance against one catalog is not supported in this release, which is what the Multi-Instance Considerations section of both versions says, and it drops this PR's sentence about PostgreSQL examples because the note from docs: document the experimental Cassandra storage backend #412 says the same.

docs/cassandra-setup.md from #412 is now built as a page at /cassandra-setup/. It is in the Guides sidebar after Storage backends, and the Storage backends table, the walkthrough and the deployment guide link to it. It gets a front matter description, a sentence-case title, NOTICE and LICENSE links as GitHub URLs, and colons, semicolons or parentheses in place of its dashes.

The Component designs sidebar also lists the backup and restore design (docs/design/15-backup-restore.md, from #396), which the site already published at /design/backup-restore/ with no sidebar entry.

The ADR title corrections for 0011 to 0019 are on main now, so they no longer appear in this diff.

At the rebased head, npm ci, npm run typecheck and the strict npm run build pass with no broken links or anchors, and no added prose line has an em or en dash.

CI passed all 29 checks on 34bea38a6. Publish to GitHub Pages is skipped, because it runs only when the event is not a pull request.