feat: T5DE's website: landing page, download, changelog and FAQ

Co-Authored-By: Claude Opus 5.5 <[email protected]>

CLAUDE.md

@@ -0,0 +1,26 @@
+# t5de-site
+
+T5DE's website, t5de.dev (see README.md). Related repositories, usually checked out beside this one: `t5de` (the
+patches and the setup this site offers), `t5de-hub` (hub.t5de.dev; this site copies its look and components).
+
+## Rules
+
+- Never use IMVU's logos, images or name as branding; always say T5DE is unofficial. Never offer IMVU's client for
+  download: T5DE is bring-your-own-client.
+- Commits: author "dhkatz <dev@t5de.dev>"; never the user's real name or email.
+- Changes reach main only through pull requests, squash-merged: the PR's title becomes the commit on main, so it must
+  be a conventional commit (`feat: …`, `fix(download): …`, `docs: …`; `!` before the colon for a breaking change),
+  checked by `.gitea/workflows/pull-request.yml`. Commits on the branch can be anything. Push a branch and open the
+  pull request on git.t5de.dev (web UI or API); the user merges.
+- Releases: release-bot keeps a `chore(release): vX.Y.Z` pull request open (`release.yml`, git-cliff from those
+  titles); merging it tags vX.Y.Z, which builds the image and deploys prod. Never tag by hand (v* tags are
+  release-bot's).
+
+## Notes
+
+- The look: the hub's (modern, neutral, light/dark following the system, color only for status). Copy is short: the
+  user dislikes wordy text. Headings and card titles in Title Case; slogans, buttons and descriptions in sentence
+  case.
+- Releases are read from git.t5de.dev's API (`lib/releases.ts`); the setup's sha256 and the IMVU Classic version are
+  parsed from the release notes t5de's CI writes (`.gitea/scripts/release.py` there), so keep them in step.
+- On this VM, Bun and Node are portable installs in `%LOCALAPPDATA%\Programs\bun` and `...\nodejs` (not on PATH).