Configuration

Configuration#

Everything about your site — its name, its schedule, its colors — is edited in the GUI’s Website tab and saved into your config repo. The app writes the files; you never edit them by hand.

The Website tab has a repo bar at the top, four editors in the middle, and the build/preview/deploy actions at the bottom. Edits autosave as you make them.

Getting set up#

  1. Config repo — the Git URL of the repository that holds your configuration. It’s yours, and it’s the only repo you need; the site template comes with the app.

  2. GitLab account — Sign in with GitLab so the app can clone and push on your behalf.

  3. Save & Sync — pulls the config repo and publishes your on-screen edits back to it. The first run is a plain clone. Sync does the same but without pushing your edits, and Update Website Template refreshes the site template only, leaving your config untouched.

Core#

Site-wide identity, used across the whole site:

  • Stream Name — what the stream is called, e.g. The Academy. It fills the page title and the greeting.

  • Streamer — your screen name. It labels your timezone column on the schedule.

  • Logo — an image shown in the header, left of the stream name. Choose… copies the file into your config, so pick it once from anywhere on disk. Accepts .png, .jpg, .gif, .svg, .webp, .avif.

  • Title Font / Text Font — optional fonts for headings and for body text, chosen the same way. Accepts .woff2, .woff, .ttf, .otf. Leave them empty and the browser’s defaults are used.

Worlds#

A world is a persistent place you stream in — a Minecraft server, a save file, a campaign. Each one has:

  • a key, the short id you’ll pick from in the schedule, and

  • a display name per locale, so Spanish-speaking viewers see the Spanish name.

Add World adds a row. A world named by the schedule but missing here fails the build, so delete a world only after nothing schedules it.

Schedule#

One row per stream, grouped by weekday: Weekday, Start, Earliest end, Latest end, Game, Platform (optional), and World (must be one of your world keys).

Times are in your local time — viewers see them converted to theirs. A bare hour is read inside the 9:00–21:00 window, so typing 7 means 7:00 PM. The end is a window rather than a single time: earliest is when you might wrap up, latest is when you definitely will.

Leave the schedule empty and the schedule page turns itself off — the nav link disappears and /schedule sends viewers home.

Theme#

The site’s color tokens, light and dark, plus a custom-CSS escape hatch. See Theming.

Messages and pages#

Two more things live in your config but are edited elsewhere:

  • Messages — the site’s own wording, in its own i18n tab.

  • Prose pages — free-form pages (an About page, rules, a link list) written in the browser while you Preview. See Building & Deploy.

Where it all goes#

Your config repo ends up holding a streamer-config.json the app maintains, plus the assets, messages, and pages that go with it. It’s plain text under version control, so every change is a commit you can look back at — but the app is the supported way to edit it, and a hand-edit that breaks the format will fail the next build.