> ## Documentation Index
> Fetch the complete documentation index at: https://docs.inklyai.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Hubs and demos

> Understand how Inkly organizes your product demos into hosted hubs and individual interactive stories.

Inkly organizes product demos around two concepts: **hubs** and **demos**.

A **hub** is the home for a collection of demos. It is the page you share with prospects, customers, new users, internal teams, or support recipients. A **demo** is one focused interactive story inside that hub.

Together, they make demos a living product surface instead of one-off recordings.

<CardGroup cols={2}>
  <Card title="Hub" icon="folder" href="#hub">
    A public demo home for a product, feature area, use case, audience, or team.
  </Card>

  <Card title="Demo" icon="play" href="#demo">
    One interactive walkthrough that explains a flow, feature, or customer story.
  </Card>
</CardGroup>

## Hub

A hub is the place where your audience discovers demos. You can use one hub for your whole product, or create focused hubs for sales, onboarding, customer education, support, or launches.

For example, a product hub might include demos for onboarding, analytics, integrations, admin setup, and billing. A sales hub might group demos by industry, persona, or deal stage.

The hub gives those demos shared navigation, branding, theme, analytics, publishing settings, and a hosted URL. When you connect a GitHub-backed hub, your repo stays the source of truth and Inkly keeps the hosted hub updated from those files.

## Demo

A demo is one guided product story inside a hub. It should have a clear job: explain one workflow, show one feature, answer one buyer question, or help one user complete one task.

Demos can be captured by an AI agent with the CLI, recorded by a human with the Chrome extension, edited in the no-code editor, or maintained directly as files. Because the demo lives in the hub, you can reuse it across pages, embed it in another site, personalize it for an audience, and update it when the product changes.

Good demos are focused. Instead of recording everything your product can do, create several small demos that map to the questions your audience already has.

## How hubs and demos work together

A hub gives your demos a shared destination. Each demo gives one product story a focused path.

<Steps>
  <Step title="Create or connect a hub">
    Start with a demo home for a product, team, or audience.
  </Step>

  <Step title="Add focused demos">
    Capture or author one demo for each product story you want to tell.
  </Step>

  <Step title="Organize the experience">
    Group demos by use case, audience, feature area, or lifecycle stage.
  </Step>

  <Step title="Publish and keep it current">
    Share the hosted hub, embed demos elsewhere, and update the source as your product changes.
  </Step>
</Steps>

## Organizing demos

Collections help you shape the hub for the audience. A collection can group demos by product area, customer segment, lifecycle stage, or sales motion.

Common patterns include:

* **Getting started** for onboarding and setup flows.
* **Feature tours** for product education.
* **Use cases** for role-based or industry-specific stories.
* **Sales plays** for demos tailored to common buyer questions.
* **Support guides** for recurring customer workflows.

You can link one demo from multiple contexts, or personalize a copy for a specific prospect or customer.

## How this maps to your repository

Inkly keeps the product model file-backed. The hub is represented by `inkly.json`, and each demo is represented by one `demos/<slug>/demo.config.json` file.

That structure matters because it makes demos readable by people and AI agents. A human can use the no-code editor. An agent can use the same source files to update copy, replace assets, customize a demo, or keep it aligned with a product release.

<Note>
  You do not need to manage every file by hand. Inkly can create hubs, capture demos, edit through the platform, and publish the hosted experience. The repository remains the shared source of truth behind those workflows.
</Note>

## Visibility

Most demos are public because they are meant to be shared from the hub. You can also keep a demo private when it is a draft, an internal workflow, or a customer-specific experience.

Local preview still lets you review private demos before you publish them.

## Where to go next

<CardGroup cols={2}>
  <Card title="What is Inkly?" icon="sparkles" href="/what-is-inkly">
    See how hubs and demos fit into the full platform.
  </Card>

  <Card title="Quickstart" icon="rocket" href="/get-a-quick-start">
    Create your first demo with an agent or the Chrome extension.
  </Card>

  <Card title="Screenshot versus HTML demos" icon="camera" href="/concepts/screenshot-vs-html-demos">
    Choose the right capture format.
  </Card>
</CardGroup>