The problem
Agents increasingly build presentations as a single HTML file: a slide per section, keyboard navigation, charts drawn in SVG. It presents well and reviews badly. Reviewers write "slide 4, the second bullet" in a chat, and the agent has to work out which slide and which bullet that meant.
How it works with Onlay
onlay push launch-deck.html
Reviewers open the link, page through the deck, and comment on a slide, a title, a bullet or an illustration. Each comment is pinned to that element, so it stays on the right slide when the deck is revised. With editing on, they fix a heading or a bullet directly.
Your agent runs onlay pull launch-deck.html and gets every thread with the element it is on. It revises the deck and pushes the next version to the same link, answering each thread.
Building a deck that reviews well
- Give every slide and every block in it a
data-onlay-id(slide-3,slide-3-title). Feedback then re-attaches exactly after a rewrite. The Onlay skill tells your agent to do this. - Keep the text in the HTML, not in JavaScript strings, so readers can select and edit it.
- Load a slide library by its full
https://address. On the Free plan a page loads the exact addresses written in the file, and a short list of CDNs loads freely. What a page may load.
Try one
The homepage has a live seven-slide deck you can comment on, with a demo agent that replies: onlay.io/#try.
When something else fits better
If the deck has to end up as a PowerPoint or Google Slides file, review it there. Onlay is for decks your agent makes as HTML.