> For the complete documentation index, see [llms.txt](https://docs.lufavo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lufavo.com/frameora/sections/how-it-works.md).

# How it works

The How it works section explains the customer journey in a simple step-by-step format.

Use this section to show how customers can order, customize, preview, or use your products.

### Open How it works settings

{% hint style="success" %}
To edit the How it works section:

* Find **Frameora**.
* Click **Customize**.
* Open the page that contains the How it works section.
* Select **How it works** in the theme editor sidebar.
* Edit the section settings and step blocks.
* Click **Save**.
  {% endhint %}

***

### Section content

The main section settings include:

* Kicker
* Heading
* Subheading
* Image
* Overlay label
* Overlay heading

#### Kicker

Use the **Kicker** field for short text above the heading.

Example:

**HOW IT WORKS**

#### Heading

Use the **Heading** field for the main section title.

Example:

**From camera roll to gallery wall in three simple steps.**

#### Subheading

Use the **Subheading** field to explain the process.

Example:

**Frameora keeps the process simple: upload your photos, choose the layout, and stick your tiles anywhere without tools.**

***

### Image

Use the **Image** setting to upload the main visual shown beside the steps.

For best results:

* Use a clear product or lifestyle image.
* Choose an image that explains the process visually.
* Avoid important details near the edges.
* Preview the section on desktop and mobile.

***

### Overlay content

The section includes overlay text that appears on top of the image.

Overlay settings include:

* Overlay label
* Overlay heading

Example:

**Overlay label:** PREVIEW-READY WALLS\
**Overlay heading:** See the look before it ships.

Use overlay text to highlight a helpful promise, preview step, or product benefit.

***

### Step blocks

The How it works section uses individual **Step** blocks.

Each Step block includes:

* Step number
* Step heading
* Step text

Frameora supports up to **3 step blocks** in this section.

***

### Step number

Use the **Step number** field to show the order of the step.

Examples:

* 01
* 02
* 03

***

### Step heading

Use the **Step heading** field for the main step title.

Examples:

* Upload photos
* Choose your layout
* Stick and restick

Keep each heading short and action-focused.

***

### Step text

Use the **Step text** field to explain the step.

Examples:

* Choose favorite family, travel, pet, or wedding moments.
* Arrange your set and preview a clean gallery look.
* Place tiles without nails, then move them anytime.

Keep step text short so the section stays easy to scan.

***

### Best practices

Use the How it works section to reduce customer confusion and explain the buying process clearly.

Good step content is:

* Simple
* Sequential
* Easy to understand
* Focused on customer actions
* Short enough to read quickly

Preview the section on mobile to make sure all steps remain readable.

***

### Save your changes

After editing the How it works section, click **Save**.

If changes do not appear immediately, refresh the storefront or open the page in a private browser window.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.lufavo.com/frameora/sections/how-it-works.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.