The Golden Rules of Presentation Design
blog.thenounproject.com
blog.thenounproject.com
The main difference between the two being that the open source projects tend to have links to what I want to read about, and the paid software—sorry, “client solutions”—have about 10 menu items that all link to either a form to have someone give me a demo, or a form where I have to prove I already bought the goddamn thing in order to see how it’s supposed to be used.
I use this all the time to keep my slides sparse for when I'm presenting, but fully detailed when I distribute them as PDFs after the fact.
[1] https://support.microsoft.com/en-us/office/print-speaker-not...
ADDED: The other thing I see a lot is just create a very detailed slide deck but don't try to actually present it in detail. Which probably works well enough I guess given that it's a modern sort of expectation.
Example
----
== Here's a slide
The Crowd Sees This
[.notes]
* this is the new block type for speaker notes: sidebar
* `notes` role required (written `.notes` in block attribute)
* source is slightly more compact
* and not tied to an admonition which can be useful in slides
== Another Slide!
Holy heck we got a lot going on
GOODBYE
----
Furthermore, you could also filter out content that's ONLY destined for presentations by using the Conditional Directives vs the backend attribute. See also https://docs.asciidoctor.org/asciidoc/latest/attributes/docu... and https://docs.asciidoctor.org/asciidoc/latest/directives/cond...[1] Asciidoc Reveal docs https://docs.asciidoctor.org/reveal.js-converter/latest/
VSC Asciidoc-Reveal extension https://marketplace.visualstudio.com/items?itemName=flobilos...
I built myself a custom tool for that a few months ago and it's been working really well. I described that here: https://simonwillison.net/2023/Aug/6/annotated-presentations...
Often, what I present is interrelated with what I write but they don't tend to be 1:1.