Skip to content

Instantly share code, notes, and snippets.

@lizTheDeveloper
Last active December 5, 2016 20:34
Show Gist options
  • Save lizTheDeveloper/e62c7af890c2c1b0db43b1a725a2286b to your computer and use it in GitHub Desktop.
Save lizTheDeveloper/e62c7af890c2c1b0db43b1a725a2286b to your computer and use it in GitHub Desktop.

##New Article Title

This paragraph briefly explains what the article is about.

###Standard List the standard(s) covered in this article

###Objectives

  • List the objectives of the article
  • Make sure that all objectives are covered in the article
  • You will call students to reflect on the objectives in the article, so make sure they can easily find where each is covered
  • These should be links to headers, if appropriate

####Why? This paragraph explains why this is important. It establishes a narrative about why we're learning it, and why we're learning it now. The "why" section also gives a broader context into the overall picture, and where this piece of info fits in.

###Vocabulary This section should go over new words introduced to the students in the article. The first usage of the word in the article should link here

  • Vocabulary Word - A Definition goes here
  • Defninition Sometimes definitions will require images or longer explainations. Put them on a newline here.

###Article

This is where you talk about the topic. Explain it with a few paragraphs, make a few analogies.

Most of the time, you'll want to include a few short code snippets followed by a description of them.

You'll also want to include larger code blocks

Encourage students to run the code in these code blocks

Asking questions (that aren't answerable without running the code) directly after a code block is a great way to make sure they get run.

####Subheaders Subheaders are great ways to call out to the objectives, keeping your content aligned with objectives and standards.

  • You can add Objectives as bullet points right after the headers

Have an inline CFU near objective call-outs

Checks for Understanding

These are questions, short activities, and other small tasks that will verify that students understood the content of the article.

Below are some examples for inline checks for understanding.

!challenge

  • type: short-answer
  • title: get elements
  • id: 126
!question

What is the method for finding elements in the document object by their id attribute?

!end-question
!placeholder

Write out the full method name, with proper capitalization

!end-placeholder
!answer

document.getElementById()

!end-answer
!explanation

Great! Calling this method with the string value of an ID in the document will return exactly one DOM element from the tree.

!end-explanation

!end-challenge

!challenge

  • type: number
  • title: how many elements
  • id: 127
  • decimal: 0
!question

How many elements are returned by document.getElementById()?

!end-question
!placeholder

Write your answer as a number, rather than as text

!end-placeholder
!answer

1

!end-answer
!explanation

Exactly, there should only ever be a single element with a specific ID.

!end-explanation

!end-challenge

Have students reflect at the end of the article to help them feel confident that the article helped them successfully understand.

Exercise

Crucially, students should always have an exercise to go through to practice what they have just learned. Make sure that the exercise covers all the objectives, and meets the standard.

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