> For the complete documentation index, see [llms.txt](https://docs.storylane.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.storylane.io/hubs-docs/creating-hubs/sectional-layouts.md).

# Sectional Layouts

<figure><img src="/files/kO9Is53zyEDKZs9tLVuY" alt=""><figcaption></figcaption></figure>

**Single section**: All content in one unified section without categories. Use for simple showcases with 3-10 related pieces (post-call follow-ups, focused demos). Maximum 12 pieces of content.

**Multi-section**: Content organized into named sections. Use for complex deals serving different stakeholders or multiple products. Each section holds up to 3 pieces of content. Maximum 10 sections.

**Example Multi-section structures**:

* By persona: "For CFO" + "For CTO" + "For End Users"
* By journey: "Getting Started" + "Core Features" + "Next Steps"
* By product: "Platform Overview" + "Analytics" + "Integrations"


---

# 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:

```
GET https://docs.storylane.io/hubs-docs/creating-hubs/sectional-layouts.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.