Workspace guides
Studio guide
Studio Workspace Reference
6.1 Studio Overview
Purpose: The command center for all projects.
The Studio Overview contains or summarizes:
- active project count;
- open issue count;
- work in progress;
- high-priority work;
- project cards and progress;
- recent activity;
- notifications;
- focus-time progress;
- current work streak;
- weekly, monthly, and all-time focus statistics;
- activity contribution heatmap;
- productivity insights;
- project progress;
- issue overview;
- badges earned;
- today’s events;
- task deadline summary;
- output snapshot;
- goals;
- upcoming milestones;
- high-priority issues.
Primary user question: “What is happening across my studio?”
Wiki guidance: Explain this as an orientation screen, not the place where every item is edited.
6.2 Today
Purpose: A forward-looking view of what deserves attention now.
Today aggregates:
- overdue work;
- work due today;
- work already in progress;
- work due this week;
- upcoming milestones;
- creator output logged today and this week;
- daily or weekly goals.
Its intended decision order is:
- triage overdue work;
- finish what is due today;
- resume something already in progress;
- look ahead at the next few dates;
- review output and goals.
Key principle: Today becomes more useful as tasks and milestones receive real dates.
6.3 All Issues
Purpose: Cross-project issue and problem tracking.
Capabilities include:
- search;
- severity filtering;
- status filtering;
- issue creation;
- issue detail views;
- cross-project aggregation.
Issue severities:
- Low
- Medium
- High
- Critical
Issue statuses:
- Open
- In Progress
- Blocked
- Resolved
- Closed
An issue can also contain richer fields such as:
- type;
- impact;
- technical details;
- steps to resolve;
- time estimate;
- assignee.
Terminology note: Some project types adapt “issues” to more creator-appropriate language such as Feedback, Script Notes, Production Notes, Reader Notes, or Design Debt.
6.4 Activity
Purpose: A cross-project record of recent movement.
Activity can represent changes associated with:
- issues;
- tasks;
- assets;
- wiki documents;
- builds;
- commits or release movement.
Common actions include:
- created;
- updated;
- closed;
- deleted;
- uploaded;
- pushed.
Primary user question: “What changed since I last looked?”
6.5 Global Calendar
Purpose: The complete Studio timeline.
Capabilities include:
- Month view
- Week view
- Day view
- event creation;
- event editing;
- project and studio-wide events;
- recurring events;
- milestones;
- task due dates.
Events may represent:
- milestones;
- deadlines;
- meetings;
- releases or publishing targets;
- shoots;
- recording sessions;
- reviews;
- rehearsals;
- recurring production checkpoints.
6.6 Studio Docs
Purpose: Shared, studio-wide knowledge.
Studio Docs are for material that belongs above any one project:
- studio standards;
- reusable processes;
- shared references;
- operational notes;
- brand principles;
- long-term studio documentation.
Studio Docs are different from:
- built-in Help, which explains KazaKit;
- Project Library documents, which belong to one project;
- Quick Notes, which are intentionally rough and temporary.
6.7 Trophy Room
Purpose: Make progress and habits emotionally visible.
The achievement system supports:
- earned and locked filters;
- progress toward the next badge;
- Common, Uncommon, Rare, Epic, and Legendary rarity tiers;
- studio-wide achievements;
- project-type-compatible achievements.
Badge categories currently cover:
- Bug Hunting
- Progress
- Documentation
- Work Habits
- Time and Streaks
- Game Development
- Film and Video
- Comics and Manga
- Music and Audio
- Content Creation
- Software
- Writing
- Planning and Organization
- Special achievements
The current application displays 72 total badge slots.
Documentation rule: Do not promise that every conceivable user action has a badge. Explain the system as a set of milestones, streaks, habits, and discipline-specific accomplishments.