CEPD · Module 3 — Content-layout mastery
The fidelity ladder, written versus visual, screen fields, the SME review pack and two-cycle scope control.
About 26 min
Practice in the lesson player
Sorting, matching, quizzes, and the module gate stay behind a free account so scored answers are not public. The teaching notes below are the same cited curriculum.
01
A development-ready storyboard tells builders what to build, SMEs what to approve and QC what to reject, screen by screen. If a row cannot be built without three clarifying questions, it is still an outline.
02
Outline: Actions, evidence and sequence only. No visual design, no copy polish.
Written storyboard: Every screen: on-screen text, narration, interaction, feedback and next logic.
Visual storyboard: Layout sketches where spatial layout, RTL or avatar blocking matters.
Build: Only after SME sign-off on the written (or visual) pack.
03
Written is enough when: Text, quiz, process or sort with clear fields. · SMEs need to approve wording and preferred paths.
Add visual when: Labelled graphic, hotspots or complex RTL layout. · Avatar or dialogue staging must be seen to be judged.
04
Field | Must answer
Screen ID and layout | Which pattern, and why for this action?
On-screen copy (EN and AR) | Final learner-facing text, not "bullets to follow"
Interaction and success rule | What the learner does; what counts as correct or preferred
Feedback | Names the gap; no sarcasm; next step clear
Media and accessibility notes | Alt text intent, captions, focus order, RTL notes
Assets and owner | Who supplies image, narration or legal citation, and by when
05
Goal and actions — One page: the business metric and the three to five actions this module rehearses.
Storyboard rows — Fields filled; preferred path highlighted; open questions listed separately.
Assessment map excerpt — Which screens produce evidence for the gate, so SMEs do not add a quiz at random.
Review rules — Cycle 1: accuracy and preferred paths. Cycle 2: wording only. New topics are a change request.
06
Unlimited SME revisions break SAM. Contract two review cycles before build: accuracy and preferred paths, then wording. Anything that adds screens, objectives or branches after cycle 2 is a change request, not one more pass.
07
Single-column storyboards with the Arabic pasted below the English hide problems until build. Use side-by-side columns (English, Arabic) per field, so reviewers see both at once and translators can see context. Add a column for "differs by language" where the scene, example or name was transcreated. Store copy as text, not inside screenshots, so it can be reused, checked against the termbase and imported. Lock the English only after the Arabic reviewer has seen it, because Arabic review often finds ambiguities in the source.
08
Write a development-ready storyboard for one lesson of your course in the two-language template, and assemble the SME review pack. This is your module artifact. Variety is not a quality measure: if a screen's layout serves no action, cut it.