remo · documentation
RU

Frames and kanban: container versus grid

Two different placement models: an object inside a frame and a card inside a cell.

Status: available updated 2026-10-28

Two models

A frame and a kanban look similar — both group objects. But they are built differently, and this explains the different behaviour.

Frame Kanban
What sets the position object coordinates cell and order within it
Moves with the container yes the card moves only between cells
Can be taken outside yes, just drag it no: the card is always in a cell
Can be an end of a connector no a card — no
frame                              kanban
┌────────────────────┐             ┌─────────┬─────────┐
│   ●      ●         │             │  card   │  card   │
│          ●         │             ├─────────┼─────────┤
└────────────────────┘             │  card   │         │
                                   └─────────┴─────────┘
objects move with the frame        a card belongs to a cell

Frame

A frame is a container. An object whose centre lands inside the frame becomes part of it and moves with it; drag it outside and it lives separately again. If frames overlap, the object joins the smaller one. Frame bounds do not clip the object — it stays visible even if it has gone beyond the edge.

A frame is useful when there are several sections and each one is a finished thought: "Sprint", "Backlog", "Risks".

Kanban

A kanban is a grid: columns set the stage, swimlanes give an additional division (for example, by team). A card belongs to a cell; its position is determined by the order within the cell, not by coordinates.

That is why a card:

  • is not dragged across the free canvas;
  • can be an end of a connector; the line follows its cell;
  • is created by double-clicking a cell, not with an "add object" button.

Layers

Frames and kanbans lie below sticky notes and shapes, text is on top of everything. The order is set by the object type, not by what you dragged last: that way a caption does not end up accidentally under a sticky note.

Where to go next

Frames and kanban — the practical side and the limits.