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

# Appfarm Showroom

We have created a dedicated Appfarm solution for demonstrating various example setups.

This solution, named **Appfarm Showroom**, requires login.

You may sign up for access by accessing [this link](https://showroom.appfarm.app/sign-up). This will give you access to both the solution in **Appfarm Create** (for seeing how things are set up) as well as you may log in to the client (<https://showroom.appfarm.app>) to view and test the examples.

Once signed up, you will be added as a user and receive an email with info on how to access the solution in Appfarm Create.

Appfarm Showroom consists of 6 Apps, to be explained below. **Note that all Apps are "Work in progress"**, meaning more examples will be continuously added to them.

### Action Nodes Examples

This app has examples of most action nodes. The examples are grouped by category in the left menu. Open it at [showroom.appfarm.app/action-nodes](https://showroom.appfarm.app/action-nodes).

Every example has two buttons: **Open in Appfarm Create** and **View docs**.

These examples are also linked from the [Action Nodes documentation](https://docs.appfarm.io/library/action-nodes.md) section.

### UI Components Examples

This app has examples of most UI components. The examples are grouped by category in the left menu. Open it at [showroom.appfarm.app/ui-components](https://showroom.appfarm.app/ui-components).

Every example has two buttons: **Open in Appfarm Create** and **View docs**.

These examples are also linked from the [UI Components documentation](https://docs.appfarm.io/library/ui-components.md) section.

### Use Cases

This app has setups that combine several action nodes and components. Examples are AI agents, PDF generation, calendar and kanban boards, and integrations. Open it at [showroom.appfarm.app/use-cases](https://showroom.appfarm.app/use-cases).

Some of these use cases are also linked from the related how-to and library pages.

### UI/UX Design Guide

This is an interactive tutorial on our best practices for UI and UX, in other words - how to make things look good and user friendly.

You can access the tutorial without logging in [here](https://showroom.appfarm.app/ui-ux-design). Navigate to this app in Appfarm Create to see how different interactions are set up. The app is intended as a tutorial for people with limited UI/UX experience.

### Offline App

This is a working offline app. It is walked through in the [Offline data handling](https://docs.appfarm.io/how-to/data-modeling/offline-data-handling.md) guide. Open it at [showroom.appfarm.app/offline-app](https://showroom.appfarm.app/offline-app).

### Push Notification

This is a separate app that you can install on your device (a PWA). It shows the Request permissions action node together with the Send push notification action node. Open it at [showroom.appfarm.app/push-notification](https://showroom.appfarm.app/push-notification).


---

# 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.appfarm.io/getting-started/appfarm-showroom.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.
