> For the complete documentation index, see [llms.txt](https://help.adalo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.adalo.com/feature-templates/browse-purchase-and-manage-classes/category-list-screen.md).

# Category List Screen

<figure><img src="/files/zP5Gvxg1j6yHGZS3ASt6" alt=""><figcaption></figcaption></figure>

The Category List Screen is a page that is dedicated to displaying the high level categories that your offering is divided into. This screen is made up of several components including a side navigation component, image component, text components, list component, and a button component.

### The Components

### [**Side Navigation**](#user-content-fn-1)[^1]

The side navigation should appear on each screen you intend for the user to navigate. This is important to help users find the information they are looking for. In this feature template, on this screen, you will notice the “Clinics” Menu Item is highlighted. This is to denote where, in the app, the user is.

<figure><img src="/files/ZNDuyYm4Zl41Fhc2iCNm" alt="" width="375"><figcaption></figcaption></figure>

The Navigation is plan text that can be updated in the side panel within the Adalo Builder. In this case, the ‘Clinics’ Menu Item is Menu Item 2 and the settings look as follows:

<figure><img src="/files/xj4r1opZE7G8NmnX7qXB" alt="" width="367"><figcaption></figcaption></figure>

None of the Menu Items utilize Magic Text and therefore are not referencing the database, however, the “Profile Section” does reference the database.

{% hint style="info" %}
If you change something on one screen in the side navigation component, you must change all instances of the side navigation on the other screens. You can do this using CMD + C (copy) and CMD + V (paste) on a Mac.
{% endhint %}

### **Image Component — Main Image**

This image component is not connected to the database and can be changed within the Adalo builder.

<figure><img src="/files/DLMBOeft1Yr322k4pmsx" alt=""><figcaption></figcaption></figure>

Changing any of the settings for this component will not alter the functionality of your app.

### **Text Component(s) — 2 Components**

These text component is not connected to the database and can be edited and styles can be changed without directly impacting the functionality of the app.

<figure><img src="/files/apkvUd4L5UmU7cDQnfeF" alt="" width="375"><figcaption></figcaption></figure>

### **List — Categories List**

This component is controlled by the database. In other words, this list displays information that is found within Collections — specifically, the Categories Collection.

<figure><img src="/files/tUkGz4CtvOrhS83dV0eC" alt=""><figcaption></figcaption></figure>

This list displays the following properties from the Category Collection:

* Name
* Short Description

It also displays a ‘Count’ of the number of classes associated with the Category through the property “Classes”.

**⚡ List Actions**

<figure><img src="/files/oDHcLHRtKmvbeAn2IQ7m" alt="" width="355"><figcaption></figcaption></figure>

The list contains a Link Action to the ‘Classes List’ Screen.

### **Button Component — Admin Portal Button**

This button component is only displayed to those users who have the value TRUE in the property “Is Admin?” in the Users Collection. This is done through visibility settings.

<figure><img src="/files/BTwFkViiKQ6sTK78EqDi" alt="" width="359"><figcaption></figcaption></figure>

In the setup tab, anything can be changed without changing the functionality of the button.

⚡ **Button Actions**

The button contains a Link Action to the ‘Admin Manage Clinics’ Screen.

[^1]:


---

# 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://help.adalo.com/feature-templates/browse-purchase-and-manage-classes/category-list-screen.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.