> For the complete documentation index, see [llms.txt](https://documentation.alpaco.email/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.alpaco.email/how-to/escape-code-from-the-editor.md). # Escape code from the editor We know how important your code is to you and the slightest little mistake can be detrimental to your output. So we've created two tags for you that each serves their purpose. ### Raw code This tag tells the editor to disregard whatever is within it. The code won't be processed by the Editor, but it will be present at export for your ESP to process. This is useful when you have something you don't want the Editor to try and process, but still want it present for your own data processing in your ESP. ``` {% raw %} // This is not processed by the Editor, but will be exported for your ESP {% endraw %} ``` ### Preview only This tag give you some options to show something in the editor, but have something else displayed at export. This is particular useful for something like product variables or a recommended feed. You can have something neat and informative displayed for the user, but at the export have all the necessary variables injected that the user should not see. ``` {% if preview %} // This is shown in the Editor for visual purposes {% else %} // But this is what's actually exported for the ESP {% endif %} ``` --- # 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://documentation.alpaco.email/how-to/escape-code-from-the-editor.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.