slidewright

# Interactive presentation builder Build slide decks that run as a website and are **projected to a room**. The deck is the visual half of a talk; the presenter does the talking. Two ways to build, one shared design language. ## First, the mental model (read before writing any code) There is **one operator** (the presenter) on **one machine**. Slides go on a big screen; the audience only **looks** — they never click, type, or interact. Everything below follows from this. Three failure modes to avoid: - **Text too small.** Slides are read from across a room, not on a laptop. Never use web-reading sizes (`text-sm`, `16px`) or fixed Tailwind text classes (`text-4xl`). Always use fluid `clamp()` so text scales with the screen. Honour the typography floor (body ≥ ~40px on a 1080p canvas). See `references/design-system.md`. - **Content hugging an edge.** Padding is a two-layer contract. Slide content must stay inside the viewport safe area, and content inside a card, panel, callout, bordered box, or other visible container must stay inset from that container's own edge. A parent slide's padding does not protect a nested container; `gap` and child margins are not a substitute for the container's own padding. Both scaffolds provide safe-area padding and a `.slide-surface` inset helper. Even `fullBleed` slides keep text content inset. - **Building an app.** No input fields, no "Submit", no login, no data collection — there is no backend and nowhere for data to go...