You are here. See how this question connects to other ideas.
Select a node to open its page · Expand to read within the map
One question
view: How do you group content?
view organizes child nodes and expresses their arrangement.
Group a task title, status and button in one view. Changing the arrangement can retain those node identities. A container does not automatically become a business object or grant access.
Start with these properties
layout arranges the children: row horizontally, column vertically, and grid in a grid. It changes how the content is placed, not the content itself. The example’s size.maxWidth limits the container width.
Read a structural example
From the source registry. This is structural reading material, not a live demo; referenced resources and actions require an application.
{
"id": "layout-1",
"type": "view",
"props": {
"layout": "row",
"size": {
"maxWidth": "800px"
}
},
"children": [
{
"id": "t1",
"type": "text",
"props": {
"content": "Left",
"level": 2
}
},
{
"id": "t2",
"type": "text",
"props": {
"content": "Right"
}
}
]
}Read the two children, t1 and t2, then their parent’s layout. Changing row to column changes arrangement; editing t1’s content changes the words.
Check your understanding
What primarily changes when a task card switches from a row to a column?
The child arrangement; task data and node identities need not change.