Vortoj.

A game is only fun until every lesson change needs a developer.

Vortoj is an educational game for elementary school kids: language learning, music, and physical movement folded into a dance-pad experience. Great for the classroom. Slightly less great if every new set of words has to pass through a developer first.

The game needed fresh words, categories, languages, difficulty levels, images, audio, and question sets. The dashboard was the missing piece: a place where teachers could change the lesson while the game stayed the game.

Boring stack, sharp tool.

Time and budget were tight, so we did the sensible thing and resisted the urge to invent a tiny enterprise platform. Angular handled the dashboard. Supabase ran locally in Docker. PostgreSQL kept the content honest. The Godot game used the same auth flow.

That gave the project the parts it actually needed: user accounts, storage, content APIs, and a dashboard shaped around the game instead of around a generic admin template.

The dashboard covered the shape of the game.

• Word checks. Falling words, spelling choices, and gap-filling questions for quick grammar and vocabulary practice.
• Media prompts. Image-to-word and audio-word questions, because a language lesson should not be trapped in plain text forever.
• Adventure mode. Question content that can meet the player mid-level, not only inside a tidy quiz screen.

Teachers change the lesson, not the build.

Questions now live in categories split by language and difficulty, so teachers can tune the game to the class instead of waiting for somebody to package a new version.

That is the useful version of tailor-made software: not a generic CMS wearing a school badge, but the exact controls this game needed. Small enough to understand. Specific enough to matter.