> For the complete documentation index, see [llms.txt](https://sitesbyseth.gitbook.io/sitesbyseth-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sitesbyseth.gitbook.io/sitesbyseth-docs/reign/sections/testimonials.md).

# Testimonials

A review-card carousel with star ratings, locations, names, optional avatars, and dates — social proof without a reviews app. On the default theme it appears on both the homepage and product pages.

## Blocks

Each **Review** block:

| Setting         | What it does                                    | Default     |
| --------------- | ----------------------------------------------- | ----------- |
| Star rating     | 1–5                                             | 5           |
| Location        | e.g. "Toronto, ON"                              | placeholder |
| Review text     | The quote                                       | placeholder |
| Customer name   | e.g. "Marcus B."                                | placeholder |
| Customer avatar | Optional photo (shown when avatars are enabled) | —           |
| Date            | Free text                                       | placeholder |

Add as many Review blocks as you have real reviews.

## Section settings

### Layout & header

* **Full width**, **Color scheme**, and padding top/bottom (36/36)
* **Heading** ("Customer Reviews") with font size (36), weight, color, and bottom spacing
* **Rating text** ("4.8 (1,637+) reviews") with size/weight/color — ⚠️ put *your* real numbers here
* **Header star size** (20) and **Star color** (#FFD700 gold), plus spacing sliders

### Carousel

* **Maximum width** (1200), **Cards visible on desktop** (1–4, default 3), **on tablet** (2), **Gap between cards** (24)
* **Navigation position** — arrows *Inside* or *Outside* the carousel — with arrow button size (50), icon size (24), background (#121212), hover background, and icon color
* **Auto-scroll** (off) + speed (5s), **Infinite loop** (on)

### Card design & content

Full control of the cards: height (300), min width (280), padding (24), background (#FFFFFF), radius (12), and a four-part shadow group — then typography/colors for every element: card stars (16), location (13/medium/#666), review text (14/#333), name (13/semibold/#121212), date (12/#999), optional **customer avatar** (36px with ring color).

### Section style

Section background (#F9F9F9) and its own padding group (60/60/20 horizontal).

## Testimonials on the product page

The product page uses a lighter **Testimonials block** inside Product information — up to 3 inline quotes with a section label, star/avatar toggles, per-quote settings (quote, author, title/location, rating, avatar), and compact styling. Same idea, smaller footprint.

💡 **Pro tip:** Screenshot-style DM praise is gold for streetwear — transcribe real customer DMs (with permission), keep locations specific ("Atlanta, GA" not "USA"), and vary star ratings slightly. A wall of identical 5.0s reads as fake.


---

# 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://sitesbyseth.gitbook.io/sitesbyseth-docs/reign/sections/testimonials.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.