Content block reference

The blocks you build a lesson from, what each is for, and when to reach for it. The scored question types have their own page.

#Basic blocks

#Heading

Splits a lesson into sections. Headings are not decoration: they are what a learner skimming the page uses to find their way, and what a screen reader uses to jump between sections. A long lesson without headings is hard work for everyone.

#Rich text

The workhorse. Bold, italic, lists, links and the usual formatting. Text blocks can also contain placeholders that fill themselves in, such as the learner's first name or your organization's name.

#Image

A picture from your document library or uploaded on the spot, with alt text describing what it shows. If the image is purely decorative, mark it as such and screen readers will skip it.

#Video

An uploaded video or a link to YouTube or Vimeo. A linked video costs you no storage. You can set a custom thumbnail.

When a lesson has a main video, the learner has to watch it before they can continue, so length is a real cost to them.

#File

Something to download: a handbook, a checklist, a form. The file lives in your document library, so the same one can be handed out by several courses.

#Line and timeline

A sequence of steps or events, shown as a line. Useful for a process, an escalation path, or what happens after an incident is reported.

#Separator

A horizontal line. A visual pause between two parts of a lesson that do not need a heading each.

#Rich blocks

#Column layout

Puts two things side by side, an image next to its explanation for instance. On a narrow screen the columns stack, so never rely on left and right meaning anything.

#Table

Rows and columns for things that genuinely are tabular, such as limits, intervals or responsibilities. Tables scroll sideways on a phone rather than squeezing, so a table with eight columns will be awkward on the device many people use.

#Info callout

A highlighted box for something that must not be missed: a warning, a rule, an exception. They work because they are rare, so a lesson where half the content is in callouts has none.

#Button link

A link styled as a button, pointing at a form, an intranet page or a policy document, optionally opening in a new tab.

#Code block

Code with syntax highlighting and a filename. Only relevant for technical training, where it beats a screenshot of an editor.

{
  "type": "near-miss",
  "area": "warehouse",
  "reportedWithin": "24h"
}

#Interactive blocks

#Accordion

Collapsible sections. Good for reference material and edge cases that would otherwise double the length of a lesson: the main thread stays readable and the detail is one click away.

#Tabs

Parallel variants of the same content, for example the same procedure for two different machines. The learner picks the one that applies to them.

#Flashcards

Two-sided cards the learner flips. Suited to terminology and definitions, where the work is memory rather than understanding.

#Checklist

A list the learner can tick off as they go. It changes nothing about their progress or score, which is the point: it is a working aid for following along, not an assessment.

#Input blocks

Input blocks ask the learner something without scoring it. They make a lesson a conversation rather than a page, and their answers can drive which blocks appear next.

#Dropdown, toggle and selector

A dropdown for one choice out of many, a toggle for yes or no, a selector for a small set of visible options.

Their real power is conditional visibility. Ask which department someone works in, then show only the part that applies to them, so everyone reads one coherent lesson instead of skipping past three sections that are not theirs.

#Gamify blocks

Two small games. Used once in a course they wake people up; used in every lesson they wear thin.

#Guess the word

The learner works out a word within a number of attempts you set.

#Hangman

The familiar game, with a word you choose. Best kept for a light moment at the end of something heavy.