Capsule trainings

The capsule is the object you build: a sequence of notions, each carrying content and, most of the time, a quiz. Its length is your decision, from a handful of notions read between two tasks up to a full e-learning course; nothing in the product fixes a duration.

The training type is decided earlier, in Understanding trainings: it changes how the learner commits, not how you build.

This section stops at the finished capsule. It puts it in front of nobody: until the capsule has a track, a listing set with To be displayed on the catalogue of, or a custom diffusion rule carrying groups, nobody can publish it. That is the subject of Publishing a capsule, and it is why authoring and distribution are two separate sections.

Where a capsule comes from

Five starting points, one object at the end: whatever the origin, you then edit the capsule the usual way, and the origin commits you to nothing.

• Creating a capsule from scratch: when you already know what to say and in which order.
• Generating a capsule with AI: when you have a subject and objectives, but no written material yet.
• Generating a capsule from a PDF: when the material already exists as a document and only needs cutting into notions.
• Importing a capsule: when the capsule exists elsewhere and the point is to retrieve it rather than rewrite it.
• Reusing content and working with several authors: when an existing capsule is the starting point, or when several people build the same one.

What happens next

A capsule that has just been created stays in Draft: it exists in the back-office, no learner sees it, and you can come back to it as many times as you need before releasing it.

• Activity formats: what a notion can hold, worth reading before you write everything as running text.
• Submitting a capsule for validation: if your account has capsules reviewed, read it before promising a go-live date.
• Version history and restoring: to go back to an earlier state, or recover what an edit made disappear.

And when a capsule does not behave as expected: Common problems: creating content.