> For the complete documentation index, see [llms.txt](https://docs.wem.io/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wem.io/platform/template-editor/miscellaneous/script.md).
# Script
##  Introduction
{% hint style="info" %}
You can find more information about the WEMScript in the specific pages. There is a page about the [WEMScript for Custom HTML](/platform/wemreference/wemscript-for-custom-html.md), and [WEMScript for Widgets](/platform/wemreference/wem-widgets/wemscript-for-widgets.md).
{% endhint %}
With the Script widget you can add HTML code and other script code (like JavaScript) to the Template Editor.
**Note**: when you use the Script widget, it is possible to overwrite (intended or unintended) the Design Template settings.
Drag and drop the Script widget to the Template Editor and the box below appears.
## Illustration
Let's build upon the EMS use case from where we had left at in the page for 'Nested Templates'. We had built an interaction template with a Tabbar consisting of two tabs and Datagrids inside Conditionals that should be displayed based on the tab clicked. The 'Projects' tab at run-time was something like the below.
Let's say that we now have this requirement - the total number of projects should be shown below the table, in red font.
1. Open the 'Projects' Template Fragement.
2. Insert a Label below the Table, which would show a count of the number of projects.
3. Click and drag the 'Script' icon and place it above the Label.
4. Compose your Script and then click on 'Validate'.
5. Repeat steps 3 and 4 for closing the script, but below the Label.
6. Click on 'Save' in the Template Editor. When you preview, you will now see the Label in red below the Table.
---
# 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.wem.io/platform/template-editor/miscellaneous/script.md?ask=&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.
