Roadmap · Nezařazeno
Everything we are building, in the open
No dates, no promises we cannot keep. Just what we are thinking about, what we decided to do, what somebody is working on today, and what is already out.
Last thing out A project can be renamed, cards and all 3 weeks ago
Exploring
0Ideas we keep turning over. None of it is a promise.
Nothing here
Planned
6Decided. Waiting for its turn.
Reactions mirror the same way messages do
Voting and following work the same everywhere and stay one number — on the site, on Discord and in the apps.
Anything personal arrives in your language
Messages aimed at you always arrive in the language you chose. Shared rooms stay in one language.
Onboarding decides what you see on Discord
You pick the products and games you care about, and only those show up. Changeable at any time.
New logo across the whole ecosystem
One logo everywhere — site, launcher, panel, docs, Discord and app icons.
Shared elements on every surface
STYGION ID sign-in, feedback, donate and the language switch look and work the same everywhere.
Docs standardised and rewritten
Every document gets one structure and one tone, so they can be read rather than deciphered.
Building
0Somebody has their hands on it right now.
Nothing here
Done
11Built and out. Newest at the top.
Tooling cleaned up and upgraded
The tools that went unused, or did a job worse than grep does, are gone; a small core stayed and what raises the quality of the result was added. Keeping the set small has been continuous work since, not a tidy-up somebody does once.
Our own STYGION agent skills
Eight skills with one source: the roadmap and documentation, the standards, the site's own grammar, Discord, Keystone, the write-ups, announcements and pushing back on a plan. They live in one directory the backend serves from GitHub, so committing one publishes it — and nobody has to remember a procedure somebody already wrote down.
Standards say where a thing belongs, not how it looks
The rulebook turns into a map. Building feedback, tickets, prices or announcements? It points straight at the system that already handles them, so nothing gets built twice. What must never break stays binding; how things look moves to the brand guide, where a decision comes with its reason.
Web & backend security audit
A deep review of our whole security posture: backend and site code, server configuration and the live infrastructure. Seventy-seven specialised checks whose findings are independently verified afterwards. The outcome is a ranked list of issues with a remediation plan.
One standard behind everything we make
Sign-in, feedback, language, look, speed and documentation work the same across every product, because they are written down in one place. A new surface is finished only once it meets all of it.
Building the STYGION Discord
The server runs from a versioned spec — channels, roles, permissions, button onboarding, settings in your own language, and tickets wired into our system.
Security hygiene in CI and rules
Automated dependency checks in CI for web and backend; agent rule for auth/session changes and host hardening for private services.
Docs aligned to code + truth
Sweep docs + design docs and fill in everything that is actually built, matching the real code state. No aspirational claims — what does not exist is WIP.
Migrate all docs into the roadmap + docs
Done: all documentation lives in the DB (docs.stygion.eu) — user and team sections; standalone markdown files migrated and retired.
Naming cleanup: generic updater surface (not "launcher")
Renamed the update surface /launcher → /updates across backend+web+launcher (serves every app via ?app=). LauncherLatest type → ProductLatest.
Real copy pass across launch surfaces
Honest, human copy on the surfaces that actually ship: Launcher, Panel, Hub and STYGION ID. Hub reviewed (clean), Panel rewritten, ID tidied + dead links fixed. Done.