How Irakasi works
The ideas behind the editor: why it works the way it does and how its parts fit together.
These pages explain the ideas behind Irakasi, why the editor works the way it does, and how its parts fit together:
- Understand the core model: see how boards, versions, shapes, cameras, and timeline animations connect to one another.
- Learn the reasons behind the design: read why boards live in your browser, why animations are built from blocks on a timeline, and how the Player runs live boards.
- Choose the right approach: compare related tools and features so you know which ones fit what you are building.
Note
The first explanations are being prepared and will appear here as they are ready.
Topics covered here
Each article focuses on one part of how Irakasi is designed:
- Boards, storage, and versions: how local boards and their files are stored in your browser, and how Versions keep translations or alternate layouts inside the same board.
- Board space, cameras, and modes: how an open board combines free spatial arrangement with framed camera views across Design, Animation, and Player modes.
- Timeline and animation model: how animation sequences, blocks, pauses, and easing work together so you can move or restyle shapes while keeping their animations intact.
When to read these pages
Choose the section of the documentation that fits what you need:
- Understanding a concept in depth: read these pages when you want the reasoning behind a feature or a mental model of how the editor works.
- Looking up a tool or setting: see the Reference when you want to check a specific control, shape, or animation block.
- Practicing or following a full project: take a Guided tour for step-by-step practice inside the editor, or see Project walkthroughs to follow a complete project from start to finish.