--- import { brand } from '../../lib/brand.mjs'; import platform from '../../data/platform.json'; /** * The hero (PLAN.md §13 phase 3). * * The org lead chose an emblem hero over a type-only one: the mark carries recognition * across the site, the Android launcher icon and the Play listing, and showing it large is * what makes those three read as one product (D11, §11). * * It costs what D16 already accepted — the emblem is raster illustration, so a mounted * `theme.css` recolours everything around it and not the mark itself. Replacing the mark * means replacing `logo.png`, and because every size here is derived on request from * whichever `logo.png` is in force (D14), that one file changes the hero, the header, the * tab icon and the installed app icon together. * * The glow behind it is drawn in CSS from the portal tokens, so it DOES follow a mounted * theme. That is deliberate: the part that can track the operator's palette does. * * The
Self-hosted community platform
{brand.siteName} is a community website for a game server — accounts, teams, forums, a wiki, news and a full admin panel — with a one-way bridge that puts the server's live world on the public site. The game itself never listens on the internet.