Skip to content

Network Whitelist Request — Friday Coding & AI Class

Send this in Week 1

Print or email this page to whoever manages the school network before you need it. A blocked site discovered at 9:05 on a Friday morning costs you the session. Discovered in August, it costs an email.


Request summary

Class: Friday Coding & AI resource class, grades 5–10 Meets: Fridays, 45 minutes, August 2026 – May 2027 Devices: School Chromebooks / laptops

The sites below are all free, education-focused, and used directly in class instruction. Most are already permitted under standard K-12 education filter categories. Please whitelist for student accounts on the school network.


Domains — required

These are used in scheduled lessons. A block here stops a class.

Domain Used for When
arcade.makecode.com Microsoft MakeCode Arcade — block/text game programming Weeks 1–8
makecode.com Parent domain for MakeCode assets Weeks 1–8
quickdraw.withgoogle.com Google Quick Draw — AI demonstration Weeks 1, 9
teachablemachine.withgoogle.com Google Teachable Machine — students train an ML model Weeks 10–11
code.org Code.org curriculum and activities Various
studio.code.org Code.org student activity environment Various
hourofcode.com Hour of Code activities Week 17 (December)

Domains — supporting

Used for reference, extension work, and backup activities.

Domain Used for
scratch.mit.edu Scratch — block programming (backup / extension)
dayofai.org MIT Day of AI — AI literacy activities
csunplugged.org CS Unplugged — printable no-computer activities
editor.p5js.org p5.js — creative coding (extension for advanced students)
khanacademy.org Khan Academy Computing (self-paced extension)
learn.microsoft.com Microsoft Learn — reference material
csteachers.org CSTA standards reference (teacher use)

Media & sub-resources

Domain Note
*.withgoogle.com Google's experiment platform — hosts the two AI demos above
*.makecode.com MakeCode asset and share subdomains
*.code.org Code.org subdomains

Specific technical requests

1. Camera access on Chromebooks

Weeks 10–11 need webcam access for teachablemachine.withgoogle.com. Students train an image classifier using the camera.

If camera access is restricted by policy, please let us know — there is a fallback (students upload images instead), but we need to know in advance so the lesson can be adjusted.

Privacy note for the record: Teachable Machine processes images entirely in the browser on the local device. No images are uploaded to Google, and nothing is stored. No student accounts are created and no data leaves the Chromebook.

2. Local storage / browser data

MakeCode Arcade saves student projects to browser local storage, not to an account. If the school policy wipes browser data on logout, student projects will disappear between sessions.

Please advise if this is the case — we can adjust our approach (students export project files instead).

3. No student accounts required

For clarity: Units 1 and 2 (August–December) require no student logins of any kind. Nothing to provision, no rosters, no data-sharing agreements. Any account creation later in the year will be discussed with administration first.


Quick copy-paste list

arcade.makecode.com
makecode.com
*.makecode.com
quickdraw.withgoogle.com
teachablemachine.withgoogle.com
*.withgoogle.com
code.org
studio.code.org
*.code.org
hourofcode.com
scratch.mit.edu
dayofai.org
csunplugged.org
editor.p5js.org
khanacademy.org
learn.microsoft.com
csteachers.org

Contact

Teacher: ___ Email: ___ Best time to reach me: _____

Thank you — happy to answer any questions about what these tools do or how they handle student data.


For the teacher — how to test before class

Run this on a student Chromebook (not yours — your account may have different policy), a few days ahead:

  1. Open arcade.makecode.com. Can you start a tutorial without signing in?
  2. Open quickdraw.withgoogle.com. Does a drawing round run?
  3. Open teachablemachine.withgoogle.com → Image Project → does it prompt for camera, and does the camera actually turn on?
  4. Make a MakeCode project, log out, log back in. Is the project still there?

Step 4 is the one people forget, and it's the one that ruins a multi-week project unit in October.