Storyboard · shots 1.2

Brightdock: the deploy log your team can read

Duration
20s
Aspect
9:16
Framework
educational-demo
Run
2026-11-19T12:00:00Z

Series lock

Character
no people on screen; the product's own interface is the subject of every shot
Environment
Brightdock's dark interface on a near-black ground, one panel per shot in the lower two-thirds, the upper third left empty
Lighting
flat screen light, a faint lime glow at the top and bottom edges of the frame
Color grade
no grade: near-black #0B0D10, off-white #F4F5F0, one lime accent #C8F250; red and amber only as deploy status inside the product

Shots

shot_01: problem
Who shipped what, and when?
01 0–3.0s problem ACCEPTround 1
Framing
WS
Angle
eye-level
Motion
static
DOF
deep

Subject

a wall of raw deploy log lines in grey monospaced type filling the lower two-thirds, one line marked in red where a health check failed, the lines fading out at the top and bottom

On-screen text

"Who shipped what, and when?"

text_01 · display · upper-third · enter 0.2s (hard-cut) · exit 2.9s (hard-cut)

Rationale

The opening has to show the problem before it is named: nobody can read this. The one red line gives the eye a place to land, and the empty upper third is where the question goes.

shot_02: reveal
BrightdockEvery deploy on one page.
02 3.0–6.5s reveal ACCEPTround 1
Framing
MS
Angle
eye-level
Motion
static
DOF
deep

Subject

the Brightdock deploy list: a panel headed Deploys with six rows, each a deploy number, what it was, the service, who shipped it and when, a lime dot for live and one amber row that was rolled back

On-screen text

"Every deploy on one page."

text_02 · display · upper-third · enter 3.1s (hard-cut) · exit 6.4s (hard-cut)

Rationale

The cut from the log wall to one tidy list is the whole pitch, so the list arrives on the first hard cut and holds for three and a half seconds, long enough to read two rows.

shot_03: walk-through
Open one.See what changed.
03 6.5–10.0s walk-through ACCEPTround 1
Framing
CU
Angle
eye-level
Motion
static
DOF
deep

Subject

one deploy open: the number 214 set very large, the service name beside it, a lime live status, then three changes each with lines added and removed, and who merged it

On-screen text

"Open one. See what changed."

text_03 · display · upper-third · enter 6.6s (hard-cut) · exit 9.9s (hard-cut)

Rationale

Step one of the walk-through: open one deploy. The number is the largest thing in any frame of the film, so the viewer knows where they are without reading.

shot_04: walk-through
Roll back in one click.
04 10.0–13.5s walk-through ACCEPTround 1
Framing
CU
Angle
eye-level
Motion
static
DOF
deep

Subject

a deploy that failed its health check, marked with a red dot, a wide lime button to roll back to the deploy before it with a cursor on it, and under it a line with a tick saying the earlier deploy is live again

On-screen text

"Roll back in one click."

text_04 · display · upper-third · enter 10.1s (hard-cut) · exit 13.4s (hard-cut)

Rationale

Step two: the thing people buy it for. The button is the one lime element and fills the width of the panel, so the action reads at thumb size.

shot_05: walk-through
Your team hears first.
05 13.5–16.5s walk-through ACCEPTround 1
Framing
MS
Angle
eye-level
Motion
static
DOF
deep

Subject

three notices stacked and fading back: the newest says deploy 214 is live and who shipped it, the ones behind it say an earlier deploy was rolled back and another went live

On-screen text

"Your team hears first."

text_05 · display · upper-third · enter 13.6s (hard-cut) · exit 16.4s (hard-cut)

Rationale

Step three: the rest of the team. Three seconds is enough because the frame is one sentence repeated three times at falling contrast.

shot_06: result
The deploy log your team can read.
brightdock.example
06 16.5–20.0s result ACCEPTround 1
Framing
MS
Angle
eye-level
Motion
static
DOF
deep

Subject

the Brightdock mark, a lime rounded square with three dark bars, centred in the lower half with the product name under it on the near-black ground

On-screen text

"The deploy log your team can read."

text_06 · headline · upper-third · enter 16.7s (hard-cut) · exit 19.9s (hard-cut)

"brightdock.example"

text_07 · caption · lower-third · enter 17.4s (hard-cut) · exit 19.9s (hard-cut)

Rationale

The result is the product named in one line. The mark sits low so the line owns the upper third, and the address is a lockup so it does not compete with it.