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

# Create an Experience

> Create a Jurni experience with AI, a template, a Figma reference, reusable sections, or a blank page, then connect real products and QA the commerce flow before publishing.

An **experience** is the main page-building object in Jurni. It contains the page structure, design, product interactions, and publishing configuration that shoppers ultimately see.

## Ways to start

Jurni supports several practical starting points depending on what you already have:

* **Generate with AI** when you have a product, audience, campaign angle, or brief and want Jurni to create the initial page.
* **Start from a template** when an existing page structure is close to what you need.
* **Build from scratch** when you want to assemble the page section by section.
* **Use a Figma reference** when your team already has a designed desktop/mobile page that Jurni should recreate.
* **Duplicate or reuse an existing experience/section** when the approved structure already exists in the same shop.

<Tip>
  Reuse approved sections—especially complex Buy Boxes—when they already exist. Rebuilding the same commerce logic from scratch creates unnecessary QA work.
</Tip>

## Generate with AI

When starting from AI, give Jurni the campaign context that should influence the page rather than only asking for a generic landing page.

Useful inputs include:

* product or offer
* audience/persona
* traffic source
* campaign or ad angle
* page type, such as advertorial, creator page, listicle, PDP-style page, or long-form sales page
* required sections
* brand constraints
* source URLs, screenshots, or Figma references when relevant

**Example:**

> Build a creator-led landing page for our protein powder. Traffic is coming from Meta ads focused on high-protein breakfast. Keep the product proof above the first Buy Box, use our existing review section, and make the mobile layout the priority.

After generation, treat the result as a draft: review every section, connect the real products, and QA the live commerce flow before publishing.

## Start from a template

Templates are useful when you want a known structure without starting from a blank page. Choose the closest page type, then replace the template's content and product configuration with the campaign-specific version.

Common page concepts in Jurni include:

* creator / UGC
* listicle
* advertorial
* long-form sales
* product-focused page
* video / VSL
* gifting or bundle page

Template availability can change as Jurni adds or updates patterns, so use the options visible in your workspace rather than relying on a fixed template list in documentation.

## Build from scratch

A blank experience gives you control over the section order and composition.

A typical workflow is:

<Steps>
  <Step title="Add the page structure">
    Use the Section Library to add the sections you need.
  </Step>

  <Step title="Connect real products early">
    Add the actual products, variants, Buy Boxes, subscription options, or bundle behavior before the design is considered finished.
  </Step>

  <Step title="Build desktop and mobile together">
    Check responsive behavior while you build instead of treating mobile as a final cleanup pass.
  </Step>

  <Step title="Add tracking and destination behavior">
    Confirm CTAs, cart/checkout behavior, integrations, and any external links.
  </Step>

  <Step title="QA and publish">
    Run the QA checklist, test the final live URL, then choose the appropriate publishing path.
  </Step>
</Steps>

## Name experiences for how the team will find them

Use a name that identifies the campaign or purpose rather than a generic label such as “Landing Page 2.” Examples:

* `Labor Day – Collagen PDP`
* `Meta – Creator Angle – Protein`
* `Black Friday – Bundle Page`

Clear names become especially important when the same experience is used in Smart Links or experiments.

## What to configure before launch

A page is not ready just because the layout looks finished. Verify:

* desktop and mobile design
* product and variant selection
* Buy Box actions
* selling plans/subscriptions
* bundle or offer rules
* cart and checkout behavior
* tracking pixels and Custom Scripts
* publishing destination
* Smart Link / experiment routing, when used

## Related guides

* Experience Editor
* Managing Sections
* AI Chat Prompts
* Figma
* Products & Buy Boxes
* QA Checklist
* Publishing Overview


## Related topics

- [Launch your first Jurni experience](/getting-started/step-by-step-setup.md)
- [Manage, duplicate, and archive experiences](/build/manage-experiences.md)
- [Start from the template Library](/build/template-library.md)
- [Strategy: Opportunities and Briefs](/strategy/roadmap.md)
- [How to Set Up the Jurni MCP Connector](/integrations/mcp-connector.md)