> For the complete documentation index, see [llms.txt](https://docs.carto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.carto.com/carto-for-developers/quickstart/create-your-first-widget.md).
# Create your first widget
As you've seen in [Key Concepts](/carto-for-developers/key-concepts.md), CARTO can help you build fully-customizable, framework-agnostic charts and widgets that stay synchronized with your map, and offer advanced filtering abilities.
In the following [examples](/carto-for-developers/examples.md) you will learn how to add these widgets to your map, and how a widget can filter the map and viceversa. There are multiple examples but here's our recommendation on where to start:
* Start with the [Formula widget](https://github.com/CartoDB/deck.gl-examples/tree/master/widgets-formula) example if you need a very basic understanding of how widgets in CARTO work.
* Go to the [Hello world with widgets example](https://github.com/CartoDB/deck.gl-examples/tree/master/hello-world-with-widgets) if you need a more complete example, with several widgets and filtering in and from the widgets.
Feel free to modify these examples to use your own data! Just remember to change the token in the `.env` file, as well as the `vectorTableSource` properties.
---
# 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.carto.com/carto-for-developers/quickstart/create-your-first-widget.md?ask=&goal=
```
`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.