> For the complete documentation index, see [llms.txt](https://docs.liquid-gears.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.liquid-gears.com/index.md).

# Platform components

The Liquid Gears Platform is comprised of core components and associated optional services.

The main components of the platform are:

* Carbon Editor for content creation and curating
* Ubiquity Dashboard for content distribution and App User management
* Mobile and Desktop apps to distribute content into
* Integrated Web Apps (a.k.a. IWAs) which comprise the user interface of the apps for end-users
* Admin Dashboards

Other optional components are:

* a document search service
* a Private Information Provider (a.k.a. PIP) to store and retrieve sensitive information

Other features can be delivered through the use of one or more components lissted above:

* localisation
* analytics
* flexible use of content metadata
* etc.


---

# 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.liquid-gears.com/index.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.
