← Back to projects

Open-source games site · Zubra in five frameworks

open.parlor

A family games site with 94 card, board, word, dice, and arcade games, built to test Zubra in a real app where five frameworks share one set of components.

My role: Creator · Maintainer

Pick a name, choose a game, and practice against the computer. No sign-up is needed.

The problem

A demo page per framework cannot show that a component compiler holds up. Real apps need tables that update every move, validated forms, dialogs, drag and drop, timers, offline play, and many pages.

The solution

open.parlor is a real app built the way teams build them. Each framework owns a different part of the site: React runs the game tables, Vue the lobby and house pages, Svelte the card designer, Solid the watch page, and Angular the admin app. The game list and daily page are drawn by the server and work with JavaScript off. Families get houses with their own tables, leaderboards, and tournaments, plus computer players and a widget that puts a game on another site.

My contributions

  • Built one set of Zubra components and used it from React, Vue, Svelte, Solid, and Angular, each in the part of the site that suits it.
  • Wrote a conformance suite of 214 checks that runs the same fixture page in each framework across Chrome, Firefox, and WebKit.
  • Drew the game list and daily page on the server with Zubra's server rendering and server functions, so they work without JavaScript.
  • Ran every game's rooms on Zubra's sync layer through open.rooms, with offline practice games against computer players.
  • Packaged it as one small server that can be self-hosted with Docker.

Behind the project

It began as a Spades game for a family blog and it is still played. The games made it a fair test for Zubra, so every package moves to each Zubra release as it comes out. The games and rooms live in their own packages, open.games and open.rooms, with open.chat for chat and open.relay for player bug reports.

Engineering decisions

Two rules keep the results honest. A fixture page never carries a workaround: if one framework needs something the others do not, that is a finding and goes upstream as an issue. A known difference stays visible as a check marked expected to fail until the fix lands. The suite has found slotting bugs in four frameworks and missing disabled states in form controls, all since fixed in Zubra and Zubra UI.

Testing

CI runs the conformance suite and browser tests of the real parts against the parlor's own server on every pull request, in Chrome, Firefox, and WebKit. I built the app from source and played practice games locally to capture these screens.

Repository
journey-to-code-org/open.parlor
Repository updated