The presentation view

An optional overview deck introducing the topic — slides feature existing units; the detail stays in the book.

The presentation view renders a single-file slide deck from data in data/presentation/: one presentation block holding pres_sections (deck columns), each holding pres_slides. It is the topic's *introduction* — what you'd flip through before opening the reference book, or present to a room.

A slide is deliberately thin: it can name a unit to feature (the projection pulls that concept/entity/fact/process's headline and summary onto the slide), carry a short wdoc body (bullets, a diagram), and hold speaker_notes for the presenter overlay. Content discipline follows from that shape — a deck *arranges* existing units; it is not a second home for reference material. If a slide needs substance the model lacks, capture the substance as a unit first and feature it.

The view is optional. Ship it by declaring artifact slides { kind = :presentation … } in wskill.wcl and authoring the deck data; just presentation-build renders it. In the built deck, arrow keys move between sections and slides, Space steps through reveals, and s toggles the speaker notes.

§ 1Examples

§ 1.1Authoring a slide that features a unit

A slide names a unit; the projection pulls its headline and summary — the detail stays in the book.

presentation intro {
  summary = "One-line deck subtitle."
  pres_section what {
    title = "What & why"
    pres_slide opening {
      unit = wskill_concept
      speaker_notes = "Open with the one-folder, many-views idea."
    }
  }
}

Expected: The built deck shows a slide headed with the unit's name and its summary in italics, plus your notes under s.