> For the complete documentation index, see [llms.txt](https://docs.nickarce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nickarce.com/bricks-mega-menu/docs/bricks-mega-menu-template/getting-started/dropdowns.md).

# Dropdowns

## Dropdown Background Color

***

Edit $dropdown-background to your desired color

```scss
// WHAT BACKGROUND COLOR DO YOU WANT FOR DROPDOWN WRAPPER ******
$dropdown-background: white;
```

## Dropdown Reveal Animation Position

***

### When its not visible where do you want it to be positioned?

Change the below to your desired value. The higher the number the lower it sits in the browser.

```scss
$fade-up-closed: 40px; // STARTING POSITION (not active)
```

### When the dropdown is visible where do you want it positioned?

Change the below to your desired value. The higher the number the lower it sits in the browser.

```scss
$fade-up-open: 20px; // ENDING POSITION (active)
```

## Dropdown Chevron Animation

***

There are three animation choices for the dropdown chevron icon when the dropdown is open and active. 

1. none: no animation
2. flip: flips the icon 180deg
3. rotate: rotates the icon 180deg

```scss
$active-dropdown-icon-anim: flip; // SELECTION (none/flip/rotate)
```

## Dropdown Accessibility

***

The template does as much as it can to be accessible but it will require you to make a few changes that will be unique to your website. 

For every dropdown you will need to add in an aria-label. This tells keyboard users what opening the dropdown will do. Examples:

* If the dropdown text is "Men's Clothing" the aria-label should be something like "Toggle Men's Clothing Dropdown"
* If the Dropdown Text is "Resources" the aria-label should be something like "Toggle Resources Menu"

You can call it a menu, dropdown, list, etc. That part is up to your website preference.

<figure><img src="/files/K9pTWOr2ISF0ytvfVr9Z" alt="" width="230"><figcaption></figcaption></figure>


---

# 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.nickarce.com/bricks-mega-menu/docs/bricks-mega-menu-template/getting-started/dropdowns.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.