speaker-notes-and-handoutslisted

# Speaker Notes and Handouts ## When to use Use this skill when a deck has to exist in more than one form: the version on screen, the version the presenter reads from, and the version the room takes away. Symptoms that it is needed — notes that print in six-point grey, a leave-behind at nine slides per page that nobody can read, a handout with last quarter's date in the footer, or confidential notes that travelled to a client because nobody stripped them. Do not use it to write what the speaker should say; this skill governs the containers, not the script. ## What it does It configures the notes master and the handout master, chooses the right print and PDF route for each audience, and closes the leaks — stale footers, unstripped notes, unreadable thumbnails. The output is a configured pair of masters plus a print/export recipe per audience. ## Method **1. Separate the three artefacts.** They are different documents with different jobs and they are governed by different masters: | Artefact | Governed by | Audience | |:--|:--|:--| | The slides | Slide master and layouts | The room, on screen | | Notes pages | Notes master | The presenter | | Handouts | Handout master | The leave-behind | In the file these are separate parts: `ppt/notesMasters/notesMaster1.xml`, one `ppt/notesSlides/notesSlideN.xml` per slide that has notes, and `ppt/handoutMasters/handoutMaster1.xml`. A deck with no notes has no `notesSlides` folder at all. **2. Set up the notes master.** `View > Note