DTC 477: Advanced Web Design & Development

Week 14: Game Design & Media Layers

Important: Share a link to your GitHub repository with your team and instructor.

To make your repository public:
Go to Settings → General in your GitHub repo, scroll to the bottom, and change the repository visibility to Public.

This Week’s Workflow

This week is about refining, completing, and preparing your game for final submission. Your core systems should already be in place. Now you are focusing on polish, clarity, and usability.

  1. Fine-Tune Scripts – Clean up and finalize your JavaScript. Fix bugs, simplify logic where possible, and make sure your code is readable with clear comments. Each team member should contribute to improving the overall system, not just their isolated part.
  2. Create and Integrate Assets – Add final images, sound, and visual elements. These can be original or AI-assisted, but should feel cohesive. Avoid random or mismatched styles—your game should feel like a unified experience.
  3. Game Text & Writing – Finalize all written content: introduction, instructions (“how to play”), in-game text, and credits. You may use AI for drafting, but revise the writing so it has a clear tone and fits your game world.
  4. Testing and Playtesting – Actively play your game multiple times. Have others play it. Look for:
    • bugs or broken logic
    • confusing instructions
    • difficulty balance
    • user experience issues
    Track issues using GitHub Issues and document fixes.
  5. UI & CSS Polish – Refine layout, menus, transitions, and visual clarity. Make sure the interface is intuitive and readable.
  6. Documentation – This is critical:
    • Write clear comments in your JS files (with developer names at the top, logic steps and links to chats)
    • Update GitHub README (project overview, roles, how to play)
    • Create About page with credits, chat logs, a paragraph describing the project: what, who, how...
  7. Final Integration – Make sure everything works together as one complete game. Each team member should test the full project—not just their part.
  8. Final Submission Prep – Each student hosts the same final version of the game. Submit:
    • Live game URL (on Canvas and in Slack channel)
    • GitHub repo link (public, with commit history)

Deliverables