# Brief: Presentation Read this before writing. Then read `theme.css` for the classes and open `exemplar.html` to see a complete, correct deck, including the navigation script. ## Purpose A deck supports a spoken argument and then survives without the speaker. Each slide makes one point, stated in its heading, so that reading only the headings gives the argument. Speaker notes carry what would otherwise be said aloud. ## Audience A live audience in a meeting, then the same people and their colleagues reading it later on a laptop or phone. Design for the reader: the deck must make sense scrolled top to bottom without narration. ## Structure The document is `
` containing `
` ... `id="sN"`, one per slide, plus fixed chrome: a `.so-progressbar`, a `.so-deck-nav` with previous and next buttons, a `.so-slide-counter`, and a `.so-help` hint. Each slide wraps its content in `.so-slide-inner` and carries a `.so-slide-num`. Slides, in this order: 1. **Title** (`.so-slide.is-title`): kicker, title, one-line thesis as `.so-lede`, presenter, date, audience. Logo optional. 2. **Agenda**: three to six items matching the section dividers. 3. **Content slides**: eight to twenty. Use `.so-slide.is-section` as a divider before each topic. Within a topic, one point per slide. Layouts: bullets (max five), `.so-cols` two-column, `.so-big` for a single number with a one-line explanation, `.so-table` for comparisons, `.so-figure` for an inline SVG chart, `.so-callout` for the one sentence a skimmer must not miss. 4. **Summary and asks**: the thesis in three bullets, then the decisions requested with owner and date. 5. **End** (`.so-slide.is-end`): where the deck and supporting documents live, and the `.so-footer` with the brand footer text. Every slide may include `