Audience: anyone new to Blender through experienced makers seeking a structured portfolio project. Structure: one course with three six-week paths. Start at the path you can demonstrate; you need not complete all 18 weeks. Pace: three 30–45 minute sessions per week, with extra render time as needed. Cost path: free Blender, original work, and no required paid add-ons. Outcome: a saved editable .blend project, a clearly attributed final still or short animation, and a short process note; procedural variants are optional supporting evidence. “Advanced” names the course path, not a professional certification.
Use the official Blender Manual with the version installed. Its broad sections cover navigation, modeling, materials, animation, and rendering. The exercises and progress gates here are Akari's proposed course design, not Blender Foundation requirements.
Pick a path and a project
Use a small desk scene as a shared through-line: a mug, book, lamp and simple surface. You may substitute an object or environment that matters to you. The subject is deliberately ordinary so geometry, light, composition and workflow are the learning targets.
- Beginner entry: you cannot yet orbit, select, transform, save and re-open a simple scene confidently. Start with the beginner path.
- Intermediate entry: show a saved scene with at least three distinct modeled objects, organized names, materials, a camera and a render you can revise. If any of these are missing, use the relevant beginner lesson first.
- Advanced entry: show an editable scene with a deliberate modifier or node workflow, a reasoned procedural-material versus UV/texture decision, organized collections, and a reproducible render. If that evidence is thin, begin at intermediate.
No one must “pass” a formal test to enter; the diagnostic simply identifies what to review. A learner can move between paths as needed.
Prerequisites and setup
You need a computer that can run the installed Blender version, permission to save project files, and a mouse, trackpad or usable alternate input. A second monitor, drawing tablet, paid add-ons and prior 3D experience are not required for the beginner path. Intermediate and advanced entry evidence appears above. If rendering is slow, use viewport captures and low-cost previews for the weekly checks, then choose a feasible final output.
- Install Blender from blender.org and make a folder with subfolders for project files, renders, references and credits. Save a versioned .blend file at the end of every session.
- Read the manual's Getting Started and 3D View navigation pages. If a shortcut differs, use the manual for your installed version rather than forcing a memorized key.
- Gather three visual references you have the right to use. Keep their links/creator names. Reference is for observation; final assets should be original or licensed for the intended use.
- Choose one final output: a still image or short animation at any level. Advanced learners may also show a procedural variant as supporting evidence, not as a substitute for the final output. Export settings and render time depend on the computer; no specific hardware or speed is promised.
Daily studio loop: 5 minutes open/review last file; 5–10 minutes read a focused manual section or inspect a reference; 20–25 minutes change one feature; 5 minutes save a version, make a viewport capture or low-cost preview, and note the next step. At the end of each week, compare the artifact with the stated objective, not just with a polished tutorial image.
Beginner path: six weeks from blank scene to a clear render
| Week | Objective and exercise | Checkpoint evidence |
|---|---|---|
| B1: navigate and save | Practice orbit, pan, zoom, select, move, rotate and scale in the 3D View. Place simple primitives for desk, mug and book; name each object. Save, close and reopen. | Reopened file has named objects in intended positions; learner can point to each transform control. |
| B2: edit geometry | Use modeling basics to modify one primitive into a recognizable mug or lamp. Compare object-level transform with editing the mesh. Keep a duplicate before a risky edit. | Object silhouette is recognizable from two viewpoints; learner can explain one edit versus one transform. |
| B3: organize and refine | Put objects into sensible collections; adjust scale and spacing using reference. Add only the detail needed to distinguish objects. If a modifier helps, try one and compare before/after via the modifier overview. | Scene remains editable, named and uncluttered; a peer can identify the focal object. |
| B4: materials and color | Give each object a purposeful material using the materials section. Change roughness and color one at a time, then make a preview. | A viewer can distinguish main materials without relying solely on color; learner can describe how one material change affected the image. |
| B5: light and camera | Frame the scene with one camera and add light so the focal object reads clearly. Use the rendering section to compare a low-cost preview with a final-quality attempt. | Focal object is visible and not accidentally clipped; before/after previews show one deliberate lighting or framing revision. |
| B6: final still and reflection | Render a still, keep the .blend, export the image, add source credits and a 150–250 word note on three decisions and one next improvement. Ask one viewer what they notice first. | Final image, editable file, credits and reflection are present; viewer's first focal point matches or usefully challenges the intent. |
Intermediate path: six weeks of control and iteration
| Week | Objective and exercise | Checkpoint evidence |
|---|---|---|
| I1: scene audit and plan | Open your beginner scene or a comparable original scene. Identify geometry, lighting and composition problems. Make three small thumbnails with different focal hierarchy; choose one. | A written plan names the intended viewer attention and two changes that support it. |
| I2: non-destructive modeling | Use two appropriate modifiers to improve a repeated or curved form. Keep editable source objects and test how parameter changes affect shape. | Side-by-side views show what each modifier contributes; source geometry remains editable. |
| I3: UV/material decisions | For one focal object, decide whether a procedural material is enough or whether a texture needs UVs. Implement one route and explain why. Do not add textures merely to look advanced. | Focal object renders without obvious stretching or unintended material seams; provenance is documented. |
| I4: lighting comparison | Make two lighting setups with the same camera and materials. Compare readability, shadow shape and mood. Choose one based on the project goal, not solely on realism. | Two preview renders plus three observations explain the choice. |
| I5: motion or camera control | Choose one branch. Motion branch: use Animation & Rigging basics to keyframe a simple lamp/object or camera move. Still-image branch: make two static camera/framing previews and compare focal hierarchy; no animation required. | Motion: playback has a clear beginning/end without accidental jumps. Still: two labeled previews and a reasoned camera choice. Both preserve an editable scene. |
| I6: audience review and final | Show the image or short preview to two people. Ask what the scene communicates and where they look first. Revise one issue, export final, archive editable project and credit assets. | Before/after comparison, two observations, final artifact and one justified revision. |
Advanced path: six weeks of a reusable, intentional pipeline
Choose one advanced focus for the desk scene: (A) procedural arrangement of books/objects with Geometry Nodes, or (B) a controlled material-and-lighting look with materials and rendering. Do not blend both until the chosen focus works.
| Week | Objective and exercise | Checkpoint evidence |
|---|---|---|
| A1: brief and constraints | State audience, intended use, visual reference, output dimensions, time budget and asset rights. Save a baseline render and list three technical risks. | One-page brief and baseline render make the goal testable. |
| A2: reusable structure | Organize collections, names and source objects. Build the first modifier/node/material system for your chosen focus, with a small number of exposed controls. | Changing one control produces a predictable variation; the original remains editable. |
| A3: parameter testing | Create three controlled variants by changing one parameter family at a time. Record what changed and why one variant better serves the brief. | Three labeled previews and a concise decision log, not just a favorite image. |
| A4: robustness and reproducibility | Test the scene after reopening. Check missing assets, scale, visible artifacts and render consistency. If using external textures, package or document them according to the manual and your intended handoff. | A second open/render attempt reproduces the intended result; known dependencies are listed. |
| A5: critique and refinement | Show the result to two viewers, one focused on visual communication and one on editability/handoff if available. Prioritize one high-impact change; keep alternatives archived. | Critique notes identify observation, decision and revised output. |
| A6: portfolio handoff | Export final still or short animation, archive .blend and dependencies, provide credits and a one-page process case study: brief, variants, choice, outcome, known limits. | Another person can open the project, identify the controls and understand the final decision. |
Checkpoints and adaptations
At each path's weeks 2, 4 and 6, score no grade. Use demonstrated / partly demonstrated / revisit for: (1) the week's visible artifact, (2) ability to explain a decision, (3) a saved editable file and comparison or note. If two items need revisiting, repeat the exact lesson that supplies them before adding complexity. These are formative course gates, not external standards.
Capstone evidence and formative rubric
Keep in your own learning portfolio, not an ASU course submission: an editable .blend file, final still or short animation, at least one before/after or variant comparison, credits, and a short process note. Beginner evidence emphasizes navigation/modeling/materials/rendering; intermediate evidence adds controlled comparisons and one revision; advanced evidence adds a reusable system and reproducible handoff.
Use each criterion as 0 = not yet evidenced, 1 = partly evidenced, 2 = demonstrated with observable evidence. This optional self/peer scale is not an official grade. A practical revision target is 6/8 with no missing criterion; revise the lowest-scoring criterion before adding effects.
| Criterion | 0: not yet | 1: partly | 2: demonstrated |
|---|---|---|---|
| Visual communication | Focal object or intention cannot be identified | Intent is visible but framing, light or material choice obscures it | Viewer can identify focal point; decisions support the stated brief |
| Technical control | Scene cannot be reopened or changed predictably | Editable but disorganized or results vary unexpectedly | Named, editable scene demonstrates path-appropriate modeling/material/node control and reproducible output |
| Iteration evidence | No comparison or critique | One comparison or comment without a linked decision | Before/after, variant or audience evidence supports a specific revision |
| Handoff and provenance | Output, source file or credits missing | Present but dependencies or reasoning unclear | Final output, .blend, credits, dependencies and process note let another person understand and reopen the work |
The rubric values clear decisions, editability and evidence, not expensive hardware, photorealism or a particular shortcut. A still-image learner can meet every criterion without animation. These are course-designed criteria, not Blender Foundation certification requirements.
- If the interface feels overwhelming: hide unrelated editors, focus on one object and one transform, and use a printed shortcut card. The manual's version-matched navigation is the reference.
- If hardware is slow: use simple geometry and low-cost previews; defer complex effects and final renders. The design decision can still be evaluated from viewport captures.
- If mobility or shortcut use is a barrier: use menus/search and remappable inputs where available. As a concrete check, complete the B1 move/rotate/scale and save/reopen sequence without requiring shortcut chords; record the input route that worked. Success is the saved artifact and explanation, not a particular keystroke.
- If a tutorial makes everything look effortless: pause after each action, predict its effect, do it on your own scene, and note what differs. Copying clicks without a decision is not the checkpoint.
- If returning after a gap: reopen the last good version, reproduce one small result, then continue. Do not restart the whole path.
Source and authorship note
Software operations and topic taxonomy come from the Blender Manual, particularly navigation, modeling, modifiers, UVs, materials, animation, rendering, and Geometry Nodes. The three paths, pacing, project, review prompts, checkpoints and rubric are Akari's instructional design, not official Blender certification criteria.