Architecture · nbg-design · Diagram Design
Inside a delivered deck
Inside a delivered deck
Architecture of one delivered HTML file: the slides and the inlined editor block, the menu and toolbars the editor builds in the browser, the edit records kept in browser storage and re-applied on load, and the three ways out — a saved edited copy, a PDF through the print layout, and an optional call to the viewer's own LLM endpoint.
DECK.HTML · ONE FILE
IN THE VIEWER'S BROWSER
WAYS OUT
BUILDS THE UI
RECORDS EDITS
RE-APPLIED ON LOAD
EDITS IN PLACE
EXPORT TO PDF
SNAPSHOT AT LOAD
APPLY RECORDS
PRINT LAYOUT · SAVE AS PDF
HTTPS · VIEWER'S KEY
HTML
Slides
N × .slide, images embedded
JS
deck-menu.js
the editor, ~3,900 lines
JS
print-layout.js
same shim as the CLI exporter
UI
Menu & toolbars
tabs · text and shape rows
STORE
Edit records
localStorage · path, original, html
EXT
LLM endpoint
your provider, your key
OUT
Saved edited copy
deck-edited.html, still one file
OUT
PDF
print dialog → Save as PDF
LEGEND
Focal component
Browser storage
Outside the deck
Calls / writes
Passive: taken or re-applied on load
HTTPS