> For the complete documentation index, see [llms.txt](https://docs.betterbuilding.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.betterbuilding.io/user-guide/2d-building/drawing/add-zones.md).
# Add Zones
A zone is a thermal space that can be air-conditioned, heated or left unconditioned. It’s drawn to the required size and always shares the same height as other zones on the same drawing.
## Add a Zone
Click on the 'Add Zones' symbol to get started, then head back to the drawing space to define your zone by drawing one wall at a time. Before you close the zone, press 'Enter' on your keyboard, give your zone a 'Title', and click 'Set'.
When working with multiple zones, make sure each zone node connects to the adjacent ones. You can use up to 60 nodes per zone. To draw long, straight lines, hold down 'Shift' to lock the direction to the X or Y axis.
## Adjacent Zones
Once you've drawn a zone, you’ll often need to add another one next to it. Start by selecting the first zone, then hold down 'Shift' on your keyboard. A square will appear, letting you snap to a point on the edge and drop a node.
Drag the node into position where the new zone will connect. To keep the movement aligned, hold 'Shift' again to lock the direction to the X or Y axis as you drag. Once the node is in place, click the 'Draw Zones' symbol in the ribbon and sketch out the second zone so it connects seamlessly to the first.
---
# 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://docs.betterbuilding.io/user-guide/2d-building/drawing/add-zones.md?ask=&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.
