Project Ops

[Title]

Project operations source: [Title].

Audience

Name the learners, participation setting, expected background, and meaningful ways to take part. Do not use age as a proxy for ability or interest.

Explain self-study, Zoom, and in-person use where applicable. In facilitated sessions, demonstrate an example, then let learners practice individually, in pairs, or in groups. A shared question is valid; define what learners must decide or do beyond watching. Keep reviewer context, known gaps, and review scope in the package README, with learner-facing instructions here.

Purpose

State why this module exists in one clear paragraph. This paragraph becomes the page summary.

What Do You Need

Keep this section only when the module needs preparation guidance. It may cover session format, prior knowledge, devices or accounts, materials, privacy or safety preparation, and participation options.

[Teaching Section]

Shape the teaching core around the module. Learning Outcomes, Core Ideas, a session outline, reflection, a hands-on activity, and a take-home artifact are optional rather than universal boilerplate.

Add, rename, combine, or remove teaching-core sections as the material requires. Track pages—not module pages—own sequencing between modules. Generated resource cards provide related labs and learning-map relationships.

Tool Boundary

State whether AI or another tool is optional, what alternatives can meet the learning goal, and where human authority remains.

Privacy Boundary

State what material is safe to use and what disclosure, account, upload, recording, or third-party information is not required.

Review Boundary

State the lifecycle and pilot status, what automated checks establish, and what still requires human or learner review.


Source: templates/module-template.md