資源
TutorFlow Modules Overview

TutorFlow Modules Overview

Modules in TutorFlow are standalone lessons that live outside any course. Build one once, run it on its own, and copy it into as many courses as you need.

本頁內容

A TutorFlow module is a single lesson that lives outside any course. It has its own link, its own learners, and its own analytics, and you can copy it into any course in your classroom whenever a course needs that lesson.

At a glance

  • One lesson, no course around it. A module is complete on its own: a lecture, a coding exercise, a flashcard set, or a language drill that learners open from a link.
  • Copy to Course. A module goes into a course with Copy to Course. You pick the course and the position, and TutorFlow inserts a copy of the lesson there.
  • Copies are independent. After copying, the course has its own lesson. Editing the module later does not change the copy, and editing the copy does not change the module.
  • Most lesson types, not all. Modules support the lesson types below. Exams, games, simulations, and slide decks are made inside a course or as their own content type.

Lesson types a module can be

TypeWhat learners do
LectureRead explanation-first content with text, formulas, images, and media
Coding LessonPractise in an interactive IDE with explanation beside the editor
Coding TestSolve coding problems that are checked automatically
WebBuild and preview a web page in real time
Python NotebookRun Python cell by cell in a Jupyter notebook
Chat with AICompare AI models and practise prompt writing
AI tutorWork through a topic in a structured conversation with an AI tutor
FlashcardReview key concepts as an interactive card set
Dictation, Speaking, Roleplay, Reading, TranslationLanguage practice for listening, speaking, conversation, reading, and translation

An Exam is not a module type. Exams keep their problems inside a course, so a standalone exam becomes a Test instead. Game, Simulation, and Slides lessons point at a classroom asset, so they exist only inside a course. Make the asset itself from its own menu and link it from a course lesson.

Why modules exist

Many lessons do not belong to one course. A coding warm-up fits the beginner bootcamp and the data science track. An AI usage guideline is for every team. A lab safety briefing opens every science course in the school.

A module lets you build that lesson once, share it on its own link straight away, and copy it into each course that needs it. The alternative is rebuilding the same lesson by hand in every course, slightly differently each time.

When to use a module vs. a course

Use a module when...Use a course when...
One lesson stands on its ownYou are building a sequence with a start and an end
You want to share a single lesson by linkLearners need several lessons in order
You will copy the same lesson into several coursesThe content belongs to one cohort or program
You need a short, portable assetYou want course-level progress, exams, and certificates

Common examples of modules

  • Company policy introductions. Copied into every new-hire course.
  • AI usage guidelines. Shared with technical and non-technical teams alike.
  • Coding concept refreshers. A Python basics lesson copied into any course that assumes it.
  • Foundational language drills. The same dictation set reused in beginner and intermediate courses.
  • Lab safety instructions. One briefing copied into every STEM course.

How modules work with courses

Open a module and choose Copy to Course. A dialog lists your courses; pick one, then click the position in its curriculum where the lesson should go, or add it as the first lesson. TutorFlow copies the lesson content and its quizzes into that course.

From then on the two are separate lessons. If the policy changes, update the module for new copies, and update each course copy that is already published. Nothing propagates automatically, which also means a change for one cohort never leaks into another.

What TutorFlow modules are not

  • Not a content marketplace. You cannot browse or import modules made by other organizations.
  • Not a SCORM or xAPI package import. Modules are authored inside TutorFlow or generated from your reference material.
  • Not a linked or synced block. A copy in a course does not follow later edits to the module.

Next step