> 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/third-party-components.md).

# Third Party Components

You can create your own components, add these components and associated properties forms to a micro app and then configure this micro app on the team or site level.

:point\_right: **Page designer does not require registering the built-in or custom components under 'Site Builder -> Components' UI.**

### **Guidelines for creating own components**

* Each third component must have an associated properties editor component as well if the component is having any editable property. Properties editor component name MUST be in the `<component_name>Props.vue`format. Example - <https://github.com/mechcloud/mechcloud-demo-microapp1/tree/main/src/components/generic/rktH2>.
* Have a look at different components available under <https://github.com/mechcloud/mechcloud-demo-microapp1/tree/main/src/components/generic> folder for sample demo components. You can use these to write your own components.
* Make sure all of your components are having a unique prefix (**mc**, **rkt** and **demo** are reserved prefixes).
* If it is not possible to have unique prefix for your (existing) components then you can put the prefix while exporting a component in the micro app -

```
export { default as DemoCmpnt1 } from './Cmpnt1.vue'
```

* Keep all your own components under a dedicated folder (e.g. **internal**) which should be a child of <https://github.com/mechcloud/mechcloud-demo-microapp1/tree/main/src/components> folder.


---

# 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/third-party-components.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.