Overview
Content bricks are used to present information to learners. They don't require interaction — they're the building blocks for delivering knowledge.
Text & Typography
Heading
A title or section heading with customizable styling. Supports rich text formatting (bold, italic, subscript, superscript).
Text
A rich text block for paragraphs and formatted content. Supports the full formatting toolbar including lists, links, colors, and alignment.
Quote
A styled quotation block with optional author attribution. Ideal for highlighting key statements or expert opinions.
Note
A highlighted information block with different variants (info, warning, tip, important). Draws attention to key information.
Highlight
A prominent text block with custom background and styling for emphasizing key concepts.
Media
Image
A standalone image with optional caption and alt text. Supports:
- File upload (PNG, JPEG, WebP, SVG)
- Stock image search
- AI image generation
- Image cropping
For a complex image (a diagram, an infographic), the Extended description field, under the alt text, holds the detail a short alt text cannot: paragraphs and lists, no links. Only screen readers read it — it stays hidden on screen and the image points to it. A decorative image (empty alt text) is not described. In the PDF export it is printed under the image.
Image and Text
A side-by-side layout combining an image with rich text content. The image position (left or right) is configurable.
Video
An embedded video player. Supports:
- YouTube and Vimeo URLs
- Direct video file upload
- Configurable height
Audio
An audio player with playback controls. Supports:
- Audio file upload
- AI text-to-speech generation
Attachment
A downloadable file link. Upload documents (PDF, Word, Excel, etc.) that learners can download.
Code & Technical
Code
A syntax-highlighted code block supporting multiple programming languages. Code bricks are not translated when using the translation feature, preserving your source code intact.
Embed code
An embedded interactive element. Three modes:
- Upload folder — Upload an HTML folder (must contain
index.html) - URL — Embed an external URL via iframe
- AI — Generate interactive HTML content with AI (organization scope only)
Embedded code does not hold learners back by default: it counts as completed when seen, and the theme's "interactive blocks must be completed" switch does not apply to it; it only blocks if you turn the blocker on in the brick or in the theme's embedded-code settings. An uploaded package can tell the lesson that it is finished —and then the blocker waits for that message— or report its height, so the frame fits its content; to do so it declares it in a slxd-embed.json file at the root of the folder. If the blocker is on and the package cannot report completion (or it is an external URL), the editor shows a warning.
An uploaded package can also be a simulation: if its slxd-embed.json declares state, result or interaction, the lesson keeps its progress (and hands it back when the learner returns), its score when it reaches an ending and each decision (in SCORM, in cmi.interactions). In the brick’s panel, once the package is uploaded, give it a simulation identifier that is unique within the content and, if its score should count, mark it Scored with its weight. Inside an exam, its score counts next to the questions and the exam does not close until the simulation reaches an ending; in a content without exams, the content’s score is the weighted average of its scored simulations once all have finished, with the content’s pass threshold. A simulation finishes —and its score is fixed— when the package reports that it is done (complete, or a state marked as an ending); a score sent earlier only updates the grade, and the last one before the end is the one that counts (0 if none was sent). A package marked Scored must therefore declare complete or state. When the content’s score comes from its simulations, the export page shows the pass threshold, and each decision and score is also reported to the LRS with xAPI. The editor’s warnings tell you if something is missing (a repeated identifier, a package that does not send its score…). Its slxd-embed.json may also declare the variables of its state, with their type ("variables": {"trust": "number", "reused": "boolean"}), for conditional content to read them; grade, score, maxScore, ending and kind are reserved names (they always read the package's result) and a package that declares them as variables is not accepted when uploaded. The manifest, the messages and their limits are explained in Embed Packages and Simulations; to show or hide bricks depending on a simulation's outcome, see Conditional Content.
Layout
Separator
A visual divider between content sections. Supports custom shapes and styles.
List
A structured list with ordered or unordered items.
Chart
Data visualization brick supporting multiple chart types:
- Bar chart
- Line chart
- Pie chart
- And more