Project guide

Project Workspace Reference

7.1 Project Overview

Purpose: The project home and current-state summary.

Project Overview can show:

• project name, icon, type, description, and status;
• project phase and progress;
• engine, platform, genre, team size, or discipline-specific equivalents;
• technology, tools, gear, or materials;
• the next event;
• issues, tasks, and assets summary;
• recent activity;
• recent issues;
• starter checklist;
• output tracking where supported;
• linked social campaign or creative project relationships.

The starter checklist can be completed directly on Overview and points into the appropriate Library, Workshop, or Chronicle destination.

7.2 Library

Purpose: The project’s written memory.

Library has three modes:

Project Wiki

For structured and durable documentation:

• categories;
• nested pages;
• page icons;
• cover treatments;
• reorderable navigation;
• Markdown or visual editing;
• heading-based table of contents;
• search;
• read and edit modes.

Good uses:

• game design documents;
• story bibles;
• character profiles;
• production briefs;
• campaign strategy;
• system documentation;
• research;
• lore;
• technical decisions;
• release plans.

Current-label note: The project sidebar calls this area Library, while the current Library tab may display Studio Wiki. The underlying content is still project-scoped. Public documentation should prefer Project Wiki or Library documents until the in-app naming is unified, and should always point out the exact visible label when giving click-by-click instructions.

Writing Studio

For focused long-form writing:

• document creation;
• creator-aware document templates;
• document search;
• word-oriented writing workflows;
• output logging;
• Writing Studio documents kept inside the project.

Templates can adapt to the project type. Examples include:

• Chapter
• Scene
• Outline
• Draft Notes
• Arc Outline
• Release Notes

Quick Notes

For raw ideas, fragments, references, and reminders:

• fast capture;
• creator-aware prompt chips;
• search;
• pinning;
• lifecycle status;
• promotion to Moodboards, Workshop, or docs.

7.3 Workshop

Purpose: Turn ideas into sequenced, visible work.

Workshop provides:

• Kanban Board view;
• List View;
• drag-and-drop status movement;
• searching and filtering;
• task creation and editing;
• priorities;
• due dates;
• tags;
• recurring work.

Recurring schedules currently supported:

• Daily
• Weekdays
• Weekly
• Monthly

Completing a recurring task generates its next occurrence.

7.4 Moodboards

Purpose: Visual shaping and creative direction.

Capabilities include:

• multiple Moodboards per project;
• creator-aware board presets;
• freely positioned cards;
• drag and resize;
• card layering;
• board switching;
• search and management;
• asset and upload-based images;
• promotion into tasks or docs.

Card types:

• Image
• Text
• Link
• Note
• Concept

Example board purposes:

• mood and tone;
• character references;
• scene direction;
• album era;
• launch direction;
• thumbnail exploration;
• UI/UX inspiration;
• general concept clustering.

Important distinction: The shipped Moodboards experience is the board-and-card workspace. It should not be documented as a freehand Excalidraw canvas.

7.5 Assets

Purpose: Keep the project’s source material close to its thinking and execution.

Capabilities include:

• app-managed file storage;
• folders and subfolders;
• file upload;
• search;
• file-type filtering;
• grid and list views;
• preview;
• tags;
• image, audio, video, PDF, model, and other file categories;
• sending useful assets into Moodboards.

Local-first note: Media selected by the user is copied or referenced through app-managed local storage appropriate to the desktop application.

7.6 Chronicle

Purpose: Show the project as a story across time.

Chronicle combines:

• changelog entries;
• project events;
• task deadlines;
• creator output logs.

Views:

• Full Timeline — past and future together
• Upcoming — future events and deadlines
• History — past releases and completed movement
• Calendar — month view

Chronicle can visually distinguish:

• milestones;
• releases;
• meetings;
• deadlines;
• shoots;
• recording sessions;
• design work;
• fixes;
• features;
• improvements;
• drafts;
• chapters;
• output sessions.

7.7 Project Badges

Purpose: Show achievements relevant to the selected project’s discipline.

Expanded project types map to compatible badge families. This avoids showing a creator a completely unrelated achievement set.

Examples:

• games use game-development achievements;
• books and serialized fiction use writing achievements;
• films, television, screenplays, theater, and photography can inherit relevant film/video families;
• apps, websites, software, and design systems can inherit software achievements;
• podcasts, music, and some publications can inherit audio or content families.

7.8 Project Settings

Purpose: Configure the project rather than the entire application.

Settings include:

• project name;
• short name;
• description;
• status;
• accent color;
• project icon or custom image;
• progress phase;
• project-type-specific engine or stage;
• genre, category, focus, or discipline;
• team size;
• target release;
• target audience;
• platform or distribution choices;
• technology, tools, equipment, partners, or materials;
• project icon-set preferences;
• read-only project statistics;
• project deletion.

Project statuses:

• Active
• Paused
• Completed
• Archived at the data-model level

Project Types and Discipline Adaptation

KazaKit currently supports 21 project types.

The core information architecture stays consistent, but terminology, starter material, progress phases, prompts, board presets, settings, badges, and some output metrics adapt to the discipline.

Progress Phases

Progress uses six stable percentage bands:

• 0%
• 20%
• 40%
• 60%
• 80%
• 100%

The label for each band changes by project type.

Examples:

• Game: About to Start → Gaining Momentum → Core Build → Feature Complete → Polish & Ship Prep → Shipped
• Movie: Development → Pre-production → Production → Post-production → Distribution Prep → Released
• Book: Outlining → First Draft → Deep in Draft → Revisions → Edit & Proof → Published
• Music: Writing Sketches → Tracks Forming → Recording → Mix & Master → Art & Rollout → Out Now
• App: Kickoff → Foundations → Core Features → Beta Ready → Store Prep → Released
• Comic: Script & Thumbnails → Pages Underway → Halfway Art → Finishing Pages → Letters & Export → Published
• Creative Project: Gathering Ideas → Exploring → Taking Shape → Deep Work → Refining → Complete

Creator Families

Some creator-aware prompts, board presets, and badge compatibility operate through broader families:

• Game
• Book and writing
• Film
• Music
• Video
• Product and software
• Podcast
• Comic
• Generic creative work

This lets related project types receive useful defaults without pretending that every discipline has an entirely separate application.