Editing published content

A published module is not frozen. When a policy changes or a quiz needs sharpening, describe the change in plain language and Vidext applies it to your draft — no rebuild, no re-approval ceremony for content-level changes. Your edits accumulate on the draft (the published version keeps serving learners unchanged); when you're ready, Publish to push them live. See Draft and published.

What you can ask for

• Text — rewrite a scene's copy, fix terminology, change tone.
• Quizzes — edit questions, answers, or explanations; add or remove checks.
• Structure — add, remove, reorder, or move scenes; reorder chapters; and insert a new chapter at the start, at the end, or next to one you name. If a new chapter needs an adjacent scene adjusted so the module still reads continuously, Vidext previews that change and asks you to approve it first.
• Layouts — change how a scene presents its content.
• Media — replace an image (describe a new one and Vidext generates it, restyle an existing one used as a reference, or upload a file to swap in), or regenerate narration and audio for the scenes you touched. Presenter video is regenerated after the next Publish.

Point at what you mean

You don't have to describe a scene in words to target it. Select an element directly in the module — a scene, a heading, a bullet, an image, a quiz — and your next message applies to that selection, so "make this shorter" or "warmer tone" lands exactly where you mean. With an image selected, Replace image opens a picker — swap in an image already used in the module or elsewhere in your organization, or upload a new file.

How an edit is applied

Each request becomes a set of concrete, validated operations:

1. Vidext interprets your instruction into structured changes against the draft.
2. Changes are validated against the content schema — an edit can never produce a broken module.
3. Affected media (narration, audio) is regenerated for the touched scenes; presenter video re-renders after you publish the draft.
4. The previous draft state is backed up before it is replaced; an audit trail records what changed. The published version is untouched until you publish.

One edit is committed at a time per module, so concurrent requests cannot trample each other. To take an edit back, use the standard undo and redo shortcuts (Cmd/Ctrl+Z and Cmd/Ctrl+Shift+Z) — they step the module's edit history back and forward.

Preview before publishing

Two checks sit between an edit and learners. Ask for a dry run to see what an instruction would change — scenes affected, a summary of the diff — before it is applied; useful when the instruction is broad ("simplify chapter two"). Once edits are on the draft, hit Preview to watch the draft in the real learner player, then Publish when it's right.

When to rebuild instead

Chat editing is for content-level changes. If the instructional plan is wrong — wrong scope, wrong structure, wrong objectives — ask Vidext to rebuild the module from the new direction. It creates a fresh internal plan and shows the replacement draft directly. Rule of thumb: if you would describe the change as "what it teaches" rather than "how a scene reads," rebuild.