See which slides of a reveal.js deck were read.

Prepare the deck for a tracked link

1. 1

   Use a standalone HTML file with styles, scripts, fonts, and images inlined, or a public deck whose assets use absolute URLs.

2. 2

   Put one useful h1, h2, or h3 in each slide when you want those exact labels in the dashboard.

3. 3

   Upload the HTML, or paste the public URL, then send the generated tracked link.

The dashboard names each slide by its heading, and by its place in the deck when a slide has none. So the title a reader sees is the title you judge it by.

What stays intact

HTMLRadar serves your deck and adds its tracker to the page it serves. There is no reveal.js plugin or code to add. Your deck’s own transitions, keyboard navigation, and plugins keep working when their scripts and styles are available to the shared page. Free links also show a small “Sent with HTMLRadar” line.

reveal.js plugins are ordinary scripts registered when the deck starts; the reveal.js documentation covers plugins and the built-in speaker-notes plugin. reveal.js plugin docs.

What the dashboard measures

Each reader is recorded separately: active reading time, how far they scrolled, and the time on each slide. A slide counts only once it has been on screen long enough to be read, and time stops counting after five seconds without any sign of the reader. That keeps a background tab from looking like a long read.

The multi-file build caveat

HTMLRadar does not rewrite relative asset paths when it serves a URL source. A local reveal.js build that depends on dist/ files beside it should be exported as one portable HTML file first. For a hosted deck, use absolute URLs for the reveal.js assets. That is the difference between a link that shows the deck whole and one that loses its theme or plugins.