> For the complete documentation index, see [llms.txt](https://staylime.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://staylime.com/docs/volume-themes/sections/trust-and-social-proof.md).

# Trust & Social Proof

Sections that build credibility — customer testimonials, press and partner logos, and icon-based guarantees.

Most visitors arrive slightly sceptical. These three sections answer that in different ways: **Testimonials** brings in other customers' voices, **Logo Slider** borrows credibility from names the visitor already knows, and **Icons with Text** states your own promises plainly.

### Section overview

| Section         | Page                                                                                      | What it does                                                                                                |
| --------------- | ----------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------- |
| Testimonials    | [Testimonials](/docs/volume-themes/sections/trust-and-social-proof/testimonials.md)       | A carousel of customer reviews with star ratings, photos, and full reviews that open in a pop-up.           |
| Logo slider     | [Logo Slider](/docs/volume-themes/sections/trust-and-social-proof/logo-slider.md)         | A scrolling row of press mentions, partner brands, certifications or payment badges.                        |
| Icons with text | [Icons with Text](/docs/volume-themes/sections/trust-and-social-proof/icons-with-text.md) | Shipping, returns, guarantees and other selling points as icons with short supporting copy. Grid or slider. |

### Quick decision guide

**I want customers to speak for me** → Testimonials. Keep each card to two or three lines and put the long version behind the **Page** setting.

**I have press mentions or recognisable partners** → Logo Slider. Square, monochrome logos, evenly weighted.

**I want to state my own guarantees** → Icons with Text. Three to five items, two-word headings.

**I need a slim trust bar under the hero** → Icons with Text in *Grid* mode, small icon size, spacing lowered to about 0.5.

**I need payment or certification badges in the footer** → Logo Slider — it's one of the few content sections allowed in the footer group. Icons with Text works there too.

**My section isn't showing on the live store** → all three hide themselves when their blocks are empty. Testimonials needs at least one block; Logo Slider needs at least one block with an image; Icons with Text needs at least one block with an icon, image, heading, text or page.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://staylime.com/docs/volume-themes/sections/trust-and-social-proof.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.