Animation Unit | Facilitator Guide

What students learn

Students take one moment from a finished comic and rebuild it with motion. They learn how key poses, duplicated frames, frame holds, in-betweens, layers, timing, and loops change what an audience can understand. The final animation needs to show what people can count on the hero to do through a visible action.

What students make

• a promise-in-action statement and five-part micro plot;
• a six-panel storyboard, or an approved four-panel support storyboard;
• a 1 to 2 second Piskel practice loop;
• a first pass and work-in-progress checkpoint; and
• a final animated GIF, saved source file, and short reflection.

Production targets

Standard route: 10 seconds at 12 fps, about 120 displayed frames. Students use duplicated frames and frame holds; they do not draw 120 different pictures.

Support route: 5 to 8 seconds at 8 to 12 fps, a four-panel storyboard, and one clear motion with frame holds. Students still communicate the promise, test the work, revise one choice, save the source, and submit a working GIF. The support route uses the same rubric.

Before Day 1

• Open Piskel for Kids on the same Chromebook model students use. Confirm that the district filter allows the editor and downloads.
• Choose a district-approved storage location for editable .piskel files.
• Make sure students can open the visual Plot Diagram copy.
• Choose the default YouTube tutorial or set up the optional Edpuzzle route below.
• Preview the final rubric and decide which students need the approved support route.

Five-day route

1. Day 1, Adapt: Reopen the hero's promise, choose one visible action, and complete the micro plot.
2. Day 2, Plan and practice: Storyboard the motion, learn the Piskel controls, create a short practice loop, and save the editable source.
3. Day 3, Prototype: Build the starting pose, main action, result, and first complete pass.
4. Day 4, Refine: Adjust timing, add holds or in-betweens, test the work in progress, and make one specific revision.
5. Day 5, Finish: Test without explaining, make the last revision, export the GIF, verify playback, submit, and reflect.

Whole-group deck map

• Day 1: slides 1 to 14. Leave slide 14 up during Plot Diagram work.
• Day 2: slides 15 to 30. Leave slide 28 up for practice work or slide 30 up for the Practice Wall.
• Day 3: slides 31 to 39. Leave slides 38 and 39 up for production and the save routine.
• Day 4: slides 40 to 45. Leave slide 44 up for partner feedback and slide 45 up for the WIP checkpoint. The six-slide Day 4 loop can rotate during work time; pause it on loop slide 4 for feedback and loop slide 5 for the checkpoint.
• Day 5: slides 46 to 56. Leave slides 49 and 50 up during the gallery walk or slide 54 up for submission.

Plot Diagram setup

Default: Students open the Drawing copy link, complete their own copy, download it as a PDF, and upload the PDF to Canvas. This route continues to work after a course copy and does not depend on a roster connection.

Optional Google Assignments route: Make a teacher-owned copy of the Drawing. In the receiving Canvas course, link your school Google account, attach the Drawing, and choose the option that gives every student a copy. Test the student turn-in and return flow before publishing the assignment. Google's current setup instructions explain the course-linking step.

Piskel tutorial options

Default: The student page embeds the original Piskel tutorial. Students pause to try each control, then show what they learned in the Practice Wall.

Optional individual Edpuzzle: Open the reusable Piskel Edpuzzle and copy it to My Content. In Canvas, edit Day 2: Learn Piskel | Watch and Try, choose External Tool, select Edpuzzle, and attach the copied lesson. Save the assignment while it is still unpublished, then test the launch in Student View. The default YouTube version stays on the student page unless you intentionally replace it with this option.

Optional Live Mode: Assign the copied Edpuzzle to the class, open its assignment screen, and select Live Mode. Wait for every student to join before selecting Start; students cannot join after the session begins. Edpuzzle's Live Mode guide has the current limits and steps.

Edpuzzle states that previous Canvas classes and assignments cannot be reused, cloned, or imported as working course connections. Follow Edpuzzle's Canvas setup guide when you choose this route.

Portable WIP checkpoint

Default: students show the exported WIP to a partner or teacher, name the action the viewer saw, record one next step, and save the updated source file. No outside account or personal board is required.

Teacher option: if you want an online WIP board, create one in a district-approved tool, add your own link, and test student posting before you publish the module.

Source-file routine

Piskel keeps periodic recovery sessions in the browser, but that recovery stays with the browser and device. At the end of Days 2, 3, and 4, students download the editable .piskel file and move it to district-approved storage. They save the source again before the final export on Day 5. The GIF is the viewing copy; students cannot use it to continue editing the project.

What to watch while students work

• A long animation with no visible action is not stronger than a short, readable one. Move students to the support route before they fall behind.
• Students often change too much between frames. Model one small change, preview it, then decide whether another in-between is needed.
• When motion looks too fast, duplicate frames at the pose the audience needs time to read.
• Ask students to play the animation without explaining it. The viewer's first description is the clearest check on whether the promise can be seen.
• Do not wait until Day 5 to check source files. A working GIF does not replace an editable project.

Assessment

The Promise, Plot Diagram, Storyboard, tutorial, and Practice Wall are formative checks and do not change the final grade. The final animation is one 100-point Major grade:

• Promise communicated through action: 25
• Motion, timing, and ending control: 25
• Visual clarity and connection to the hero: 20
• Planning, feedback, and revision: 20
• File management, export, and reflection: 10

Before publishing the module

1. Keep the module itself unpublished until you decide to teach it.
2. Test Piskel, the Plot Diagram copy link, tutorial playback, GIF discussion posts, final GIF upload, and submission comments in Student View.
3. If you choose Google Assignments or Edpuzzle, reconnect and test that course-specific integration before students see it.
4. Confirm that every student-facing item you plan to use is published. Teacher guides remain unpublished.