> For the complete documentation index, see [llms.txt](https://docs.mechcloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mechcloud.io/dashboard-builder/page-designer/single-component-prompts/native-html-tags.md).

# Native HTML tags

### Adding HTML tags on a page

To incorporate standard HTML tags into your page, simply provide clear commands. For example -

```
Add an h1 heading with 'Welcome to MechCloud' text
```

```
Insert a paragraph with 'This is a sample paragraph' text
```

For more complex structures, such as a CSS grid of images -

```
Create a grid component with the following grid areas:

"area1 area1 area4"
"area2 area3 area4"

Each grid item should be an image with '<image_url>' as the source.`
```

Simply click on an element to update its properties (style, classes etc) which will display editable properties in the third column of the page designer.


---

# 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.mechcloud.io/dashboard-builder/page-designer/single-component-prompts/native-html-tags.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.