fairyfox.io is the project hub and documentation library for the software work of Fairy Fox (@junebug12851 on GitHub). It exists to be a single, current front door to that work — somewhere that says what is being built and links straight to it, instead of a scatter of repositories with no index. The site is written as documentation: a neutral, plain account of the projects and the conventions behind them.
An index of the projects
Every project in one place, generated from a single registry so the list never drifts out of date.
A documentation library
How the projects fit together, how this site is built, and the shared engineering standards the repositories follow.
A running log of changes
Update posts and round-ups of what changed across the projects, with an Atom feed.
The projects
Three projects sit around the hub, each developed in the open with its own documentation and releases:
- Pokered Save Editor 2 — a desktop save-file editor for Pokémon Red & Blue, built in Qt 6 (C++/QML). It reads and writes saves byte-for-byte and is the project the shared engineering standards originally came from. It is currently in alpha.
- Pokered Save Editor — the predecessor: the original editor, built with Electron and Angular. It is complete and stable, and remains the recommended working tool until the Qt 6 rewrite reaches parity.
- Random AI Prompt — a JavaScript prompt generator for Stable Diffusion, with a web UI and one-click image-to-animation export.
The full list, with links to each project's documentation, downloads, and source, is on the projects page.
How it's built
The site is a static Jekyll site with no
external theme: the layouts, includes, and stylesheet are hand-owned, for full
control and no theme churn. It is built and deployed by GitHub Actions on every
push — there is no manual publishing step — and hosted on GitHub Pages as a user
site, served at the fairyfox.io custom domain. Because the domain is
set on the user site, each project's own GitHub Pages site is served under it too
(for example, fairyfox.io/pokered-save-editor-2/), so the navigation
links straight into a project's documentation. The fuller account is under
how fairyfox.io is built and
deployment.
How it stays current
Two things keep the site from drifting. First, the parts that can be generated are generated: the projects list, the navigation menus, and the updates feed all render from single sources, so adding a project or a post is one small edit rather than several. Second, behind the site is a structured, living set of notes — the same notes system the projects use — so the repository documents itself and anyone opening it can get oriented without outside context. The whole of that knowledge base is surfaced, in a readable form, under this site in the documentation library.
How the projects connect
This repository is the hub for the projects, and the relationship is deliberately loose: communication happens through git only, one direction at a time, and only on request. The hub keeps read-only copies of the projects so their changes can be summarised here, and each project pulls the hub's shared standards when it wants to adopt them. There are no submodules and no live coupling, which keeps every repository independent. The full model is documented under cross-project sync.
A note on voice
The site is written about the work rather than in the first person, and it does not set out to glorify anything — it documents and indexes. Fairy Fox is named for attribution; the work itself is meant to be the subject. The source for this site is public: it is the repository that hosts it.