Final project updates (#489)

* Replaced stock photo with Maker Component Close-Up

* Fixed missing Mini-Project images

* Corrected wording, added details.

Changed pxt to MakeCode, added a new row to rubric about variables, and
added an explanation of the flexibility of the rubric to the bottom.

docs/courses/csintro/finalproject.md

@@ -1,11 +1,11 @@
 # Final project
 
+![micro:bit holder square](/static/courses/csintro/conditionals/microbit-holder.jpg)
+
 In this unit, we will be reviewing the concepts we covered in the previous weeks, and providing some ideas for an independent final project that students can focus on in the next several weeks. We will also provide a rubric for keeping students on task and tracking the learning that they are doing as they work on their projects. This is an expanded version of the process students followed in the [Mini-Project](/courses/csintro/miniproject), in Lesson 6. 
 
 Students are asked to create an independent project that demonstrates the use of something they have already learned, something they went out and researched for themselves, something they borrowed from somewhere else (with citations) and something completely original. They are also asked to document their learning process throughout the next couple of weeks using an independent project framework that emphasizes metacognitive development and process-oriented work.
 
-![Puzzle](/static/courses/csintro/finalproject/puzzle.jpg)
-
 ## Lesson plan
 
 1. [**Review**: Review of lessons 7 - 11](/courses/csintro/finalproject/review)

docs/courses/csintro/finalproject/project.md

@@ -52,7 +52,7 @@ Sample Work Log:
 3/31: 45 min. Worked on attaching cardboard arm to servo and mounting servo to inside<br/>
 4/1: 30 min. Looked up documentation on talking to NeoPixel strip, worked through demos<br/>
 4/3: 45 min. Hot glued NeoPixel strip to outside of dinosaur, finished painting<br/>
-4/4: 30 min. Coded lighting patterns in pxt._
+4/4: 30 min. Coded lighting patterns in MakeCode._
 
 **Teacher note:** We generally don't accept late work logs. If a student simply didn't have time to do any work on the project, he should still file a work log, and report that no work got done. Work logs are worth a few points each, so missing one or two isn't a problem, but if it happens a lot it's usually time to do a check-in with that student and see where she is with the project.
 
@@ -145,6 +145,13 @@ We have found that a "science fair" format works nicely, with students sitting a
 **2 =** Code somewhat effectively demonstrates the use of new concept(s). Only some variable names are unique and/or clearly describe what information values the variables hold. Code is somewhat efficient.<br/>
 **1 =** Code demonstrates the use of new concept(s), yet is not effective. Few or no variable names are unique and/or clearly describe what information values the variables hold. Code is not efficient.
 
+### Variable names
+
+**4 =** All variable names are unique and clearly describe what information values the variables hold.<br/>
+**3 =** Most variable names are unique and/or clearly describe what information values the variables hold.<br/>
+**2 =** Only some variable names are unique and/or clearly describe what information values the variables hold.<br/>
+**1 =** Few or no variable names are unique and/or clearly describe what information values the variables hold.<br/>
+
 ### Maker component
 
 **4 =** Tangible component is tightly integrated with the micro:bit and each relies heavily on the other to make the project complete. <br/>
@@ -167,3 +174,4 @@ We have found that a "science fair" format works nicely, with students sitting a
 **2 =** Reflection piece is superficial and lacks 2 of the required elements.<br/>
 **4 =** Reflection piece is trivial and lacks 3 of the required elements. 
 
+As always, these rubrics are just a starting point and you should certainly feel free to adjust them as appropriate for your own classroom or learning environment.

docs/courses/csintro/miniproject.md

@@ -1,13 +1,13 @@
 # Mini-project
 
+![Ideas](/static/courses/csintro/miniproject/problem-solving.png)
+
 In this unit, we will be reviewing the concepts we covered in the previous weeks, and providing some ideas for an independent “mini-project” students can focus on in the next several classes. We will also introduce a framework for keeping students accountable to the work they are doing individually and in groups, and providing a rubric for assessment of the development process, as well as the finished product.
 
 It is important to allow students to practice accounting for the work they are doing on a short “mini-project” like this, so that when they move on to an independent project spanning multiple weeks, it will be easier for you to keep track of what everybody is doing.
 
 It also reinforces the important idea that how you solve problems is at least as important to learning as whether you solved them at all (or even got the right answer). Programming is a process of patient problem-solving, and finding ways to value, acknowledge, and reward the problem-solving process is an important part of assessment.
 
-![Ideas](/static/courses/csintro/miniproject/ideas.png)
-
 ## Lesson plan
 
 1. [**Review**: Looking back at what we've learned so far](/courses/csintro/miniproject/review)

docs/courses/csintro/miniproject/review.md

@@ -1,6 +1,6 @@
 # Review
 
-![Take another look](/static/courses/csintro/miniproject/review.jpg)
+![Take another look](/static/courses/csintro/miniproject/review.png)
 
 Take this time to review the concepts we have covered so far.