> For the complete documentation index, see [llms.txt](https://docs.intelligems.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intelligems.io/general-features/editors.md).

# Editors

Every experience starts with a change to your site. This is where you make it.

Intelligems gives you a few different ways to build a change, depending on what you're editing and how much control you want. Most changes happen in the Visual Experience Builder, which is the default editor on every account. Use the others when you need to work directly with images or write your own CSS and JavaScript.

Whichever editor you use, the change is saved to the experience itself. You build it once, then choose whether to run it as a Test or a Personalization.

### **Choosing an editor**

| Editor                                                                   | What it's for                                                             |
| ------------------------------------------------------------------------ | ------------------------------------------------------------------------- |
| [Visual Experience Builder](/general-features/editors/visual-builder.md) | Click any element on your site and change it, without touching your theme |
| [AI Visual Builder](/general-features/editors/ai-visual-builder.md)      | Describe the change you want in plain language and let Viv build it       |


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.intelligems.io/general-features/editors.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.