A BETTER WAY TO SHARE THE WORK
Turn the deck into a story that works without you in the room
The slides carried part of the argument. Your explanation carried the rest. Give asynchronous readers both.
New to creating with an agent? The request will guide it through the task. Bring your notes; you don’t need to write HTML.
How do I turn a presentation into a standalone reading page?
Give your agent the source slides, approved speaker notes and the question the reader needs answered. Ask it to rebuild the narrative for reading rather than reproduce slide screenshots. Carry over the evidence and caveats, and flag missing context. Review the result against the deck and notes before sharing.
01 / SEE THE DIFFERENCE
Four slides become one complete reading argument
Fictional support-guide pilot deck and notes. No customer results are implied.
Slide 1: Pilot overview. Notes: four guides planned. Slide 2: Three ready. Notes: three passed editorial review, not launch approval. Slide 3: Next step. Notes: account recovery awaits a policy answer. Slide 4: September 14. Notes: target only; sponsor decision still needed.
- Main answer
- Three guides passed editorial review; the four-guide pilot is not approved for launch.
- Evidence
- Four guides are planned. Account recovery still awaits a policy answer.
- Date in context
- September 14 is a target, not a launch commitment.
- Reader action
- The sponsor still needs to decide; the supplied notes do not specify a decision deadline.
Open a complete fictional HTML example, with its source notes →
Create my reading page from a deck02 / MAKE IT YOURSELF
Start with the evidence. Shape the page around the reader.
Recover the argument from the slides and notes
Ask the agent to identify the main claim, supporting evidence and conclusion across both sources. Speaker notes may contain the explanation that makes a sparse slide meaningful. If that explanation is absent, ask for it; a polished transition should not introduce a new factual claim.
Write headings that make sense alone
Replace prompts such as 'The opportunity' with the supported point a reader should understand. Explain acronyms and references that depended on the live talk. Keep each claim near its evidence, including a limitation that the presenter originally said aloud.
Rebuild visuals as readable evidence
Use approved data and labels to create a table or visual suited to the page. Do not estimate exact values from an unlabeled chart or use screenshots as the only source of meaning. Provide text explaining the relevant relationship. Keep the deck for live delivery or when editable slides are required.
Audit the adaptation against both sources
Compare the reading page with slides and notes, tracking what moved and what was omitted. Exclude private presenter reminders and internal commentary. An HTML adaptation is not a promise of automatic PowerPoint conversion, preserved animation or pixel-identical layout.
03 / TRY THIS PROMPT
Copy this into your agent. Add your source material.
Use the conversation where you already did the work, or start one with your notes. Replace the placeholders and supply any missing context; only attach information you are allowed to share with your agent.
Get the ready-to-copy creation request for guided questions, this task, and a draft review before anything is published.
Adapt my authorized source deck and approved speaker notes into a standalone static HTML reading page for [audience and question]. Reconstruct the argument rather than embed slide screenshots. Preserve evidence, data definitions, caveats and source references. Distinguish slide content from supplied explanatory notes; flag missing context instead of inventing it. Use readable narrative headings and explain visuals in text. Do not infer exact chart values, fabricate transitions as facts or include private presenter reminders. Ask only for missing essentials using existing authorized context. Use my saved artifact style if available. No scripts, forms, slide-conversion fidelity or animation promises. Show me the source-to-section mapping and draft. Do not publish or change access without separate explicit approval.
04 / BEFORE YOU SEND
A polished page still needs your judgment.
- Can someone who missed the talk understand the argument and next step?
- Are the page's claims supported by the slides or approved notes?
- Are chart values, definitions and spoken caveats preserved accurately?
- Have private notes and unsupported contextual additions been excluded?
When HTML fits
A read-ahead, recap or standalone explanation for people who will read asynchronously.
When another format fits better
Keep the source deck when people need to edit slides, present live or retain slide-specific production details. Use a separate format decision for fixed-file or offline delivery; this workflow does not export a PDF.
FROM DRAFT TO A LINK
Make it clear. Make it yours. Then share it.
Keep creating and revising in the agent you already use. With a compatible connection, share/artifacts publishes the reviewed HTML so you do not have to rebuild it in another editor. Ask your agent to use your saved artifact style for headings, color, and tone; review the result before sending it.
Choose who should be able to open the page and verify the returned link. For corrections to the same deliverable, update the existing artifact without changing its link. Publish a separate artifact when the old edition needs to remain available.
These are static pages, not live apps: no scripts, forms, or automatic data refresh. Source collection and scheduling depend on your agent and its available tools, not on share/artifacts.
Make this with my agentQuestions before you start
Can I use the slides without speaker notes?
Yes, if the slides already contain enough context. Ask the agent to flag unexplained claims or missing definitions. Do not assume it can recover what was said during the presentation.
Will it look exactly like the deck?
The goal is a readable adaptation, not pixel-identical conversion. Preserve facts and brand direction while letting the reading layout differ from projected slides.
Should I share slides or a reading page?
Use slides when live delivery or editable slide files matter. Use a reading page when the argument should stand on its own. If recipients require a fixed file or offline delivery, evaluate that requirement separately.