Creating a module

Creation happens in the chat home: you attach the sources, describe what you want, and Vidext plans internally before opening the module build. You review and edit the actual draft rather than approving a separate outline. This page is the map of that workflow; the rest of this section covers each stage in depth.

One module at a time

Vidext creates one focused module per request: a single learning experience on one topic ("GDPR basics", "Handling returns") — fast to create, easy to maintain. A new module starts as a standalone entry in your module library; you add it to one or more courses when it's ready, so the same module can be reused. Asking for a "course" produces the same thing: one module.

For bigger goals ("Sales onboarding"), work module by module — create the most valuable module first, then describe the next one in a new request. A strong module today beats a perfect course next month.

The creation path

Describe what you want — and attach what you have

In the chat composer, attach any sources (uploads, a website, or connected sources), then describe the outcome you want. You don't pick a use case up front — Vidext infers the right methodology from your request. It asks a clarifying question only when the action you want is genuinely ambiguous, not just because detail is missing.

Plan and build: go straight to the module

An explicit request to create or build makes Vidext produce a structured plan internally and hand it straight to the builder. The module opens without an outline panel or a second confirmation turn. Narrative, on-screen text, layouts, and interactions appear first; visuals and voice narration follow as the build continues. See Build, review, and publish.

Review: edit the real draft

Review the content as it arrives. Use chat for broad changes or select a scene, heading, image, or quiz to target an exact adjustment. When the build is complete, preview the draft in the learner player.

Finish: publish and assign

When it reads and plays correctly, choose Publish. That starts presenter-video rendering and version verification. The version becomes live only after the whole result passes; until then learners stay on the previous published version.

A published module is still not delivered. Putting it in front of people is four more actions, and they belong to delivery rather than creation — see Teams and assignment.

What you need before you start

One honest answer to each of these is enough:

Who is this for? ("New support agents in their first month")
What should they be able to do afterwards? ("Resolve a standard return without escalating")
What material do we have? (A policy PDF, a process doc, the relevant help-center pages)

Thin sources are recoverable

You can create from a prompt alone if it carries enough direction, and Vidext can research public or official sources where your prompt calls for it — but your own material always produces the most accurate, most on-brand result.

A plan-only request stays in chat

Ask for a plan, outline, or structure without asking Vidext to create the module and it will present the plan in chat, then stop. No module or build is created until you explicitly ask for one.