Skip to content

Instantly share code, notes, and snippets.

@aspencer8111
Last active May 21, 2017 17:18
Show Gist options
  • Save aspencer8111/f6f06c3e2aa8d6b0f78b3a91b1dbcf64 to your computer and use it in GitHub Desktop.
Save aspencer8111/f6f06c3e2aa8d6b0f78b3a91b1dbcf64 to your computer and use it in GitHub Desktop.
Suggested Curriculum Template

NOTE This template provides a structured and consistent way to create new checkpoints. Please do your very best to include/use each section of this template.

Overview and Purpose

In this checkpoint you _________________________.

Vocabulary

There are many new terms that you may not understand in this checkpoint. Take some time to really study each term and its definition below. Google each term. Make sure you understand it and have commited the definition to memory.

Objectives

  • Objective 1
  • Objective 2
  • Objective 3

After this checkpoint, you should be able to:

  • Use blah to do blah blah
  • Use blah with arguements to solve common blah problems

Why __________?

Why is the student learning this? How would this be used in the real world?

______ In Action

This is where we show, teach, explain how to do/use blah

Assignment

Put this new thing you learned into practice with the following exercise:

@wktdev
Copy link

wktdev commented May 12, 2017

I think "This checkpoint introduces you to" should be "In this checkpoint you" . I think the subtle difference will provide more flexibility for instructors to write an overview that can be more clear for students. For example: "In this checkpoint you create menu items for bloc jams" . "In this checkpoint you learn how to add interactivity to web pages". The way your phrasing is now seems to lean instructors toward writing overviews that sound more like "This checkpoint introduces you to event listenerss and how to add interactivity to web pages" and sounds less personable. I know the curriculum material I wrote does the same thing and I need to go back and fix it. Just a suggestion.

@aspencer8111
Copy link
Author

@wktdev - Updated. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment