Build a technical lesson that a learner can finish

The EDUCATE teacher manual (version 0.9, 3 August 2007, third draft) and the eleven-page publishing guide describe an earlier teaching platform. Their module–lesson–activity structure remains useful as a design question; their buttons and addresses are not current operating instructions.

New explanation and worked examples by the editorial team.

The diagram in words: One outcome → A task with visible criteria → Learner-view release check.

Keep the lesson structure inspectable

The publishing guide separates the programme, modules and lessons, then connects lesson material with activities and supporting resources. Start with one outcome and decide what evidence would demonstrate it. A large folder of slides is not a complete lesson if the learner cannot identify the task or expected product.

A complete fictional lesson card

Outcome: distinguish rainfall volume from discharge. Resources: readable data with units and a short explanation. Task: calculate volume for 100 mm over 2 km² and identify missing information for discharge. Product: conversions, arithmetic and a limit statement. Feedback: name the first incorrect reasoning step and offer a new pair of inputs.

Release as the learner will see it

Check access to the brief, resources, criteria and final submission state. Use a learner-view route provided by the current platform; do not infer access from an editor’s view. Make essential information readable outside a screenshot and supply an alternative for any inaccessible media. These checks do not require bringing the old platform back into service.

Preserve a revision record

Save the lesson identifier, version, resource names, source dates, criteria and reviewer. If a field changes, say which learner-facing task is affected. Before the next release check that the links still point to the same resources. The original manuals establish their period and roles; the lesson card and checking procedure here are new editorial work.