Student onboarding guide

From sign-in to certificate in TeachPlay

A practical student-facing guide for accessing the AI-Enhanced Educational Game Design microcredential, learning through the guided course, submitting evidence, and understanding the certificate handoff.

Screen recording

Watch the complete learner journey

The recording was captured with Playwright from the TeachPlay learner workspace. The WebM includes ElevenLabs neural narration audio, captions are attached as a VTT track, and the separate MP3 file remains available for LMS reuse or later edits.

Student workflow

What students do, in order

01

Sign in

Use the course account provided by the instructor or continuing education unit. Signed-in progress is required for official evidence review and certificate issuance.

02

Review the credential

Open the credential page, confirm duration, CEU value, evidence requirements, and the portfolio products expected at the end.

03

Learn and build

Move through the 12-module pathway. By D3/D4, use Google AI Studio Build mode to turn the smallest defensible loop into a runnable game prototype.

04

Playtest and revise

Run the live preview with a target learner or a clearly labeled rehearsal, capture observations, and revise the game before treating it as submission-ready.

05

Submit evidence

Attach the public game link, repository/export, screenshots, short recording, playtest evidence, provenance log, and revision rationale in the portfolio.

D3 → D5 build bridge

Build the game in Google AI Studio, then submit what the game can prove

AI Studio is the build surface; TeachPlay is the learning and review surface. The course does not grade how much code Gemini generated. It grades whether your learning objective, game loop, feedback, observable traces, and revision decisions are visible and defensible.

Editorial illustration of a learner moving from a game prototype and loop diagram to playtest evidence and a submitted folder.
Generated teaching visual: build a minimal loop, inspect it in the browser, collect evidence, and submit the design argument.

1. Prepare the build brief

  1. Copy the D2 objective-to-mechanic crosswalk into a short build brief.
  2. State one learner, one target behavior, one game loop, and one success signal.
  3. Ask AI Studio for the smallest playable web prototype, not a full product.

2. Build and inspect

  1. Open Google AI Studio and use Build mode.
  2. Read the generated files in Code and test the live preview with keyboard and pointer.
  3. Keep the public preview or exported GitHub project link. Never put an API key in a submission.

3. Playtest the artifact

  • Run the smallest loop from prediction to action, feedback, and revision.
  • Capture a short screen recording plus two or three stills that show the game state.
  • Separate observed behavior from your interpretation and label rehearsal runs honestly.

4. Submit a reviewable packet

  • Submit the game URL and repository/export URL in D3/D5.
  • Attach the crosswalk, playtest notes, audit, AI provenance, and revision log.
  • Use the TeachPlay portfolio page to attach one artifact per deliverable, then submit for instructor review.
Build a five-minute educational game prototype from the attached objective-to-mechanic crosswalk. Keep one learner decision, one meaningful feedback state, one revision path, and a visible event trace. Use placeholder visuals if needed. Do not invent learning outcomes, learner data, or playtest findings.

Open the detailed AI Studio, Firebase, Workspace, Higgsfield, and Playwright playbook →

Completion model

How certificate handoff works

Official learner path

  • Student signs in with a course account.
  • Student completes the guided course and portfolio worksheets.
  • Student submits evidence for instructor review.
  • Instructor approves the submission against the rubric.
  • TeachPlay exposes the certificate and credential evidence.
  • Student completes the post-credential survey for program improvement and optional de-identified research use.

Survey after certificate request

After requesting the credential, students open the post-completion survey. It asks about module clarity, usefulness, workload fit, video and reading support, AI provenance, evidence artifacts, transfer plans, barriers, and optional research follow-up consent.

Open the post-completion survey

Instructor setup

What to tell students before they start

Minimum instructions

  • Use the same email account for every TeachPlay session.
  • Do not submit the final packet until all required evidence artifacts are ready.
  • Keep AI prompts, outputs, edits, and rejected ideas in the provenance log.
  • Use the 12-module sequence as the learning path. Use the portfolio checkpoints for evidence submission and completion review.

Evidence packet

  • D1 learner/context and learning problem
  • D2 objective-to-mechanic crosswalk
  • D3 prototype and facilitation guide
  • D4 playtest and audit evidence
  • D5 final defense and implementation packet

Instructor registration and management

Instructor access is provisioned through the protected Cloudflare Access policy. Add the instructor's approved email to the Access allowlist, then use the same identity to open the instructor console. The issuer key remains a controlled back-office option and is never placed in learner instructions.

Use Admin dashboard for learner records, progress, evidence, scoring, and credential gates. Use Portfolio review for computational-artifact analysis and final review actions. Access approval is separate from learner enrollment, so instructors can manage many learner records without impersonating a learner.

FAQ

Common student questions

Do I need to code a full game?

No. A paper prototype, low-code prototype, or implementation specification can satisfy the credential if the learning loop, facilitation logic, AI governance, playtest evidence, and revision rationale are reviewable.

Why do I see 12 modules and portfolio checkpoints?

The 12-module sequence is the learning path. Portfolio checkpoints collect the evidence students produce across those modules for submission, review, and certificate readiness.

When do I receive the certificate?

The official certificate is available after authenticated submission and instructor approval. After requesting or receiving the certificate, complete the post-completion survey so the team can improve the credential and, with your optional permission, use de-identified responses for research reporting.

What should I do if my certificate says not found?

First confirm that you are signed in with the same account used for the course. Then confirm that your final evidence packet was submitted and approved. If both are true, contact the instructor or program administrator.

Assets

Download or reuse the walkthrough materials