NS Design System
v3.0.0 · 257 tokens

159Video series & schedule

The publishing plan: what ships on which day, and the second-by-second template every video follows — hook, promise, sting, teaching, bridge.

The weekly cadence

MONYouTube lesson (7–12 min) — one concept from the current coursecourse thumbnail style · intro sting · end screen
WEDShort / Reel (under 60s) — the single best moment of Monday's lessonlesson thumbnail · hook caption card
FRIInstagram carousel or LinkedIn post — the lesson as 5 swipeable stepsinstagram post styles · social action icons
SUNCommunity touch — poll, Q&A, or next-week teaserstory style · promo card

One lesson feeds the whole week. Never create Wednesday's short from scratch — cut it from Monday's video. The system's thumbnail styles exist so a series is recognizable in the feed before the title is read.

The video template — every video, same skeleton

0–3sCold hook. The payoff shown or said first — the finished flow running, the exam passing, the error disappearing. No logo yet, no “hey guys.”raw screen recording, full bleed
3–10sThe promise. One sentence: what they will be able to DO by the end — “By the end of this you'll deploy your first Apex trigger.” Then the sting.logo sting (Preloader · flip, ~1.8s) + title lower-third
10–40sContext. Why this matters and where it sits in the roadmap — “this is lesson 03 of Apex Basics; last time we built X.” Show the roadmap, name the prerequisite.roadmap card · mono index 01/02/03 overlay
40s–The teaching. Numbered steps, one concept per step, said then shown then said again. Every step gets its mono index on screen — the numbering IS the structure.live screen + step lower-thirds · code panels for snippets
last 30sRecap + bridge. The three things they can now do, then the bridge to the next lesson — “next, we turn this data into insight.” One CTA only.recap card (3 mono-indexed lines) → end screen
end 10sEnd screen. Next lesson thumbnail + subscribe. Silence is fine; no outro music ramp.youtube end screen template

Hook line formulas — write three, keep the best

  • Payoff-first: “This is a working approval flow — built in eleven minutes, no code.”
  • Mistake-first: “Most admins set up validation rules exactly wrong. Here's the tell.”
  • Stakes-first: “This one topic is 12% of the exam — and it fits in one screen.”
  • Say the hook over the result, never over your face or a logo.
  • Numbers only when concrete (Principle: never decorative stats).
  • If the hook needs two sentences, the video is about two things — cut one.

Ending lines — the bridge, not a beg

  • “You can now ___, ___ and ___. Next, we ___.” — the recap IS the CTA.
  • One ask per video: next lesson OR subscribe OR the roadmap link. Never all three.
  • Last frame is always the end-screen template — muscle memory for the viewer.

Video Structure — First 60 Seconds

The hook/promise/credibility/roadmap formula, with a visual timeline

open ↗