> 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-dates/time-slots-and-workout-screens.md).

# Time Slots & Workout Screens

Browsing is a central feature in most apps where there is lots of information that a user would like to view before making a selection.

The Browse Dates Feature Template is great for displaying a list of open dates and then taking a user to a details screen to view more relevant information about each date or event.

<figure><img src="https://3467607506-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LhGHkPsv15svPIU5I7C%2Fuploads%2FQ3IHjlXdNBXYem8GIqwh%2Fbrowsedatesscreens.png?alt=media&amp;token=c60ae352-c0e6-4f13-a5af-288a16f2c280" alt=""><figcaption></figcaption></figure>

By default, the list of Upcoming Challenges only shows events in the future (Date & Time is after Start of Today).

Similar to the Browse Users Feature Template, there is information that is shown in the list and on the Workout Screen that comes from the database; however, there is no way in this feature template to control that information. Without a form to input the data in the database, the admin or creator of the app must enter the information directly into Adalo.


---

# 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://help.adalo.com/feature-templates/browse-dates/time-slots-and-workout-screens.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.