> For the complete documentation index, see [llms.txt](https://synap.ac/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://synap.ac/docs/platform/collections/cards-and-player-views.md).

# Cards and Player views

The **Layout** setting changes what the collection feels like to a student. Cards creates a browsable resource library. Player creates a guided, course-style journey. Although it is a single setting, it can completely change how students use the same content.

{% hint style="info" %}
**Location:** Collections → select a collection → Configure → Layout
{% endhint %}

![The Layout setting with Cards selected](https://3891068282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWXE6hvHQFtER1a1Dm3l5%2Fuploads%2F8tloSVgElr9nYTCdqPcW%2Flayout-setting.png?alt=media\&token=879cb156-71f9-43db-ac18-a36f8a7f651a)

### Cards view

Cards view presents folders and items as a browsable catalogue. Students open a card, use its content, then return to choose what they want to open next.

![A collection presented to a student in Cards view](https://3891068282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWXE6hvHQFtER1a1Dm3l5%2Fuploads%2F2aRZ2w1JJmMbqidH9ZOa%2Fcards-view.png?alt=media\&token=44f4d12a-c48e-4f5b-b9f8-baf0a61058dc)

Cards view works well for:

* a question bank where students choose what to practise;
* an optional resource library;
* a small collection whose items make sense independently; and
* content where choice and repeat visits matter more than a fixed order.

The collection heading can include its short description and, when progress tracking is enabled, the percentage viewed. Folders and sub-folders open as separate levels. Locked items can remain visible so students know that more content exists, but they cannot open them.

### Player view

Player view opens the content inside one continuous, ordered experience. On desktop, the contents menu remains beside the current item. **Previous** and **Next** guide the student through the available items in the order you have set.

![A collection item presented inside Player view with the contents menu](https://3891068282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWXE6hvHQFtER1a1Dm3l5%2Fuploads%2FQIDsSWgV8ItTWguDFf3G%2Fplayer-view.png?alt=media\&token=e3a6717d-72bb-4aee-86bd-c11b74575448)

Player view works well for:

* a course-style learning resource;
* content with an intended reading or activity order;
* a longer collection where students benefit from seeing their position; and
* notes and documents that should be read without repeatedly returning to a card grid.

Folders and sub-folders become groups in the contents menu. Items that are locked or outside their schedule appear as unavailable and are skipped by **Previous** and **Next**.

### Cards and Player compared

| Student experience   | Cards                                             | Player                                               |
| -------------------- | ------------------------------------------------- | ---------------------------------------------------- |
| Feels like           | A library or question bank                        | A course-style resource                              |
| Opening content      | Open an individual card                           | Open content inside the collection Player            |
| Moving between items | Return and choose another card                    | Use the contents menu or **Previous** and **Next**   |
| Order                | Visible, but students choose what to open         | Strongly suggested by the navigation sequence        |
| Folders              | Browsable levels                                  | Groups in the contents menu                          |
| Overview             | The card list is the main overview                | A separate overview can appear before the first item |
| Annotations          | Not available as a collection-level Cards feature | Can be enabled for supported content                 |
| Collection export    | Not available from Cards view                     | Can be enabled for supported items                   |

### Hide overview page

This option appears when Player is selected.

* **Disabled:** students first see an overview of the collection's folders and items. The overview remains available in the contents menu.
* **Enabled:** students go directly to the first item and the overview entry is removed.

Hiding the overview makes the collection feel more immediate and linear, but students lose the initial map of what it contains. Make sure the first item works as an introduction and that the order remains clear.

{% hint style="warning" %}
If the first item is unavailable or placed unexpectedly inside a folder, students may arrive at a confusing starting point. Preview the student view after changing the structure or schedule.
{% endhint %}

### Changing an existing collection

Switching layout does not change the item order, folders, access or schedules. It changes how students move through that structure. A free-choice question bank can suddenly feel compulsory in Player view; a carefully sequenced learning resource can lose its sense of progression in Cards view.

Before changing a collection that students already use, check:

* the overview and first available item;
* folder and sub-folder names;
* locked and scheduled items;
* desktop and embedded layouts;
* generated-attempt and mock actions, if enabled; and
* annotations and export, which are Player-specific collection features.


---

# 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://synap.ac/docs/platform/collections/cards-and-player-views.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.