Scrollable Deck
Why public reporting decks should be assembled from reusable slides and live governed data instead of pasted screenshots and manual collation.
This scroll view is assembled from the same slide resources as the presentation deck.
Speaker Notes
Open with the pain: business decks often pretend to be static documents, but they are really recurring data products. The chart image is intentionally familiar: a manually copied business graphic that should have come straight from governed data.
The promise of this deck is that slides can be web resources that query trusted data and stay current.
Speaker Notes
Use this slide to name the hidden operational cost. Every export, paste, screenshot, and formatting pass is a small control failure: provenance is lost, the numbers go stale, and reviewers spend time checking presentation mechanics rather than business meaning.
Speaker Notes
This is the architectural pivot. A slide is not just a rectangle of HTML; it is a resource with state. The template controls presentation, while the query controls what data is assembled for that presentation.
This lets different decks reuse the same slide patterns without copying the facts.
Speaker Notes
Point out that this slide slot is embedding a reusable speaker-bio slide. The wrapper slide does not copy Malcolm's profile text. It references another slide resource that owns its own query and template.
Speaker Notes
Show the actual query that reads Malcolm's public profile from the CMS graph. This is the mechanism behind the previous visual slide: RDF in, framed JSON-LD out, rendered HTML from a template.
Speaker Notes
Connect the pieces: named graph, canonical profile resource, query, frame, and template. The important claim is not just that the deck is dynamic; it is discoverable and inspectable as ordinary web resources.
Speaker Notes
Explain that navigation is not hardcoded JavaScript knowledge. Each slide advertises standard and extension link relations. Browsers use them for keyboard navigation; agents can use the same links to explore the deck and inspect how a slide is produced.
Speaker Notes
Generalize beyond speaker bios. Policies, training material, release notes, and board packs all suffer from the same stale-copy problem. Data-centric slides let those documents reflect governed source data instead.
Speaker Notes
Close by returning to the newsletter or reporting workflow. The point is not prettier slide automation; it is replacing manual collation with linked, governed resources that humans and agents can both traverse.