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

# Content

> This is where you begin build your demo

## Welcome Page

Every demo opens with a Welcome Page. It is an optional title screen that greets viewers before they dive into your first feature.

* **Welcome Message —** The headline and intro copy viewers see first, before they start the demo. You can format the text, add links, or lists. If "Use Welcome text for Search Summary" is turned on (in Demo Settings), this same text also doubles as the summary shown for this demo in search results — so keep it clear and self-contained if you plan to enable that.

* **Show Welcome Message options —** Toggle ON to make the page visible to end-users.

* **Background Image —** Here is where you add an image for the page. If "Make image the full background" is ON, the image covers the full page background (specs: 1920 x 1700px); if OFF, it shows as a banner instead (specs: 1920 x 380px).

* **Alternate Mobile Image —** If you want to use a different image for your mobile demo than what is set for your background image, you can apply that here. *Specs: 1120 x 610px*

***

## Features

Demo content is organized into Features — what we refer to as **chapters** of your demo. Each feature is made up of one or more Steps a viewer moves through.

* **Feature Title —** This acts as the name of this chapter, shown in the feature navigation. Required — it also sets the feature's URL slug automatically.
* **Feature Description —** This is a description of the feature the user will be walking through — it sits above the feature's steps.
* **Show on first step only —** Toggle ON to show the Feature Description only on this feature's first step, instead of on every step.
* **Hide description in full screen mode —** Toggle ON to hide the Feature Description while the viewer has the demo maximized.
* **Select Feature Icon —** Here is where you choose a Material icon or emoji — and its color — to represent this feature in the nav.

### **Feature Actions**

* **Show Feature —** show or hide the feature from viewers without deleting it.
* **Delete Feature —** Shown as a trash icon, tooltip "Delete Feature"
* **Duplicate Feature —** Shown as a copy icon, tooltip "Duplicate Feature"
* **Open at feature —** opens that feature's live page in a new tab. Shown as an external-link icon, tooltip "Open at feature"

> [!NOTE]
>
> Unlike Welcome/Completion, Features don't have a background-image field — just the icon picker — so there's no "Background Image" / "Alternate Mobile Image" entry here.

***

## Steps

Steps are the individual parts that build out a Feature — the steps a user moves through, one at a time, to complete that chapter of the demo.

**Every step consists of two parts:**

* **Step Options —** Settings shared by every step, whether it's a Single Step or a Timeline Step — choosing the media type, whether it has a header/footer, and controlling how it transitions from this step to the next step.
* **The step's content —** Choosing what media to upload, adding step instructions, alt text for accessibility, a hotspot, or keyframes (timeline steps only).

### **Step Actions**

* **Delete Step**
* **Duplicate —** duplicates below current step
* **Duplicate to end —** adds a copy at the end of the feature instead of right after the original. Shows a tooltip "Duplicate to end"
* **Change to other step type —** If your step is a single frame step, it will say "Change to Timeline". If a Timeline step, it will say "Change to single frame".
* **Deselect All —** If you have a single step or multiple steps selected, you can deselect all of them at once using this option.

***

## Step Options

These are the settings shared by every step, whether it's a Single Step or a Timeline Step.

* **Media Type —** Selecting between having one static screen in your step (single step) or a scrubbable video or image sequence (timeline step)
* **Add Header & Footer —** Toggle ON for the option to add a header and/or footer image to this step from the "Add Media" button.
* **Transition Out —** Choose how this step animates away when moving to the next one: None, Dissolve, Slide (Up/Down/Left/Right), or Push (Up/Down/Left/Right).
* **Easing —** Choose the animation curve for the transition: None, Ease Out, or Ease In.
* **Duration —** How long the transition takes, from 0.2 to 1 second.

***

## Single-frame Step Content

A Single Step is the default step type — one static screen in your demo. Use it for any part of the walkthrough that doesn't need motion: this will include a screenshot with a hotspot and instructions guiding the viewer through what to do next.

* **Header —** Add an image that appears above the step's main content. This is usually a top-level navigation item like a hamburger menu or anything you want to live above your main content. *Specs: Desktop 1280px, Mobile 750px, Tablet 888px, Watch 476px.*
* **Footer —** Add an image that appears below the step's main content. Usually a bottom-level navigation item with your apps pages, quick actions, or a more menu. *Specs: same as Header.*
* **Main Image —** Add the screenshot or image for this step based on the device type you selected in the demo settings. *Specs vary by device: 1280 x 800px for Desktop, 750 x 1624px for Mobile, 888 x 1166px for Tablet, 476 x 832px for Watch.*
* **Step Instructions —** The main instructional copy shown to viewers for this step. You can format the text, add links, or bulleted lists.
* **Additional alt text —** Accessibility text for this step, read by screen readers — not shown visually.
* **Hotspot —** One hotspot for the whole step. It stays visible the entire time the step is on screen.  Place a hotspot directly on the image to mark what the viewer should interact with, and choose its *Style: Traditional, Arrow, Box, Circle, or Star.*

***

## Timeline Step Content

A Timeline Step turns one step into a scrubbable video or image sequence. Instead of a single static screen, use it to walk viewers through different scenarios. This could be a drag-and-drop interaction, an animated transition, or anything a single screenshot can't capture.

* **Header —** Add an image that appears above the step's main content. This is usually a top-level navigation item like a hamburger menu or anything you want to live above your main content. *Specs: Desktop 1280px, Mobile 750px, Tablet 888px, Watch 476px.*
* **Footer —** Add an image that appears below the step's main content. Usually a bottom-level navigation item with your apps pages, quick actions, or a more menu. *Specs: same as Header.*
* **Main Image —** Add the screenshot or image for this step based on the device type you selected in the demo settings. *Specs vary by device: 1280 x 800px for Desktop, 750 x 1624px for Mobile, 888 x 1166px for Tablet, 476 x 832px for Watch.*
* **Timeline Player —** Add one or more images or video clips in sequence to build the scrubbable timeline. Drag to resize how long an image displays; video clips are trimmed instead using Edit Video. *File types accepted: JPEG, PNG, GIF, SVG, and MP4.*
* **Edit Media —** Here you can crop your image or trim a video clip to the range you want. Drag the start and end handles on the reel *(shown in mm:ss)*. Toggle "Mute video audio in demo playback" to control whether the clip's original audio plays during the demo.
* **Keyframes —** Mark specific moments on the timeline where a hotspot and text callout should appear during a step. Select **Add Key Frame** at any point on the scrubber to drop a new one. Each keyframe gets its own text field for callout copy, plus its own hotspot placement and style. Set the same way as a Single Step's hotspot. Add as many keyframes as the sequence needs, and remove any with Delete Keyframe.
* **Hotspot —** Add a separate hotspot per keyframe. As the viewer walks through the sequence, a different hotspot can appear at each keyframe. Because of that, keyframe hotspots get one extra field Single Step hotspots don't have: Duration (how long that keyframe's hotspot stays visible once its moment is reached; 0 means it stays until the next keyframe).

***

## Demo Feedback

The Feedback Page gives viewers a dedicated place to tell you what they think. Use it to collect ratings, open-ended comments, or contact details from anyone exploring your demo.

* **Tab Title —** This is the nav label for this page, defaulting to "Give Us Your Feedback."
* **Icon —** Select an icon using the button next to Tab Title. It opens the standard icon-selector modal.
* **Form —** The actual question builder. It's a sortable list where each question has:

  * **Type —** 11 options: Small Form, Large Form, Likert (10), Likert (5), Likert (3), Sentiment Scale, Yes/No, Up/Down, Name, Email, Contact Request.
  * **Question —** the question's text or body copy.

You can drag questions to reorder them, duplicate one, delete one, or hit + Add Question to add a new one.

***

## Completion Page

The Completion Page is the natural endpoint of a demo. It appears automatically once a viewer has worked through every step, closing out the experience and pointing them toward what to do next. It never shows up in the nav, so there's nothing to turn on or off.

* **Completion Message —** The main message shown when a viewer finishes. You can format the text, add links, or lists.
* **Completion Image —** Here is where you add an image for the page. If "Make image the full background" is ON, the image covers the full page background (specs: 1920 x 1700px); if OFF, it shows as a banner instead (specs: 1920 x 380px).
* **Mobile Alternate Image —** If you want to use a different image for mobile than what's set for your Completion Image, add it here. *Specs: 1120 x 610px.*
* **Buttons —** Each button is independent — use either, both, or neither.
  * **Continue to Demo —** Point viewers to another demo, with its own button label.
  * **Custom Link —** Point viewers to any URL, with its own button label.
* **Additional Text —** Optional extra copy shown below the main message — toggle ON to reveal a second rich-text field.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.