> For the complete documentation index, see [llms.txt](https://helpdesk.smaply.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdesk.smaply.app/journey-maps/lanes.md).

# Lanes and columns

Lanes are the horizontal rows of a journey map. Columns are the vertical structure. Together they form the grid that cards snap to. Different lane types support different kinds of content: text for narrative, emotion chart for sentiment, grid for multi-row organisation, divider for visual separation.

#### Why use lanes and columns

* Structure a journey into clear rows and steps, so readers can scan across time and down dimensions
* Match each row to its content with dedicated lane types for narrative, sentiment, matrices, and visual separation

#### In this section

* [**Add and manage lanes**](/journey-maps/lanes/how-to-add-and-manage-lanes.md) - Create, rename, reorder, pin, duplicate, and delete lanes (text is the default lane type).
* [**Add and manage columns**](/journey-maps/lanes/how-to-add-and-manage-columns.md) - Add, remove, and reorganise the columns of a journey map.
* [**Emotion chart lanes**](/journey-maps/lanes/how-to-use-emotion-chart-lanes.md) - Visualise the emotional journey with a sentiment scale.
* [**Grid lanes**](/journey-maps/lanes/how-to-use-grid-lanes.md) - Multi-row lanes for tables, channels, or matrices.
* [**Flow lanes**](/journey-maps/lanes/how-to-use-flow-lanes.md) - Draw connector arrows between cards to map a process or blueprint.
* [**Divider lanes**](/journey-maps/lanes/how-to-use-divider-lanes.md) - Visual separators between sections of a journey.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://helpdesk.smaply.app/journey-maps/lanes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.