Collections
Show quests together in a titled list, such as a getting-started list or this week's challenges.
A collection is a titled list of quests your app shows together, such as "Getting started", "Booth challenges" or "This week's quests". You choose the order, and can add a description and an image.
The same quest can sit in several collections. A member's progress follows the quest, not the list, so finishing it in one place shows it finished everywhere. Duplicating a quest makes a new quest with fresh progress.
Membership and identity
| Who | Controls |
|---|---|
| Project code | Declares collections. |
| Console | Lets you edit their details, arrange quests, and publish changes. |
| Your app | Decides how to show them. |
Author collection presentation
In Console, Edit details in a collection's ⋯ menu changes the title, description, image and alt text, in the same draft as your changes to its quests and their order. Publishing shows them to members. An image can be an HTTPS address, or a path beginning with / that your app serves.
Your developer can also set these in code. A later deployment replaces the details they set there; details they left out keep your values.
{
"collections": [
{
"key": "getting-started",
"title": "Getting started",
"description": "A few activities to get familiar with the community.",
"image": "/images/getting-started.png",
"imageAlt": "The workshop entrance"
}
]
}Arrangement and eligibility
A collection only arranges quests; it doesn't decide who can take part:
| To… | Use |
|---|---|
| Show quests together in order | A collection. Its order does not enforce a sequence. |
| Require one quest to be finished before another starts | A prerequisite on the second quest. |
| Stop new tries | Pause the quest. Removing it from a collection does not pause it. |
A quest without a collection still exists; whether members see it depends on your app. Quests that run on their own don't need a claim button.