# Types Of Hubs
{% tabs %}
{% tab title="Playlist" %}
Sequential content presented in a specific order, guiding prospects through a curated journey.
**Best for:**
* Post-call follow-ups with materials discussed on your sales call
* Sales leave-behinds with a narrative arc (problem → solution → proof → next steps)
* Champion enablement where you control the story they share internally
* Multi-stakeholder deals requiring organized content by role or use case
**How it works:**
* Content appears in a left sidebar menu with a logical sequence
* Prospects progress through materials in the order you define
* Main viewing area displays selected content
* Works best with 5-10 pieces of content with clear progression
**When to use Playlist:**
* Sales teams sending post-discovery materials
* Deals requiring specific narrative flow
* Champion enablement scenarios
* Any situation where content order matters
{% endtab %}
{% tab title="Gallery" %}
A thumbnail grid layout where prospects browse and choose their own exploration path.
**Best for:**
* Website embedding on product, solutions, or resource pages
* Self-service content discovery where prospects control their journey
* Marketing campaigns requiring broad accessibility
* Top-of-funnel content where visitors need flexibility to explore
**How it works:**
* All content displays as thumbnail cards in a grid
* Prospects click any card to view that content
* No prescribed order—prospects explore based on interest
* Best with 6-12 pieces of content organized into clear sections
**When to use Gallery:**
* Marketing teams embedding on websites
* Trade show follow-ups where prospects scan multiple resources
* Self-qualification scenarios where prospects choose relevant content
* Any situation requiring ungated, browse-friendly experiences
{% endtab %}
{% endtabs %}
{% hint style="info" %}
**Pro tip:** Most sales teams default to Playlist for controlled storytelling. Marketing teams typically choose Gallery for self-service exploration.
{% endhint %}
---
# Agent Instructions: 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/types-of-hubs.md?ask=
```
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.