What does course creation look like in the new builder?

How courses are built now that screens are made of blocks, what your customers see when they create one, and what that changes for an Embed integration.

Screens are made of blocks arranged on a six column grid, rather than chosen from a fixed set of screen types. A creator picks a layout, which gives them a pre-arranged set of blocks, then adds, removes and rearranges those blocks freely. Any block can sit on any screen, so one screen can carry an explanation, an interactive element and a knowledge check together.

For an Embed integration this is a content model change rather than an API change. Courses are still courses, screens are still screens with ids, and your existing integration code keeps working.

What is a block?

A single piece of content on a screen: a heading, a paragraph, an image, a table, an accordion, a question. The full set groups five ways:

• Text and structure: heading, paragraph (including lists and links), table, button.
• Media: image, video (landscape or portrait, with captions), audio including generated narration, slideshow.
• Interactive: accordion, checklist, process, flashcards.
• Documents and embeds: an embedded document, or external content in an iframe.
• Questions: seven types, used as a knowledge check on a screen or gathered into a scored quiz section.

A block is set to a width in columns, with a minimum of two, and dragged where it should sit. Blocks can sit side by side or stack down the screen.

Why a grid rather than a blank canvas?

Because the grid is what keeps your customers' courses looking designed rather than assembled. A creator chooses where things go within a structure instead of placing elements freely, so spacing and alignment stay consistent across every screen, and a course built by someone with no design background still looks like it belongs in your product.

What do creators start from?

Every screen starts from a layout, and the layout can be swapped afterwards. The layout picker groups them five ways:

• Content: text, images and video.
• Interactive: checklist, accordion, numbered list, acronym, flashcards, process.
• Knowledge check: a single practice question on a screen.
• Embed: large embed, text with embed, full document.
• Section intro: an emphasised cover screen that opens a section.

How do courses hold together?

Screens group into sections, which learners move through as chapters with their own progress. A course opens with a Start screen and ends with a Finish screen, with the sections in between.

A scored quiz is its own section, numbered alongside the content sections. It opens with a cover screen carrying the quiz title, the question count and a Start quiz button, gives each question its own screen, and ends with a results screen. A single question block on an ordinary screen is a knowledge check instead, and is not scored.

Where does AI fit?

The agent sits in the builder rather than only at the start. A creator can ask it to generate a block, a screen, several screens at once or a whole section, and to rewrite, restructure, add assessment, narrate, translate or theme what already exists.

The agent panel has three tabs: Chat for asking, Review for a check of the finished course with one-click fixes, and Insights for what learner data shows once people have been through it.

If you would rather your product drove all of this instead of your users talking to an agent, the same tools are available to your application over MCP or REST.

What does this change for my integration?

• Course and screen ids are unchanged. Anything keyed on them keeps working.
• The course embeddables are unchanged. Players, cards, lists, builders and analytics all behave as they did.
• Screen-level embeddables are the new surface. Screen Builder and Screen Player let you put single-screen creation and delivery in places a whole course would not fit.
• Themes still apply through themeId. A course built from blocks takes your theme the same way.
• Courses created without specifying a builder get the Classic builder. The new builder is opt in, so your application asks for it explicitly before your users see it.

Frequently asked questions

Do my customers have to learn a new tool?

They start from a layout and edit what is on the screen, which is close to the old flow. The difference is that the layout is a starting point rather than a fixed shape, so they can change it afterwards instead of picking a different screen type and moving their content across.

What happens to courses built in the Classic builder?

They keep working exactly as they do, they open in the Classic builder, and learners see no change. A course lives in the builder it was made in.

Is Hotspot still available?

Not as a block. Hotspot screens in courses already built in Classic are unaffected and keep working as they do today.