> For the complete documentation index, see [llms.txt](https://dev.ubidots.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dev.ubidots.com/dashboards-and-widgets/custom-ui/paragraph.md). # Paragraph Displays headings or paragraphs depending on the \`type\` property.

This element makes it easy to apply different text styles. The following table describes each available paragraph type: | Paragraph type | Description | | -------------- | ------------------------------------------------------ | | normal | Displays standard text without any special formatting. | | bold | Displays text in bold style. | | h1, h2, h3, h4 | Displays the corresponding heading. | ## Paragraph type: normal Displays a paragraph similar to the HTML `

` tag. ## Paragraph type: bold Displays bold text, similar to the HTML `` or `` tags. ## Paragraph types: h1 to h4 Displays heading text according to the selected heading level. Similar to the HTML `

` to `
` tags. #### Examples The following XML maps to the screenshot shown at the beginning of this section. ```xml
NORMAL BOLD H1 H2 H3 H4
``` --- # 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://dev.ubidots.com/dashboards-and-widgets/custom-ui/paragraph.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.