> For the complete documentation index, see [llms.txt](https://community.threekit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community.threekit.com/platform-documentation/catalog-2.0-docs/project-data/assets/nodes/layout-containers.md).

# Layout Containers

**Modular and spatial configurator** physical constraints can now be setup easily in platform using new **Layout Container** nodes to build Room Builder like interactions in the Threekit Player:

* Item Selection and highlighting
* Item positioning/dragging
* Positioning constraints

![](https://content.gitbook.com/content/efQOUWnh8WUpteoAKY9N/blobs/RipHk6TVkbJF5yCGubQs/LayoutContainer_1.gif)

Layout Container nodes control for movement constraints, selectability of elements, and outline styling.

**Layout Container Node**

Layout Container nodes can be added in the scene using the new toolbar icon or the right-click menu in the Scene Tree:

![](https://content.gitbook.com/content/efQOUWnh8WUpteoAKY9N/blobs/qt7SJm1Af48bNZ4nDYo5/LayoutContainer_2.png)

<img src="https://content.gitbook.com/content/efQOUWnh8WUpteoAKY9N/blobs/bVzpOlNdsHxyh4en23Ji/LayoutContainer_3.png" alt="" width="443">

To enable dragging, use the **Container Meshes reference** field to reference existing node(s) within he asset to act as dragging constraints. In this example, there is a Plane node representing a floor so that elements cannot be moved beyond it:

<img src="https://content.gitbook.com/content/efQOUWnh8WUpteoAKY9N/blobs/6nEa273hKv2ZmvRLDkAq/LayoutContainer_4.png" alt="" width="551">

**Selection color & thickness**

Layout Containers contain overrides for the default Selection Highlight Color and Outline Thickness as Operators in the Selection section:

<img src="https://content.gitbook.com/content/efQOUWnh8WUpteoAKY9N/blobs/j9K8b5DVGkn58mbriIAy/LayoutContainer_5.png" alt="" width="531">

<img src="https://content.gitbook.com/content/efQOUWnh8WUpteoAKY9N/blobs/Qn5lOtxtHTq4iWwX7NL6/LayoutContainer_6.png" alt="" width="528">

Then, models can be imported into the asset and made children of the Layout Container in order to be constrained to the Floor Plane:

<img src="https://content.gitbook.com/content/efQOUWnh8WUpteoAKY9N/blobs/subvCV2cI6rngSxHfkKb/LayoutContainer_7.png" alt="" width="447">

In the example above, there are multiple Layout Container nodes to produce Floor and Wall constraints.&#x20;

**Props & immovable objects**

Props, or unselectable/immovable, elements can be added to the asset simply by placing the outside of layout containers.&#x20;

#### Selectable components

Want to make components of a product selectable in the Player? Layout Container nodes can also be used to make children nodes selectable without any movement. Simply leave the **Container Meshes** reference blank and all children will still be selectable in the player.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://community.threekit.com/platform-documentation/catalog-2.0-docs/project-data/assets/nodes/layout-containers.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
