> For the complete documentation index, see [llms.txt](https://brand.coingecko.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://brand.coingecko.com/visual-identity/style/effects.md).

# Effects

## Elevation

Elevation is not a big part of the CoinGecko visual style. We like sticking to simple flat surfaces like Gecko’s in real life. 

{% hint style="info" %}
**We use elevation only for specific UI components** within Moon Design System.
{% endhint %}

For other brand related applications within CoinGecko we recommend the following:

* When possible, avoid using elevation such as drop-shadows or box shadows
* Instead, opt for a suitable replacement such as a simple outline or divider stroke when trying to distinguish elements of a design.
* Elevation may be used on a case-by-case basis if absolutely necessary. Please consult the design team if you intend to use elevation in company presentations or visuals.

{% hint style="danger" %}
On the web: CSS box shadows generally have poorer performance implications on page rendering times (i.e. browsers don’t like it)
{% endhint %}


---

# 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://brand.coingecko.com/visual-identity/style/effects.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.