GeezerVison

Add an article resource explaining how a small multiplayer web application separates prerendered public information from live room state.

The case study covers shared-component prerendering, anonymous build-time data, a separate WebSocket room service, action acknowledgements and checks for the static/live boundary. It is intended as a concrete architecture example, rather than a product-directory listing or a performance claim.

Disclosure: I am associated with Blather, the example project. The article is publicly available as a Markdown Gist and contains no application source, question bank or participant records.

Validation: reviewed the resource front matter in GitHub's rendered preview and checked that this comparison adds only one resource file (7 lines). A full Jamstack site build was not run.