How Our Team Works

How Our Team Works

Classroom 6X is run by a small team of people who enjoy browser games and care about making them easy to play. Rather than introduce ourselves with headshots and job titles, we think it is more useful to explain what we actually do each week to keep the site working. Everyone on the team plays the games, and most of us cover more than one of the roles below.

Curation

Curation decides which games join the library and which ones leave. We look for HTML5 and WebGL games that run without downloads, play well on a Chromebook, and add something to the collection instead of repeating what is already there. Suggestions from players are a big source of new titles. Curation also means saying no: games with graphic content, intrusive redirects or unreliable hosting are not listed, however popular they may be.

Quality Assurance and Testing

Before a game goes live, it is loaded and played on several devices, typically a low-cost Chromebook, a laptop and a phone, across more than one browser. Testers check that the game starts, that controls respond, that fullscreen works and that sound behaves properly. After launch, QA rechecks games on a rolling schedule and handles reports from the report button. When a source breaks, testers look for a working backup server or recommend removing the game.

Editorial

The editorial side writes game descriptions, category pages, guides and blog posts. Our rule is simple: describe games accurately, explain controls clearly and never invent facts. We do not publish fake statistics, fabricated reviews or claims we cannot back up. Where a game contains jump scares, online chat or cartoon violence, we say so, so that players, parents and teachers can make informed choices.

Player Support

Support reads messages from the contact form and reports submitted from game pages. Common requests include broken games, game suggestions, questions about saved favorites, and copyright or removal requests from developers. Technical issues go straight to QA, and rights requests are handled according to our DMCA policy. We aim to reply to every message that needs a response.

How We Work Together

These roles overlap constantly. A support message about a slow game becomes a QA test, which can lead to a new backup server and an editorial note on the game page. Because the library is intentionally a manageable size, the whole team can stay familiar with it and notice problems quickly.

Get in Touch

If you have feedback on how we work, a game you would like us to test, or you are a developer with a question about your title, please reach us through the contact page.