What a course is
A lesson teaches one idea in a few minutes. A course teaches a whole subject. It is a set of units (chapters), and each unit is a short list of items: lessons, simulations, circuits, quizzes and built-in lab lessons, in the order readers should meet them.
A course doesn't copy its items: it points to them. Each lesson or simulation stays a post of its own, with its own votes and comments, and can be used in several courses. When its author improves it, every course that uses it gets the better version.
The Civil engineering from scratch course is a full example: 13 units and 45 lab lessons.
Quick start
- Write the outcomes first: two to six things readers can do after the whole course.
- Sketch the units on paper: one goal each, three to seven items each.
- Make the pieces that don't exist yet. Write lessons, and post the simulations and circuits readers will practise on (new simulation, new circuit; see the simulation and circuit guides).
- Build it. Open Build a course, fill in the promise, add units, and use + Add to this unit to search for items and add them. Your own posts are listed first.
- Check the preview and the checklist, then publish. The preview is the real course page. Moderators review new courses from most members, as with other posts.
Your work is saved on this device as you type. Items you add can be moved between units with โ โ, and each can carry a short note to readers, such as "Focus on the second graph".
Design it backwards
Experienced course designers start at the end. This is backward design (Wiggins and McTighe):
- Outcomes: what should readers be able to do at the end? "Design a beam that is safe and stiff enough" is checkable. "Understand beams" is not.
- Evidence: which activities will show they can? Usually a simulation, circuit or lab lesson where they do the real thing. Put these at the end of each unit, and a bigger one at the end of the course.
- Teaching: only now choose the lessons that prepare readers for that evidence. Anything that doesn't serve an outcome can go.
Why: it keeps a course focused. Courses designed front-to-back tend to cover everything the author knows; courses designed backwards teach what readers need.
Units
- One goal per unit, written as "after this unit you canโฆ". It appears under the unit title and tells readers why these items belong together.
- Three to seven items. Small enough to finish in a sitting or two, so readers feel progress; split anything bigger.
- Inside a unit: teach, practise, apply. A lesson or two first, then practice with feedback (a quiz or an easy simulation), then a task that uses it (a harder simulation, a circuit, a lab puzzle).
- Across units: simple to complex. Put what a later unit needs earlier. Come back to big ideas in later units with harder cases (a spiral): reactions in unit 1, again in trusses, again in buildings.
- An introduction (optional) links a unit to the last one: "You can now find the forces on a beam. Next: will it break?"
What goes in a unit
| Item | What readers do | Use it for |
|---|---|---|
| Lesson | Step through explanations, guesses, questions and calculations; may include a Try it step | Teaching each new idea |
| Simulation | Set values in a 3D physics scene and run it until it meets the requirements | Practice and challenges where the idea must work for real |
| Circuit | Build or fix a circuit in a live simulator | Electronics practice and challenges |
| Quiz | Answer a multiple-choice question, with feedback on each wrong choice | Quick checks between lessons, and reviewing earlier units |
| Lab lesson | A guided lesson inside one of the site's built-in labs, such as the beam or bridge lab | Rich, hands-on topics the labs already cover |
Mix them. Alternating reading, guessing, calculating and simulating keeps attention, and each kind practises the idea a different way.
Simulations and circuits
There are two ways to put a simulation or circuit in a course:
As an item in a unit
Add the simulation or circuit post to the unit like any lesson. Readers open it from the course page, solve it, and it is ticked off. Best for practice and challenges after the lessons.
Inside a lesson, as a "Try it" step
In the lesson editor, add a Try it step and search for the post. It appears inside the lesson, and the lesson continues once the reader solves it (or reveals its solution). Best when readers should discover the idea by experimenting, right before you explain it.
Give every simulation a clear task. "Change the thrust until the rocket flies straight, and watch the angle" works better than "Play with the simulation". Newcomers left to explore freely tend to learn little (guided discovery beats pure discovery). In a Try it step, use the What to notice box to say what the activity showed.
The simulation or circuit is graded by its own checker, exactly as on its own page, and a correct answer counts towards its accuracy statistics as usual.
Order
- Guided (the default): the course page highlights the next item, and items further on ask "This course suggests finishing โฆ first. Open anyway?" Choose this when each item builds on the one before.
- Free: readers pick any item. Choose this for independent topics, or a reference collection readers dip into.
Even in guided order nothing is ever truly locked: adults learn best when they can choose, and a reader who already knows unit 1 shouldn't be stuck there.
What readers see
- The course page: your summary and outcomes, who it's for, the total time, a progress ring, and a Continue button that opens the next unfinished item. The units are a path down the page; the current one is open, finished ones are ticked.
- A course bar on every item: opened from the course, each lesson, problem or lab lesson shows "Unit 2: Trusses ยท 3 of 5" with Next at the top and again at the bottom, so readers never have to go back to find their place.
- Progress is saved to the reader's account: solved problems, finished lessons and lab lessons show as done on any device they sign in on. Readers who aren't signed in keep their progress in their browser.
The checklist
Beside the editor, a checklist reads your course as you build it. Its warnings are advice; you can publish anyway.
| Warning | What to do |
|---|---|
| Add the outcomes / make one checkable | Two to six, each starting with a verb such as explain, calculate, design or choose. |
| Say who it is for | The audience and what they need first. |
| A unit has no goal | Write "after this unit you canโฆ" for it. |
| A unit has more than 7 items / a single item | Split it, or merge it with a neighbour. |
| The course opens by teaching | Make the first item a lesson or lab lesson. |
| A unit has nothing to do | Add a lesson with questions, a quiz, a simulation or a circuit. |
| Add something hands-on / end with a challenge | Add a simulation, circuit or lab lesson, ideally a harder one at the very end. |
| Mix kinds of activity | Don't build a whole course from one kind of item. |
| Over 20 hours | Split it into two courses, or part 1 and part 2. |
| Items awaiting review | Readers can open them, but they aren't in the feed until a moderator approves them. |
The server refuses only what would break the course page: no summary, no outcome, a unit with nothing in it, the same item twice, or an item that no longer exists.
After publishing
- A course is a post like any other: people can vote on it, comment on it and save it.
- Edit it with Edit post on the course page: add units, reorder, swap items. Readers keep their progress, because it belongs to the items, not the course.
- If an item is deleted or rejected, the course shows it as unavailable, and the editor asks you to remove it before the course can be saved again.
- Read the comments on your items. A lesson many readers abandon needs splitting or an example, wherever it is used.