LyraCoreProject

Spec: the LyraCore public site

Decisions locked in a wayfinding session on 2026-08-12. This file is the handoff to whoever builds the site.

Destination

A public site at https://lyracoreproject.github.io that a developer or operator lands on, understands what LyraCore is, and follows one guide from the install command to a running server.

Audience

Operators and contributors. Not players.

The site is the project’s front door for people outside the repos. It is not a republishing of LyraCore/docs/ — those documents are written for agents and maintainers, stay in their repo, and are linked, never copied.

Stack

Vite + React + TypeScript, guides authored in MDX, built to static files and deployed to GitHub Pages by a GitHub Actions workflow. See docs/adr/0001-react-for-the-public-site.md for why React and not a Rust static site generator.

No wiki. All content changes go through a pull request, matching the other repos in the org.

Content

Two pages. That is the whole site.

Landing page

What LyraCore is, aimed at a developer or operator. Links to the three repos — LyraCore, lyracore-cli, wire-harness — and to the quickstart guide. No “come play” link yet; see Not yet specified.

Quickstart guide

Every step from

curl -sSfL https://raw.githubusercontent.com/LyraCoreProject/LyraCore/main/install.sh | sh

to a running server. Nothing beyond that. Source material is LyraCore/docs/quickstart.md, which covers prerequisites, the SpacetimeDB installer, and the piped-run caveats.

This guide becomes canonical. A companion pull request in LyraCore shrinks docs/quickstart.md to a pointer at this page. A newcomer’s first contact is a URL, not a file in a repo. The deep material — architecture.md, danger-zones.md, schema.md — stays in LyraCore/docs/ where the agents look.

Licensing firewall

Applies verbatim, as in the other repos: this repo never contains or links game data. No *.dbc, no *.MPQ, no DBFilesClient/, no classic-db dump. Guides may describe formats and ingestion steps, and require the reader to bring their own client data. Screenshots of the game client are fine.

Not yet specified

• Prospective players. A public root URL will catch people looking for the Argus community realm. What the landing page says to them is undecided. Today it says nothing.
• Live realm status. A status widget or online-player count on the landing page is the interactive element that justified React. Not built, not designed.

Out of scope

• Player-facing guides — how to get a client, how to connect, what works.
• A custom domain. The default lyracoreproject.github.io URL is the address.
• News or blog posts.
• Guides for lyracore-cli and wire-harness. The CLI overlaps LyraCore/docs/development-cli.md; write it when someone asks.