> For the complete documentation index, see [llms.txt](https://bricksmotion.gitbook.io/bricksmotion-components/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bricksmotion.gitbook.io/bricksmotion-components/components/scroll-scenes/sticky-sections-1.md).

# Sticky Sections #1

### Component Structure

* **SS1 COMPONENT** (Section): The main container for the sticky sections, set up with specific classes for styling and functionality.
  * **SS1 SECTION** (Block): Multiple sections that make up the core of the component, each designed to stick to the top of the viewport as the user scrolls through the content. These sections are styled with `ss1__section` for sticky behavior.
    * **SS1 CONTAINER** (Container): Holds the content for each section, including images and text. The container is set up for grid display to organize the content neatly.
      * **SS1 IMG** (Image): Each section contains an image styled with `ss1__img`, displaying various visuals related to the section's theme.
      * **SS1 CONTENT WRAP** (Block): A wrapper for the textual content within each section, providing a structured space for headings and text.

### Animation Structure

**SS1 - IMG**

This timeline focuses on animating the images within each section, applying grayscale filters and opacity changes to create a dynamic visual effect as the user scrolls. Animations are triggered by scrolling into the section, making the images stand out through transitions.

**SS1 - CONTENT**

This timeline is dedicated to animating the textual content within each section. It modifies the content's opacity and position (using the `y` property) to create a fading and sliding effect as the user scrolls past the sections. The goal is to draw attention to the content through smooth, engaging transitions.


---

# 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://bricksmotion.gitbook.io/bricksmotion-components/components/scroll-scenes/sticky-sections-1.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.