LaperDocs

Navigate the workspace and episodes

Learn the three-column project shell, dimension navigation, episode scope, and local viewing behavior.

Read the workspace from left to right

A project uses a consistent editor shell:

  • The narrow navigation rail switches dimensions such as Script, Outline, Characters, Storyboard, or Assets.
  • The project panel contains the project title, episode list, project actions, and dimension-specific controls.
  • The central area displays the current editor, board, table, or canvas.
  • The AI panel floats above the workspace and can be moved or resized without becoming part of the document.

Some dimensions offer more than one view. Characters can use a board, network, or casting table; scenes can use a canvas or table; assets can use a generation canvas or task list. Changing a view changes presentation, not the underlying entity.

Know what changes with an episode

In Script projects, screenplay text, outline, beats, scenes, and shots are episode-specific. Characters, locations, props, worldview, knowledge files, and advisors stay shared across the project. In Cinema, reels are episode-specific while characters, props, production settings, and tasks are project-level.

When you switch episodes, only your own local route and document binding change. A collaborator can stay in episode 1 while you work in episode 4. This prevents routine navigation from dragging the whole room around.

Create, rename, and remove episodes carefully

Use the episode controls in the project panel. A newly created episode becomes your active episode and opens at a predictable primary dimension. Renaming changes the shared episode label. Removing an episode affects its episode-level screenplay or reels, so confirm the target and preserve a history version before destructive restructuring.

Understand connection indicators

Presence and connection indicators distinguish synchronized collaboration from local editing. Temporary disconnection does not create a second project; edits can remain in the local document layer and synchronize when the connection recovers. Avoid opening duplicate tabs to “force” a save. Let the connection state settle, and use history or export for explicit checkpoints.