Gamify Exploration

Student Checklist

Use the game above as your starting point.

1. Play through every area and identify the player, an NPC, and an enemy.
2. Pick one small change your team could make: a level, sprite, interaction, or game rule.
3. Tell your team which part you will own before changing code.

Team Setup Checklist

Before editing, one team member creates the GitHub portfolio repo, then:

1. Add Collaborators → Settings → Collaborators → Invite your team (they need write access)
2. Enable Issues & Projects → Settings → Features → Check both boxes
3. Each person clones → git clone <repo-url> in Terminal
4. Open in VSCode → cd portfolio; source venv/bin/activate; code .

Everyone needs the repository open in VSCode with collaborator access before they can contribute.

How This Game Is Built

The project keeps each kind of work in a predictable location:

• levels/ contains the JavaScript that assembles each game level.
• images/ contains the backgrounds and sprites used by those levels.
• docs/ contains the project notes your team can use as a model.

Read the Gamify project overview to understand the directory layout, workflow, and asset paths. Then use the sample Water level documentation as a model for recording the goal, files changed, sprites, testing, and next step for your own work.

Daily Team Checklist

1. Pull latest changes from your team branch/repo.
2. Run make dev and keep it running while you work.
3. Pick one Issue and complete one scoped change.
4. Commit in a branch or open/update a PR from a fork; the scrum master integrates.
5. Move Kanban cards and post Issue progress notes with evidence.

What a strong VSCode desktop looks like: