> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/classic-app-builder/design-and-structure/components/html-component.md).

# HTML Component

Creating a HTML component and passing values to it.

Custom HTML components offer flexibility and customization options in your application. You can create these components and pass values to them from anywhere else in the application via parameters. Below is a guide on how to effectively use custom HTML components

**Adding an HTML Component:**

{% @arcade/embed flowId="hIBIIhyMcytQbx1APlzB" url="<https://app.arcade.software/share/hIBIIhyMcytQbx1APlzB>" %}

**Modifying and using Parameters:**

Customizing custom HTML components involves the strategic selection and effective usage of parameters. By carefully adjusting and renaming parameters, you ensure the component aligns seamlessly with your application's specifications, resulting in an enhanced user experience.

{% @arcade/embed flowId="bhf45yEqpV2R6hoQ7Dj0" url="<https://app.arcade.software/share/bhf45yEqpV2R6hoQ7Dj0>" %}

**Using HTML Attributes with Tags:**

In addition to parameters, HTML attributes like 'style' and others can be used alongside tags in HTML components. This allows for direct application of various attributes.<br>

{% @arcade/embed flowId="G19xxQ36ePAXpD6rsqEn" url="<https://app.arcade.software/share/G19xxQ36ePAXpD6rsqEn>" %}


---

# 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.jetadmin.io/classic-app-builder/design-and-structure/components/html-component.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.