> For the complete documentation index, see [llms.txt](https://docs.launchboard.app/cxd/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.launchboard.app/cxd/cxd-2022-summer-workshops/programming-workshops/video-game/program-a-video-game.md).

# Program a Video Game ⏱

#### **👉 As you work through the following activities don't hesitate posting questions on Slack (#ws-programming-video-game) and include a link to your Replit code when needed (or even a short video).**

{% embed url="<https://www.loom.com/share/ec31e31a8ac149e8b9322795575bb780>" %}

## 1 Complete the Hello Phaser Tutorial to Get Started

{% embed url="<https://docs.idew.org/video-game-code-reference/tutorials/hello-phaser>" %}

## 2 Complete the Matching Game Tutorial to Understand Some Key Concepts in Programming with Phaser

{% embed url="<https://docs.idew.org/video-game-code-reference/tutorials/matching-game>" %}

## 3 Complete One (or Both) of the Following Game Tutorials

{% embed url="<https://docs.idew.org/video-game-code-reference/tutorials/top-down-game>" %}

{% embed url="<https://docs.idew.org/video-game-code-reference/tutorials/side-scrolling-game>" %}

{% hint style="success" %}

## Well done! Share a link or two of any games you have created on Slack!

{% endhint %}

## Planning for Student Success

Now that you have experience with programming for this project...

* **Consider how you will approach classroom management when students are completing a tutorial like this one.**&#x20;
  * What will be your expectations?&#x20;
  * How much will be individual work versus team work?
  * Will you assign any code champions to help you support students with questions?
* **How will you supplement it with other programming content or experiences?**
  * Will you use any online tutorials?
  * Will you supplement with any CS unplugged activities?
  * Will you create any custom programming exercises yourself?


---

# 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://docs.launchboard.app/cxd/cxd-2022-summer-workshops/programming-workshops/video-game/program-a-video-game.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.