> For the complete documentation index, see [llms.txt](https://everyday-digital.gitbook.io/authoring-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://everyday-digital.gitbook.io/authoring-docs/content-pages/content-page-library/memory-game.md).

# Memory Game

## What is a Memory Game?

**Create a memory game to drive visual learning and recognition.** The Memory Game shows the back of up to 12 cards. Each card is revealed with a tap and can then be paired with its match.

## Quick steps: how to create & edit a Memory Game

1. **Open Authoring.** Create or open a [Learning Story](/authoring-docs/authoring/content-types/learning-story.md) [content type](/authoring-docs/authoring/content-types.md).
2. **Open the Editor.**
3. **Add a Memory Game page.** Select the + icon and choose Memory Game from the Add Page options.&#x20;
4. **Edit the page.** Select the page to view [Page Options](/authoring-docs/content-pages/story-and-page-settings.md#what-are-the-page-options), then select Update to add and edit content.&#x20;
   * To set a time limit on the Memory Game, enter a Maximum Time In Minutes. If set to 0, the time to complete the game is unlimited.
   * Change the background colour if desired.
   * Add up to six (6) different cards (at least 420 x 588px each) that need to be matched. Add one image that will appear on the back of all cards.&#x20;
5. **Create a Response (Optional).** Select the [Add Response](#how-do-i-create-a-response) button to provide user feedback for correct and/or incorrect answers.
6. **Add an Activity Guide.** Add the [Memory Game Guide](/authoring-docs/content-pages/content-page-library/activity-guide.md) page in fornt of the Memory Game page in order to supply users with instructions on how to play.

## Memory Game FAQ & Tips

### How do I create a Response?

Select the Add Response button and upload an image or icon and enter the dialog text. Dialogs that have over 40 characters will show as a pop up.

### How does the Memory Game work?

**The memory Game page presents a user with twelve cards, all turned over to display the back of the card.** Each time a card is selected, it is turned over. A second card may then be selected in order to match the card that is already open.&#x20;

**The user must match all cards in order to proceed.** If a time limit has been set, they need to complete the game within that time.

**Users may be evaluated.** Depending on the grading and scoring settings, users can be evaluated on this activity. [Story Settings](/authoring-docs/content-pages/story-and-page-settings/story-settings.md#scoring-grading-mode)

**Response Dialogs.** [Add a response](#how-do-i-create-a-response) to provide user feedback for correct and incorrect answers.

### What are the image specifications for the Memory Game cards?

Each card should be portrait and be at least 420x588px big or at a higher ratio (.svg, .jpg or .png format).&#x20;


---

# 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://everyday-digital.gitbook.io/authoring-docs/content-pages/content-page-library/memory-game.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.
