> For the complete documentation index, see [llms.txt](https://anticode.gitbook.io/templates/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://anticode.gitbook.io/templates/plugins/bubble-shaking-animation.md).

# Bubble - Shaking Animation

### Overview

This is a simple Plugin that allows you to add a sleek shaking animation to your elements when a user is hovering the element, thereby enhancing the user experience. You can choose between 8 different animations. <https://shakeplugin.bubbleapps.io/> for a demo.

Based upon <http://elrumordelaluz.github.io/csshake/> Licensed under MIT

### Instructions

1.Go to Settings-> General and add the option to expose and ID attribute for your elements. 2. Drag a "Shake" element to your page and specify the type of animation, as well as the id of the element that you want to be animated (don't forget to add the Id to the element itself).


---

# 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://anticode.gitbook.io/templates/plugins/bubble-shaking-animation.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.