Roadmap · STYGION Web
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
1Ideas we keep turning over. None of it is a promise.
Planned
21Decided. Waiting for its turn.
What a modpack costs to play
The other half of the same question, and a page of its own because it is not the same question. What a pack costs your own machine: the median frame, the worst one percent beside it — an average hides exactly the stutter that ruins an evening — and which of your parts ran out first, so "should I buy a card or a processor" stops being answered by vibes. It waits on the benchmark the launcher runs; until that exists there is nothing measured, so the page is not opened rather than filled with something.
What a modpack actually costs to run
Nobody can tell you how many players a modpack holds on a given machine, so everybody guesses and half of them buy the wrong box. Servers that choose to send a measurement build the answer together: how many players a pack held, on what hardware, and what gave out first. You say what you have — pick the pack, drop in a mod list, or add the few mods you care about — and say roughly what the machine is, and the page shows the nearest runs it really has, with how near they are and how many there were. Where there is not enough to answer, it says so instead of inventing a number. And the part nobody publishes for any mod: what a single mod costs. Every run already knows whose code the time went into and how many of each mod's things were standing on the server, so the two together give a cost per thing — the number you want when you are deciding what to cut. It will say plainly what it is measuring: where time was spent rather than what caused it, and only the time that pushed the server past playable. The same page will carry what a pack costs to play, not only to run.
Addresses read the same in both languages
The rest of the site follows one rule: English addresses with no prefix, Czech behind /cs/. The documentation does not — its pages carry Czech addresses even in English, so the same page reads as two different things depending on where you arrived from, and a link shared with somebody who does not speak Czech looks like a mistake. Every page gets an English address, the old ones keep working so nothing anybody has bookmarked or linked breaks, and search engines are told which is which.
A documentation section has a page of its own
A section's name in the documentation — "Panel", "Launcher" — cannot be clicked today. It is a heading above a list rather than a link, so there is no single place that says "this is the whole documentation for the panel": you either walk the tree one page at a time, or you search. A section should have a page of its own at `/docs/<section>`: what that part of the documentation is for, every page in it with its summary in the order they are meant to be read, and where to start when it is somebody's first time. It is also the thing worth sending to somebody, and the thing a search engine should read — today the best link to the panel's documentation is a link to one arbitrary page of it. Same cloth: an index at `/docs` listing every section, and each page saying which section it belongs to.
A workspace worth looking at
The tool the team spends its day in should look as good as what we put out — rhythm, hierarchy and calm, not a table of rows.
Things can be started from the workspace
A new article, a documentation page, a card, a thread — the button is always in the same corner and the editor opens over the page.
Did this page help?
A thumb up or down under every documentation page. What did not help turns up in our own queue of work.
How many people come to us
A view of traffic for the team. It arrives together with the cookie bar, because nothing is measured without consent.
Translate this for me
A button on a message, an idea or a page that shows it in your language. Only you see the translation, and the original stays beside it.
The second language starts filled in
Whoever writes an article or a help page does not start the second language from an empty screen. The draft is then rewritten properly — nothing goes out unread.
One person, one page
Linked accounts, devices, points, conversations, roles and notes in one place instead of scattered over five screens.
The account — somebody’s own place on the site
Linked accounts, devices, your own conversations, points, notifications, settings that hold everywhere, and export and deletion without writing to support.
Discord is managed from the surface, not by a script
Channels, roles and permissions as an editable surface. A change is shown as a difference against what is on the server right now before it is applied.
One blog post, every channel
Publish the daily post once and it appears on the site, on Discord and on every one of our social channels. No copying it around by hand.
Admin UI: Discord management (MCP parity)
Admin workspace gets the same Discord control surface as MCP: read/edit channels, roles, permissions, guild settings, messages, moderation, announcements… One backend API, two surfaces — agent (MCP) and human (admin UI). Kept out of the user-facing product area.
Notifications: person vs whole section
Assigned person → notify only them. Section → everyone in that section. Later also push to the mobile admin app.
Community section (social / community ops)
Work section for the community team — overview and tools for social ops in one place.
User admin and role assignment
User list and role assignment. Discord is the source of community roles; STYGION ID only uses the team role to unlock admin sections (as today).
Global ban / unban across services
One ban/unban across STYGION ID and every server/service we run — not a single app only.
STYGION ID multi-surface (web + launcher + …)
Principle (2026-07-15): most ID features on the web (workspace + login/connect outside it). Launcher = thin client. Devices, friends, profile, notifications…
Roadmap redesign
Clearer columns, sharper statuses and more readable cards.
Building
2Somebody has their hands on it right now.
The Keystone page, built again from nothing
Keystone's page gets rebuilt rather than edited — the same product, said properly: what one file replaces, what it does the first evening you install it, and the load test nobody else offers. The mod wears its own mark throughout, not a stand-in drawn for it.
Cross-linking roadmap, docs & pages
The roadmap and docs as one connected whole — a task shows its related docs and vice versa. The linking foundation is done; the on-page display remains.
Done
59Built and out. Newest at the top.
A processor list that stops printing rubbish
Nearly a quarter of the models in the picker carry no cores and no clock, some names are numbers lifted out of the wrong column and are not processors at all, and because the list is sorted by name the rubbish is the first thing you see when you start typing. Somebody looking for their own chip meets six things that do not exist before meeting one that does. The list gets rebuilt from its sources rather than patched row by row, and the script that builds it lives with us so the next refresh is a command instead of an afternoon. What has no specification is dropped rather than shown empty, a model is listed once, and what you type is matched against what people actually own.
The runs are on the page before you pick anything
Today the page asks three questions and shows nothing until it has a run from a pack close enough to yours — which for almost everybody means an empty page and a sentence explaining why. That was written against false precision and it bought it with a page nobody can use. The measurements go first instead. Every run is listed the moment the page opens; the machine and the pack move up top as a filter that only reorders and annotates, never unlocks. Each row says for itself how near it is — how much of your pack it shares, and whether the processor was measured or borrowed from a neighbour. The threshold stops deciding whether you see a row and starts deciding how confidently it is worded. Any row opens into the whole run.
Find out what a modpack costs before you buy the machine
Search for your modpack by name, say what your machine is, and read what packs like yours actually did on machines like yours: how many players they held, what gave out first — the processor, memory, the collector or loading chunks — and what each mod in them cost. Nobody publishes that last number, for any mod. No pack name is ever typed by the server itself: a server is identified by the mods it actually loaded, which is both easier and more honest, because two servers with the same mods are comparable whatever they call themselves. Every number carries the count of runs behind it, and where there are not enough, the page says how far off its nearest match is instead of printing a number anyway.
Sending it out is a visible step
A release is finished in one place: the version, the channel and everywhere it should go. Before it is sent, exactly what would go is shown file by file — an upload cannot be taken back. What failed is visible and can be sent again.
Edit tasks in UI + MCP
Everything that can be done to a task works from the workspace and from an agent — it is one capability described once, not two interfaces that drift apart.
Assign: person or section
A task goes to one person, or to a section — and what goes to a section, somebody takes. Until then it is visible as waiting on everybody.
A taskboard in the team workspace
A taskboard for the team behind the same gate as the rest of the workspace. Anybody on the team creates a task, gives it a title and a description, and hands it to a person or to a whole section. It is not the public roadmap and never mixes with it.
Language parity — what is missing in Czech
A view across everything written: what exists in English with no Czech version, and what the Czech version is older than.
The team workspace, rebuilt from nothing
Built and live at admin.stygion.eu: its home is one queue of what is waiting for somebody, not a menu. The chronicle of changes, people, releases, numbers, money, language parity and the taskboard. What each person opens follows from the role they actually hold.
Web redesign — brand identity across all pages
Delivered by the site rewrite, live since 22 August 2026: one visual language across the site, the roadmap, the documentation, the workspace and the product pages, motion and page transitions included.
Workspace, account and documentation are three separate applications
Each has its own frame, its own addresses and its own navigation. Somebody visiting their account does not get a tool built for a shift, and the other way round.
Logo → back to the homepage
Clicking the logo top-right returns to the homepage.
Developers section in your account
Make, edit and take down your Play buttons in your own account. The button on your site is a picture served from us, so a change here reaches every page carrying it — you paste the code once. Anything else you build on top of STYGION and put on your own site goes in the same section.
Its own look, not a roadmap clone
The same clarity, but a layout and palette that fit feedback rather than plans.
States: new, in progress, resolved
Every item shows where it stands — nothing disappears without an answer.
Feedback map — a public board
Feedback from anywhere in one public place, in the same spirit as the roadmap.
Launcher devices on the web
On id.stygion.eu account: list linked launchers (device label, last seen) and revoke — no launcher required.
Data export and account delete in UI
User path for GDPR export and delete — wired to the backend.
A STYGION wallpaper section
Downloadable wallpapers for desktop and phone, in the resolutions people actually use.
Full website rewrite
The site gets rebuilt from the ground up so every page holds one line and one standard.
You can see how long a taken row has left
The time left stands beside the name, and one press adds another hour. Somebody else’s row shows it too, so you know whether waiting is worth it.
A row in the queue offers what can be done with it
Every kind of row knows what it is waiting for — a conversation offers “resolved”, a version its channel. The queue has no one-size button.
The studio’s numbers in one place
How many people have an account, what they asked for, what we released and how many installations checked in — counted from what already happens here, without following anybody.
Catalog: what each product page lists
A product page’s features are put there from the roadmap — one place for the decision “this belongs on the page”, so the page cannot fall behind what was actually built.
A product page lists its features from the roadmap
What a product does is not written twice. The page lists cards from the roadmap, and the line between what it does and what is coming is a real release rather than a status on the board.
I have got this
When somebody on the team picks your question up, the others can see it — so two people do not write you the same answer.
What most people want and has waited longest
A view that puts how many people asked for something together with how long it has not moved. It shows where disappointment collects.
An idea shows what became of it
An idea still says, a year later, how many people wanted it and which version carried it out. Whoever voted finds out how it ended.
What is waiting — one queue for all of it
Everything waiting for a person — an unanswered question, an untriaged idea, a version ready to go out — in one list by age, pre-filtered to what somebody looks after.
The chronicle — what happened in the studio
One stream of every change: who did it, what exactly changed and how it went. Where it can be, a change is undone in one press.
The keyboard runs the whole surface
Jumping to a place, searching, moving down rows and opening a detail all work from the keyboard. Somebody who spends a day here never reaches for the mouse.
Documentation can be narrowed down
Sections with counts, both halves, and a search across title, address and summary. The filter lives in the address, so it can be sent to somebody.
Sort by what people want most
Wherever something carries a number, the list can be reordered by it. What has waited longest stays the default.
Updates get their own place beside the blog
What we released is no longer a page off to one side but one of the applications you switch between in a click. Filters by product and channel have their own address, and a version opens the whole list of changes.
Cookies and accessibility as their own pages
Alongside terms and privacy: what the site stores in your browser, and an accessibility statement that names what we have not verified.
A page for STYGION ID
What STYGION ID is, how signing in works, what the account carries and what we know about you. Its own mark from the shared family.
Blog and release list
Our own blog, every release with a filter per product, a news section on the home page, and an RSS feed per language.
Product marks — one family
Every app and service has its own mark: the company hexagon with its own glyph inside, same geometry and colour. Side by side they read as a set.
Tickets — report management
Admin /tickets + user My tickets + Support in the launcher. Poll without F5. Roadmap/docs/panel CTAs — next step.
Terms of service and privacy (CZ + EN)
Live Terms and Privacy pages in Czech and English; sign-in links no longer 404.
Security headers and OAuth redirect
CSP, HSTS and Cross-Origin-Opener-Policy on the web; OAuth error paths only allowlisted redirects (no open redirect).
Realtime tickets (no F5)
Ticket thread refreshes itself every few seconds — new messages without a manual refresh.
Other people’s avatars in the workspace
User lists and chat show everyone’s Discord avatar, not only yours.
Friends, chat and online status on the web too
Workspace user section /friends — same social graph as launcher. Presence from hub (poll). Admin section untouched.
Launcher connect — auto code handoff
After confirm: iframe + beacon + location.replace to 127.0.0.1 (not HTTPS fetch). Code is fallback only. Live on id.stygion.eu.
Design polish — rhythm, hero, icons, mobile
Tighter section rhythm, new hero, unified icons, consistent satellite pages and polished mobile navigation.
Docs feedback & comments in admin
The team sees feedback and comments per docs page in one place, can reply, and the author is notified.
Sign out
Sign out of STYGION ID at any time.
Source reference on a task card, on the board (team)
A team member sees a task’s source reference right on the roadmap, not only in the workspace; hidden from the public.
Internal team docs
Non-public team docs as a hidden mirror of the public section, team-only. Content is agent-managed; the manual editor is being removed.
Follow a task from its card
Follow a task in one click on its card; get a message on every change and when it ships. A finished task can no longer be followed.
Language switch on the roadmap
Switch the roadmap between Czech and English.
SEO & discoverability
Link previews, descriptions and a sitemap for every public page.
Card sub-tasks (checklist)
Open a task to see its steps — a start-to-finish checklist of the work.
docs.stygion.eu — public docs
Guides that explain how and why things work. Searchable, bilingual.
Custom 404 page
A branded page when a link goes nowhere — with a way back.
Brand-new homepage
Complete redesign of the stygion.eu homepage — new visuals, structure and copy.
Task timestamps + ordering
Every task shows when it was added and completed; columns sort newest-first.
Web = pure frontend/BFF, logic in the backend
Verified: web holds no business logic or crypto/secrets — the server-side BFF only proxies to the backend (which holds the service token, signs OIDC tokens, enforces authz). The browser never calls the backend directly.