Skip to content
Branching Tales

Architecture explainer

About Branching Tales

A concise map of what Revisium provides, what the app writes, and where to evaluate the proof surfaces.

  • 80/20 story
  • architecture
  • source links

What this demo proves

Branching Tales is a public RPG codex where Revisium supplies schema-first content and this frontend turns it into browsable player-facing surfaces.

1

Frontend

React Router SSR shell, locale state, page slices, and Explainer Widget.

2

GraphQL

GraphQL router exposes generated data and CMS tables to the app.

3

Revisium

Revisium owns schemas, rows, localized fields, file metadata, and drafts.

4

Backend

NestJS subgraph can add runtime counters, comments, and recommendations.

Revisium generated

  • schemas and typed tables
  • localized content
  • file fields
  • formula values
  • draft revisions

Frontend wrote

  • React Router screens
  • MobX ViewModels
  • GraphQL request orchestration
  • responsive UI
  • route relationships

Schema-first catalog

Start with the implemented world catalog and inspect source proof.

Open

CMS guide surface

Read the guide catalog that comes from CMS rows and author references.

Open

Branching story

Preview the revision comparison route while its data dependency is blocked.

Open

Home

Browse the public game database entry point.

Start

World atlas

Inspect a file-backed catalog with pagination and source links.

Proof

Items

Open gear filters, formulas, and SVG file fields.

Proof

Guides

Read CMS-backed guide content and author references.

Read

Frontend repo

Frontend implementation, docs, and review rules.

Open

Backend repo

Backend subgraph for runtime extensions.

Open

Docs repo

Public product and DevRel documentation.

Open