> For the complete documentation index, see [llms.txt](https://docs.tomorrowx.com/cap/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tomorrowx.com/cap/best-practices/tag-replacement-techniques.md).

# Tag Replacement Techniques

## Simple tag replacement.

A special tag is inserted in the html page, where we desire data to be inputted. The tag could be of the form “`$tag_name$`” or any other selected format that will uniquely identify it in the html page.

Use the “**Template Replacer**” rule to replace unique tags in the html page with the values of given parameters.

## Tag replacement with parent tag repetition.

It is similar to the previous technique, with the added benefit of finding the parent html tag of the unique tag, in order to repeat it.

This is useful, for example, when we want to add new table rows without changing the already existing attributes and style of the “`<tr`” parent tag.

It can also be used for html options or html lists.


---

# 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.tomorrowx.com/cap/best-practices/tag-replacement-techniques.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.