---
title: "Slide deck template – Display.dev"
description: "An HTML slide deck – scroll-snap slides, stat cards, and a one-point-per-slide structure in a single file with no dependencies. Publish it to a URL in one click, no account."
---
# Slide deck template
An HTML slide deck – scroll-snap slides, stat cards, and a one-point-per-slide structure in a single file with no dependencies. Publish it to a URL in one click, no account.
- Format: HTML
- Detail page: https://display.dev/templates/slide-deck
- Raw template file: https://display.dev/template-sources/slide-deck.html
- One-click anonymous publish (no account): POST the file to https://api.display.dev/v1/public/artifacts as multipart/form-data (`file` field)
## Agent prompt
Build a slide deck on this topic on display.dev. Fetch https://display.dev/template-sources/slide-deck.html as the starting point – scroll-snap slides, one point per slide, stat cards for numbers. Replace the sample content, keep the one-point-per-slide discipline (split a crowded slide rather than shrinking text), and keep the file self-contained (inline CSS, no scripts, no external requests).
Publish it with the display.dev MCP publish tool if connected. Otherwise POST the file to https://api.display.dev/v1/public/artifacts as multipart/form-data (`file` field, optional `name`) – no account needed. You'll get back `previewUrl` (the link to share) and `claimUrl` (one-shot link to take ownership). Reply with both.
## What this template is for
A deck that's a URL, not an attachment. Scroll-snap gives you real
slides – one screen, one point – with no framework, no build step, and
no script tag: it's CSS only, so it renders anywhere HTML renders.
The structure encodes the discipline that makes decks readable: a
three-number summary up front, a "what we deliberately did not do" slide
(the one people remember), and stat cards instead of chart screenshots.
## How teams use it
- **Quarterly reviews and readouts.** The agent drafts the deck from the
quarter's shipped work and metrics; you cut it down to one point per
slide.
- **Sent before the meeting.** Because it's a page, people actually read
it in advance – and leave inline comments on the slide they disagree
with.
- **Presented as-is.** Full-screen the browser tab; scroll advances the
slides.
## Template source
````html
Q3 platform review – slides
Platform team · Q3 2026
Q3 platform review
What we changed, what it cost, what it bought us.
Scroll or press space – each slide is one point.
The quarter in three numbers
−38%
p99 API latency (410 → 254 ms)
−€8.4k
monthly infra spend
2
SEV-1 incidents (was 6 in Q2)
What we shipped
Read-path caching in front of the three hottest queries – the p99 win.
Queue consolidation from four brokers to one – the spend win.
Migration lint + staging at scale – no lock-taking migration has reached production since.
What we deliberately did not do
The multi-region read replica – demand didn't materialize; re-evaluate on the first EU-latency escalation.
Service extraction of the billing module – the monolith's boundary held; the extraction stays parked.
Q4 plan
October: retire the legacy search index (last consumer migrates 3 Oct).
November: load-test the write path at 3× peak before the seasonal spike.