The source for bearddoddity.github.io — the project site for the tools I build for my own stream, plus guides, a blog, and a community game database.
Static HTML and CSS, served by GitHub Pages. No build step, no framework, no dependencies: what's in this repo is what ships.
| Page | What it is |
|---|---|
| Home | Project index |
| StatusForge | Product page and downloads for the game-detection app |
| Blipy | The dual-PC companion agent |
| Joystick | The Joystick.tv chat bot |
| Game Database | Community-contributed, signature-verified game metadata |
| Guides | Setup walkthroughs — dual-PC Blipy, overlay setup |
| Blog | Posts |
| About, Privacy, Terms, Disclosure | The legal and who-am-I pages |
| Path | What's in it |
|---|---|
index.html, about.html, privacy.html, terms.html, disclosure.html |
Top-level pages |
tokens/ |
The design system — colours, typography, spacing, effects, components, and web components. This is the shared visual language across the site and the apps |
assets/ |
Logos, images, and nav.js (the mobile nav toggle) |
styles.css |
The small top-level stylesheet that pulls the tokens in |
statusforge/, blipy/, joystick/ |
Per-product pages |
guides/, blog/ |
Guides and posts |
gamedatabase/ |
The Game Database page and its data (see below) |
gamedatabase/ is the one part of this site that takes contributions, and it's
worth understanding how before you send one.
gamedatabase/submissions/is the inbox. Add a plain JSON file with the game metadata you have — title, genre, release year, developer, publisher — and open a pull request. GitHub's "Add file" button works fine if you'd rather not clone.gamedatabase/entries/is what the page actually reads. Every file in it carries an Ed25519 signature, and the page verifies that signature in the browser before rendering anything. Push access to the folder isn't enough on its own — an unsigned or wrongly-signed file is silently skipped.- Between the two is a review: submissions get fact-checked, then signed and
moved into
entries/.
That's what stops someone pushing false "fact-checked" data into a page people trust. Both folders have their own README with the exact file shapes.
gamedatabase/games.json is the small seed list the page falls back on.
Pushing to main publishes. GitHub Pages serves this repo as-is, so anything
committed here is live — there's no staging environment and no build to fail.
The StatusForge download page is kept in sync from the StatusForge.io repo by a workflow there, so release links update themselves when a new version ships.
There's nothing to install. Open a file in a browser, or serve the folder:
python3 -m http.server 8000Relative paths between pages and tokens/ assume you're serving from the repo
root, so prefer the server over opening files directly.