> For the complete documentation index, see [llms.txt](https://uxsmart.gitbook.io/velare/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://uxsmart.gitbook.io/velare/customize-your-pages/storytelling/featured-review-slider/group-block-content/block-quote.md).

# Block - Quote

**Quote** holds the review itself: the stars, the words the customer wrote, and who wrote them. It is what a hesitating shopper actually reads on a slide of the [Featured review slider](/velare/customize-your-pages/storytelling/featured-review-slider.md), and the reviewer's name and location are what make it read as a real person rather than marketing copy. Add one quote per slide inside a [Content](/velare/customize-your-pages/storytelling/featured-review-slider/group-block-content.md) block.

<figure><img src="/files/nBdLu5ExshIOwZb8VcYq" alt=""><figcaption></figcaption></figure>

### Where to find it <a href="#where-to-find-it" id="where-to-find-it"></a>

{% hint style="success" %}
**Steps:**

1. Go to **Online Store > Themes > Customize**.
2. In the left sidebar, click the **Featured review slider** section.
3. Open the **Content** block for the slide you are building.
4. Click **Add block**, choose **Quote**, then fill in the rating, the review, and the reviewer details.
   {% endhint %}

*Result:* the stars, the review text, and the reviewer details render inside the content half of the slide.

### Settings <a href="#settings" id="settings"></a>

| Setting            | Description                                                                                                                                                                  |
| ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Rating star**    | How many stars this review shows. Set it to match what the customer actually gave, since a wall of perfect fives reads as less credible than an honest mix.                  |
| **Rating color**   | The color those stars are filled with. Amber and gold read as a rating instantly, while a brand color blends in more quietly.                                                |
| **Author name**    | Who left the review. A first name and initial is usually enough, and something is always better than an anonymous quote.                                                     |
| **Author address** | A line under the name giving the person context, such as a city, a job title, or the company they work for. It is what makes the review feel like it came from someone real. |
| **Quote content**  | The words of the review. Keep it to the part that answers a real doubt, because a shopper will not read a full paragraph on a moving slide.                                  |

### What changes on the storefront <a href="#what-changes" id="what-changes"></a>

* Everything a shopper reads on the slide comes from this block. The blocks around it only decide where it sits and what color it is on.
* The review is typed in by hand, so it does not update itself when new reviews come in. Revisit it when the quote goes stale.
* Leaving **Author name** empty removes the attribution, which weakens the review even when the words are good.

### Related pages <a href="#related-pages" id="related-pages"></a>

* [Group Block - Content](/velare/customize-your-pages/storytelling/featured-review-slider/group-block-content.md): the block this one lives inside
* [Featured review slider](/velare/customize-your-pages/storytelling/featured-review-slider.md): the section it appears in
* [Block - Image](/velare/customize-your-pages/storytelling/featured-review-slider/group-block-media/block-image.md): the picture shown next to the quote


---

# 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://uxsmart.gitbook.io/velare/customize-your-pages/storytelling/featured-review-slider/group-block-content/block-quote.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.