Files
galaxy-game/site
Ilia Denisov ec98639d49
Build · Site / build (push) Successful in 8s
Tests · Integration / integration (pull_request) Successful in 1m38s
Build · Site / build (pull_request) Successful in 10s
Tests · Go / test (pull_request) Failing after 3m0s
Tests · UI / test (pull_request) Successful in 2m35s
fix(site): link to the game with target=_self to avoid VitePress SPA 404
VitePress is a Vue SPA; a same-origin link to /game/ (a separate app, not
a VitePress page) was intercepted by its client router and rendered
VitePress's own 404 until a manual reload. Mark the game links (both
home pages and the nav item) target="_self" so the click is a real
browser navigation that the edge Caddy serves from the game bundle.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-23 19:13:15 +02:00
..

Galaxy project site

The public project site — an overview today, documentation as it grows. Built with VitePress and served as static files at the root (/) of the single-origin deployment; the game UI lives under /game/ (see tools/dev-deploy/Caddyfile.dev).

Layout

  • index.md, ru/index.md — per-locale home pages.
  • .vitepress/config.ts — site config: locales (English + Russian, with the built-in language switcher), LaTeX math (math: true), and the two-column navigation (left sidebar = chapters, right outline = on-this-page).
  • .vitepress/theme/ — the default theme without bundled fonts, plus a minimal monospace type stack in custom.css.

Authoring

  • Add a page as Markdown and register it in the sidebar of each locale in .vitepress/config.ts.
  • Localised content mirrors the English tree under ru/.
  • Math uses LaTeX: inline $E = mc^2$, block $$ … $$.
  • Link to the game with the root-relative /game/ path so the build stays domain-agnostic (no hard-coded host).

Commands

pnpm install
pnpm dev      # local dev server
pnpm build    # static build into .vitepress/dist
pnpm preview  # preview the build

The dev and prod deploys build the site via make -C tools/dev-deploy seed-site and the dev-deploy / prod-build workflows.