Session 0A: A session about a thing
A spectacular pun
Get the slides
This deck’s slide content can be split into separate _SECTION_*.qmd files at the project root and pulled into slides.qmd with {{< include >}} – see the top of slides.qmd for how this file is wired in, and the “Fast iteration on a single section” note in README.md for how to preview a section like this one on its own.
You can see that while there are a few quirks, the separate slides can display primarily as they will in the final deck.
Your Content Here
This is a slide with some text on it.
Here is column 1
Here is column 2
This will be on the screen at the start.
This will be on the screen at the start.
This won’t appear until you press a button.
Then this will appear when you’re ready.

Value boxes
A simple value box can help convey points, especially when combined with fragments.
This appears SECOND (Index 2)
This appears FIRST (Index 1)
There are some speaker notes on this slide - but you can’t see them unless you’re in speaker view!
Use the {.no-box} syntax next to your slide title to remove the background grey box.
This only works on second level slides - not # level slides.
Value boxes
A simple value box can help convey points, especially when combined with fragments.
Value boxes
Like this!
And here’s a more advanced type of box with an icon
And here’s a more advanced type of box with an icon and a value
And one without an icon
This appears SECOND (Index 2)
This appears FIRST (Index 1)
You can use the {.focus-list} div to auto fade in and out as you move through a list
This works with indented lists too
Using reunings code focus extension, we can highlight different parts of a code example.
When this fragment is shown, the first line of code will have the focus class added to it and it gets highlighted.
Then this line when we move through
The title slide (the very first slide of the deck) is generated from the title-slide.html partial and styled by title-slide.scss. It is driven entirely by YAML frontmatter keys — see the top of this file for the values used to build this deck’s title slide:
title, subtitle — the module/session textauthor — as before; the author name is coloured via $hsma-title-author-colortagline — short strapline, coloured via $hsma-title-tagline-colorpartner-logo / partner-logo-alt — a logo shown on a white plate, top-righttitle-image — a small image/GIF (or video:) shown above the title texttitle-media-a — a single image/video panel, top-left of the slide (position: right moves it under the partner logo; bare: true drops its shadow box)title-countdown — a timer, top-left: true = 10 minutes, or give minutes / "m:ss"title-media — a list of image/video panels, bottom-right of the slidetitle-box-image — an image just above the title box, matching its width (image:/alt:, or placeholder: true)title-video — a video panel, bottom-right: youtube: (video ID) or video: (file); no-controls: true hides the player UI; placeholder: true shows an empty boxsplash — adds a slide before the title slide with just logos over the banner (optional background: overrides the title slide’s background); each logo takes an optional position: (e.g. top-centre, bottom-right) and height:title-audio — src: (and optional loop: true) for audio that starts when the title slide is shown and stops when you move off itpartner-logo-plate — none or dark for white logos that vanish on the white plateqr-code — QR code to the hosted deck: auto works out the GitHub Pages URL, or give a URL (optional qr-code-caption:)Every key is optional. Leave all of them out and the title slide falls back to the original centred title/author layout.
Each media slot accepts either image: (works for GIFs too) or video: (plus optional poster: and autoplay: true).
If a deck needs a hand-built title slide instead of the generated one, add data-visibility: hidden to title-slide-attributes to hide the generated slide, then reuse the same styling on a normal slide with the .hsma-title class and the .hsma-ts-* slot classes shown below:
