HSV colors | Bezier and NURBS curves | Vector (font) scaling/rotating/etc. | Scene graphs | OpenGL lines API | OpenGL rectangles API | OpenGL texturing API | OpenGL rotation API | OpenGL colors API | GLUT (busywork to get 3D graphics on the screen) | JOGL (busywork to get 3D graphics on the screen) | SVG file format | 3D Model/View/Projection matrices | linear algebra | Lighting (from an OpenGL 1.0 perspective, which misses a lot of lighting theory) | OpenGL material API | OpenGL MipMaps API | More scenegraph, this time with camera and lights | How to do a bunch of stuff you already learned, this time in Three.JS instead of OpenGL | How to do meshes, in Three.JS instead of OpenGL | How to do fixed-function shadows, this time in Three.JS instead of OpenGL | The programmable pipeline (finally) | WebGL busywork to get something on the screen | GLSL syntax | texture units | 2D transforms, this time in GLSL instead of fixed-function | Lighting in GLSL | Textures in GLSL | Multiple framebuffers | deferred shading | ray tracing | path tracing
and feel as though you've taught a lot of stuff, but in reality it's not a honest simplification of later graphics knowledge.
I think that a better approach would be (1) Explain 3D math, linear algebra, etc. (2) Explain raytracing algorithms, show the student some simple raytracing code (3) Explain the basics of modern GPU-based rendering (4) Show the student some simple software-based raster rendering, which mimics what the GPU does (5) Explain the shader pipeline (6) Using WebGL (no need to teach three.js and OpenGL 1.0 also!), show the student all the various principles of 3D graphics, going into theory when appropriate.
Scenegraph? That's irrelevant. GLSL syntax? We don't need a comprehensive explanation, the documentation already does a better job than we would. We just need to cover enough to let them know what's possible. HSV color? Bezier curves? MipMaps? OpenGL 1.0 API in gory brutal detail? GLUT? JOGL? Those deserve a mention but not an entire section.