Build the production
Create scenes and locations. Set framing, angle, movement, lens, lighting, sound and direction for every shot.
Shot Atlas expands my original shot planner into a complete production workflow, connecting creative decisions with the practical work of making a film.
Framing decisions, reference images, shoot timing and continuity notes need to stay connected.
The original prototype planned individual shots and saved a sequence in the browser. This expansion adds private productions, scene organisation, storyboard references and a schedule derived from the shooting order.
Create scenes and locations. Set framing, angle, movement, lens, lighting, sound and direction for every shot.
Separate finished screen duration from setup and shooting time. Reorder shots to update the schedule from call time.
Mark shots planned, filmed or needing a retake. Print shot cards, export CSV or back up the production with its reference images.
React and TypeScript on a Cloudflare Worker, with D1 records and R2 image storage.
Each production is a bounded, versioned document. The server checks ownership on every read and write, validates shot data and compares revision numbers in the update query. A stale save returns a conflict instead of overwriting newer work.
Image uploads are size- and format-checked, with private retrieval. Backup imports create a separate production and preserve a recoverable working copy if image restoration fails.
Automated workflow checks cover validation, schedule calculations, CSV formula neutralisation, save/reopen behaviour, conflicting saves, cross-user access and storyboard ownership using an in-memory SQLite database.
TypeScript checks and the production build pass. Real-browser visual and hosted sign-in verification remains outstanding.
The sample is fictional. Shot Atlas is a planner, not an optical simulator or a real-time collaborative editor. Saved work uses explicit Save actions; the original GitHub repository contains the earlier browser-only prototype.
Original prototype source