Loading...
Understanding the why behind the what.
Whiteboards in Kora are structured canvases for planning, creative direction, and reflection—connected directly to albums and projects. Unlike generic notes apps, Whiteboards preserve context, link to real work, and persist across the entire project lifecycle. They're where strategy becomes structure.
Most creators use notes apps (Apple Notes, Notion, Evernote) to capture ideas, briefs, and creative direction. But notes apps have a fatal flaw: **they don't connect to the work itself**.
**Scenario:** You write a detailed creative brief for an album in Notion. Two months later, you're deep in production and can't remember where you saved the brief. You search for 10 minutes, find it, read it, then switch back to your DAW. Context is lost.
**The problem:** Notes live in a separate app, disconnected from your project files, tasks, and delivery state. You have to **remember** to check them—and remember where they are.
Whiteboards solve this by **embedding planning directly into your project**. The brief, the reference tracks, the creative direction—they live **inside** the album, not in a separate app.
Whiteboards are **structured canvases** that live inside Kora albums. They support:
**Text blocks:** Write briefs, creative direction, or post-mortem reflections.
**Reference links:** Embed Spotify tracks, YouTube videos, or mood boards directly in the Whiteboard.
**Task connections:** Link Whiteboard sections to specific tasks or tracks, so planning flows into execution.
**Templates:** Use pre-built templates for album planning, weekly reviews, or post-project reflections.
Whiteboards are **persistent**—they stay with the album from planning through delivery. You don't have to search for them. They're always there.
Notion and Apple Notes are great for **general-purpose note-taking**. Whiteboards are purpose-built for **music project planning**:
**Notion:** Requires manual linking, custom databases, and constant maintenance. Great for flexibility, exhausting for consistency.
**Apple Notes:** Fast and simple, but no structure. Notes pile up, and you lose context over time.
**Whiteboards:** Automatically connected to albums, tasks, and delivery state. No manual linking required. Structure is built-in, not bolted on.
Whiteboards are **opinionated**—they assume you're planning albums, not writing grocery lists. This constraint is a feature, not a limitation.
Whiteboards are for creators who need to **preserve context** across long projects:
**Composers:** Capturing director notes, creative direction, and reference tracks for film/game scores.
**Producers:** Planning album concepts, tracking artist feedback, and documenting production decisions.
**Sound designers:** Organizing sound palettes, reference assets, and client briefs for library work.
**Anyone managing multiple projects:** Whiteboards prevent context loss when switching between albums or clients.
If you've ever thought 'What was I trying to do here?' two months into a project, Whiteboards solve that problem.
Implementation notes, middleware documentation, and adaptive music planning connected to audio files.
Director feedback, cue notes, and creative direction preserved alongside scoring projects.
Creative direction, collaborator notes, and release planning embedded in album workflows.
Production notes, artist feedback, and project planning connected to production timelines.