When you write mood: confident in a Workshop script, the compiler makes roughly 50 design decisions on your behalf. Background color. Text color. Accent color. Font family. Letter spacing. Line height. Entrance animation. Entrance duration. Exit duration. Spring mass. Spring tension. Spring friction. Transition type. Transition duration. Beat length. Hold multiplier. Spacing scale. Camera movement. Corner radius. Shape opacity. And more.
These decisions are not independent. A bouncy entrance animation demands a warm palette. Cinematic timing demands deliberate typography. Fast-paced urgency demands high-contrast colors and tight spacing. Getting any single parameter wrong breaks the coherence of the entire system.
Mood solves this by treating visual identity as a coordinated system rather than a collection of individual settings. You choose the emotional register of your content. The compiler handles the interdependencies.
Six Moods, 30 Identities
Workshop ships six core moods: calm, confident, dramatic, elegant, playful, and urgent. Each has five variants that shift palette shades and typographic weight while preserving the mood's fundamental character.
The same product launch script rendered across all six moods produces six completely different visual experiences — each internally consistent, each appropriate for a different audience and context. Confident for a SaaS demo. Dramatic for a keynote opener. Playful for a social clip. Urgent for a flash sale.
The compiler picks a variant deterministically based on a hash of the script content. Different scripts get different variants automatically, providing visual diversity across a body of work without any randomness. The same script always gets the same variant.
Composition
The + operator lets you combine two moods. The first mood contributes kinetics — how things move, how fast they appear, how springs behave. The second contributes surface — what things look like, what colors and fonts are used.
mood: confident + elegant gives you the structured, medium-energy motion of confident with the deep indigo, gold, and DM Sans surface of elegant. The result is a visual identity that neither mood produces alone.
A compatibility matrix classifies every mood pair as coherent, tension, or conflict. Coherent pairs reinforce each other. Tension pairs create interesting contrast. Conflict pairs may produce awkward results — the compiler warns you, but does not prevent it.
Why Spring Physics
Most animation systems use easing curves — cubic beziers that map time to progress. Workshop uses spring physics instead. Each mood defines spring parameters: mass, tension, friction, and damping.
Springs feel physical. A heavy element enters slowly and settles deliberately (dramatic). A light element bounces in and overshoots before settling (playful). A tightly damped element slides in smoothly with no oscillation (elegant). These behaviors emerge naturally from the physics parameters rather than being hand-tuned per animation.
The same entrance — enter: pop — feels different in every mood because the spring parameters change. In playful, it bounces. In elegant, it eases to a stop. In urgent, it snaps. The author does not need to know about springs. The mood handles it.
Mood as API
For platform integrators, mood is the highest-leverage API parameter. A single string in a compile request controls the entire visual output. This means you can offer your users a mood picker — six options — and each selection produces a professional, internally consistent video without any design knowledge.
No color picker, no font selector, no timing controls. One dropdown. Six options. Thirty visual identities.
Next Steps
Explore the Moods Reference for specific values per mood. Read the Mood System architecture for the technical deep-dive. Try different moods in the Quickstart — change one word and see the entire video transform.