Turn a WWII unit history book into an interactive 3D experience

A Redditor had Claude read a scanned 368-page 1945 cavalry unit history and Claude Code build a browser 3D retelling of a grandfather's battle, plus pages for all 2,655 men named in it.

Done withClaudeClaude Code· Nov 16, 2026

What they did

The poster owns a history of the 106th Cavalry Group that its men printed in Germany in 1945, with rosters of almost the whole unit. Their grandfather, a lieutenant in B Troop, is named twice in it, both times in a forest attack in Lorraine in October 1944. They scanned the book with a phone scanning app and gave all 368 pages to Claude, which ordered the story by troop and date, flagged OCR mistakes and caught duplicate names. Claude then pulled out the rosters, matched names in the narrative to men on them, and generated a page per soldier. Claude Code wrote the 3D scenes with three.js (terrain, trees, weather, figures, gunfire) and adjusted the look by taking its own screenshots and comparing. The poster set two rules: nothing invented beyond the book, and every scene labelled by how strongly the book places their grandfather there.

How it went

They published three pieces as Claude artifacts: a two and a half minute interactive scene of the October attack ending on the real medals, a chapter-by-chapter route from Normandy to Austria with the page scans one tap away, and a searchable directory of all 2,655 men. Sound came from 50 public-domain recordings placed in space. The poster calls it unfinished: the figures are rough, and one figure walked through a tree until they added a build check that fails on collisions. A friend told them the original pages and maps should lead, and that is their next step.

Worth knowing

Keeping the agent from filling gaps took an explicit rule; without it a battle scene invites invented detail. In the comments, a person doing similar work with naval records said frontier models got expensive for OCR at this volume, so they run two local models and hand-check only the lines where those disagree.

Try it

With Claude· 6 parts to fill in

I have scanned [book, diary or unit history] as [number] page images. First read every page, fix OCR errors, and build a structured timeline of events by [unit, person or place] and date, plus a list of every named person with the pages they appear on. Show me the timeline and any names you were unsure about before building anything. Then build a browser experience with [three.js or my preferred library] that walks through [the event or period I care about], labelling each scene by whether the source names [person] there or only places their group there, with the original page one click away. Do not invent events, dialogue or details the source does not support. Stop when every scene links to its source page and the build runs without errors.

Square brackets are the parts to fill in. The prompt is ours; the story is theirs.

Where they said it

Related