> 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/demo-components.md). # Demo Components ### Adding **Demo Components on a page** Sites created under the **Default (Managed)** team have access to components from the [mechcloud-demo-microapp1](https://github.com/mechcloud/mechcloud-demo-microapp1) repository by default. Here are some examples on how to add these demo components on a page - ``` Add 'demo hero' component ``` ``` Add 'demo pricing' component ``` **demo** is actually an alias for **rkt** and so you can very well replace **demo** word with **rkt** in the above prompts. For other generic components, use: "Add a `` component." #### **Applying CSS Classes and Styles** Enhance your components by specifying styles or classes directly - ``` Add a div with a yellow background and 1px solid border ``` ``` Insert a div with class1 and class2 classes ``` #### **Updating Component Properties and Styles** To modify component properties - * Select the desired component. * Use the properties editor in the rightmost column to adjust attributes, styles, or classes. --- # 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/demo-components.md?ask=&goal= ``` `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.