download the last version for windows ToDoList 8.2.6

Information on how to distill an episode’s key points, see the Developing Content chapter. (FIXME) with 3-7 major take-aways from the episode. For information on writing useful learning objectives, see the Developing Content chapter. (FIXME) with 3-7 learning objectives for the episode, each on a new line and in quotation marks. These motivating questions will appear in the schedule on the lesson homepage. Replace Key question (FIXME) with 1-3 motivating questions for the episode, each on a new line and in quotation marks.The lesson template creates a scheduleįrom these time estimates and places it on the lesson homepage. The episodes, but it is useful to have a starting point to benchmark from. Will likely be updated by Instructors as they get real-world data on how learners respond to the pacing of Enter an estimated number of minutes for teaching the episode and an estimated number of minutes for learners to spend completing challenge problems (including class discussion of challenge solutions).Title will appear on the episode page and in the schedule that appears on the lesson homepage. Replace Introduction with the episode title ( not the lesson title) in quotation marks.This section explains each component of the YAML header and what that information is used for.įor each episode, you will need to create a copy of this file and: Stored in the YAML header is used by the lesson template to populate important parts of the lesson webpage. The material between the first and second instances of - is called the YAML header. The content of this pre-made episode file is shown below:. You can use this file as a template for creating each of your episode files, as it provides anĮxample of how these files must be structured.

When your lesson repository is created, it will start out with one pre-made episode file ( 01-introduction.md).

D.4.1 After the Sprint: Recommendations for GitHub.

D.3.1 During the Sprint: Recommendations for GitHub.

D.2.1 Before The Sprint: Recommendations for GitHub.

C.5.7 (Recommended) Centralise Link References.

C Adapting Existing Lessons for The Carpentries.

A.3.1 Using Labels to Encourage Contributions.

7.8 The stable lesson: Maintenance and lesson releases.

7.4 Early development (pre-alpha through alpha).

6.3.1 Maintainer recruitment, requirements and time commitment.

4.4.4 Use the concept in a different context.

4.2 Formatting the dataset for teaching.

3.3 Example using a Software Carpentry Learner Profile.

1.2 Creating a narrative and selecting a dataset.

1.1.3 Planning the content of the lesson.

1.1.2 Designing challenges to assess understanding.

Download the last version for windows ToDoList 8.2.6