Assignment Link Updates

Author: Mark Fitzgerald

.DS_Store

@@ -0,0 +1,78 @@
+# Code 201: Foundations of Software Development
+## Weeks 1-2 night and weekend track:
+### Introduction to Web Development
+**Instructors & TA's**
+
+*Lead Instructor*: Mark Fitzgerald
+
+*TA*: <to-be-determined>
+
+##Week 1 - Daily Plans
+###Class 01
+1. Intro to Code Fellows
+2. Introductions
+
++++BREAK+++
+
+3. Intro to Dev Env (Tool Belt & Browser basics)
+4. Intro to User Stories
+5. HTML & JS Basics (Hello World)
+
+###Class 02
+1. HTML Basics
+  1. Links
+  2. Images
+
++++BREAK+++
+
+2. JavaScript Basics
+3. Debugging Basics
+
++++BREAK+++
+
+4. Git & GitHub
+
+###Class 03
+1. Code Review
+2. Control Flow
+3. Logical Operators & Counters
+
++++BREAK+++
+
+4. HTML Lists
+5. HTML Tables
+
++++BREAK+++
+
+6. Github Branches
+7. Separation of Concerns
+8. README.md / Documentation
+
+##Week 2 - Daily Plans
+###Class 04
+1. Code Review & Survey Comments
+
++++BREAK+++
+
+2. Functions
+3. Introduction to CSS
+4. Color
+
++++BREAK+++
+
+5. Basic DOM Manipulation
+  1. getElementById
+  2. innerHTML
+
+###Class 05
+1. Code Review
+
++++BREAK+++
+
+2. JavaScript Arrays
+
++++BREAK+++
+
+3. CSS Box Model
+4. HTML Forms
+

week_1-2/.DS_Store

@@ -0,0 +1,26 @@
+# Week 1, Class 1
+
+# Reading Reminder
+
+* ["Structure" (HTML & CSS, Ch. 1)](https://canvas.instructure.com/courses/1176151/modules/items/13085606)
+* ["Text” (HTML & CSS, Ch.2)](https://canvas.instructure.com/courses/1176151/modules/items/13085607)
+* ["Process & Design" (HTML & CSS, Ch. 18)](https://canvas.instructure.com/courses/1176151/modules/items/13085608)
+* ["The ABC of Programming" (JavaScript, Ch.1 )](https://canvas.instructure.com/courses/1176151/modules/items/13085609)
+
+# Assignment for Class
+In class, we wrote a program that accepted user input and, based on that input, displayed a message back to the user. Your assignment in lab today involves a variety of different activities related to that.
+
+[Submit Your Work](https://canvas.instructure.com/courses/1176151/modules/items/13085610)
+
+## User Stories (MVP)
+ - As a developer, I want to use basic markup to structure my index.html page, so the layout is in the order of assembly I prefer
+ - As a developer, I want to receive and use the user's name, so that the program is personalized to their experience.
+
+## Technical Requirements
+ - Work will be done in an HTML file in Atom, and then submitted via Canvas (copy and paste into submission)
+ - Good use of HTML; e.g. 'body', 'doctype', 'p', 'head', 'html', 'h1', and 'title'
+ - HTML is cleanly written and indented for readability and organization
+ - JavaScript written to alert the user in a "Hello, World" type of script
+
+## Helpful Resources
+- [**Supporting Information**](support.md)

week_1-2/README.md

@@ -0,0 +1,33 @@
+# Supporting Information
+### Tool Belt
+If there are any lingering issues with the setup or functionality of your laptop and the software installations, we need to individually address that right away in lab. **Note**: Students using Linux or Windows should coordinate with the TA or Instructor who is the most experienced with those platforms (We will help identify those people).
+
+### Design
+Design a script (**without actually writing any code yet!**) for a simple "Hello, World" app.
+
+For all local file manipulation, use the Terminal and the Unix commands that you learned in class today.
+
+Next, create a file called index.html that has all of the primary components of an HTML document in the proper structure and order: 'body', 'doctype', 'head', 'html', and 'title'.
+
+Do by hand as a flowchart on a piece of paper (think of paper as a little personal whiteboard... what a concept!). You'll need these designs for the rest of the lab assignment.
+
+### HTML content!
+Add a new file to your folder called index.html (do this from the terminal) and create the basic HTML structure for this page using your basic building block elements (doctype, html, head, body, script, etc).
+
+Once the framework is in place, add new elements and content to your page for the following areas of information about you:
+
+- Name
+- Biography
+- List of Experience
+- List of Education
+- List of Goals
+
+Think about how readable your code is to other programmers. Be attentive to code style and conventions, as much as you know of them at this point.
+
+### JavaScript!
+Like we did we did in class, write JavaScript inside of script tags (placed at the bottom (inside) of the body), that does the following:
+
+- Receives user input through a prompt that asks “What is your name?” and stores that input into a variable
+- Returns an 'alert' box with a message that contains that user name somewhere in the middle (“Good to meet you, Homer, enjoy your doughnuts!” or the like)
+- Adapt the message to something different than what we did in class
+

week_1-2/class-01/.DS_Store

@@ -0,0 +1,32 @@
+# Week 1, Class 2
+
+# Reading Reminder
+* ["Links" (HTML & CSS, Ch. 4)](https://canvas.instructure.com/courses/1176151/modules/items/13085612)
+* ["Images" (HTML & CSS, Ch. 5)](https://canvas.instructure.com/courses/1176151/modules/items/13085613)
+* ["Basic JavaScript Instructions" (JavaScript, Ch. 2)](https://canvas.instructure.com/courses/1176151/modules/items/13085614)
+
+# Assignment for Class
+Today we will be using the code we wrote in the last class as an example for creating a guessing game project to which we'll be adding during the rest of the week. Use three personalized guessing game questions (The game will consist of three yes/no questions about you (example: "Did I grow up in South Dakota?")). Your end product will look very much like what we finished with in class yesterday, just customized. And if you want, extend it.
+
+[Submit Your Work](https://canvas.instructure.com/courses/1176151/modules/items/13085615)
+
+## User Stories (MVP)
+ - As a developer, I want to create a simple webpage, so that my users can interact with my game.
+ - As a developer, I want to provide three questions to the user, so that they can guess the answer and get to know me.
+ - As a developer, I want to notify the user after each question, so they are aware whether they were correct or not in their answers.
+ - As a developer, I want to debug my code using well structured console messages
+ - As a developer, I want to manage my code through an online version control system, so I have the ability to work with others and manage my revisions
+
+## Technical Requirements
+ - A Github Repo has been created for this assignment, and cloned to the local machine
+ - Directories and file structure are organized with best practices; e.g. Folder called "week_1-2" and file called "index.html"
+ - HTML and JavaScript are cleanly written with correct indentation and syntax
+ - Console.log messages are well written and correctly displaying to the browser console
+ - **Add, Commit, Push** process is being followed; evident in GitHub that commits are made regularly, and with good commit messages
+
+## User Stories (Stretch)
+ - As a developer, I want to add a fourth question that takes a numeric input, and indicates to the user whether the guess is 'too high' or 'too low'.
+
+## Helpful Resources
+- [**Supporting Information**](support.md)
+- [Try Git: Github's Git Leaning Tool](https://try.github.io/levels/1/challenges/1)

week_1-2/class-01/README.md

@@ -0,0 +1,48 @@
+# Supporting Information
+# Git
+#### Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency.
+
+### Git Commands:
+    git status              Provides a detailed description of current state in working directory
+
+    git checkout -- <file>  Remove all changes to file to the point of the last commit.
+
+    git add <file>          Include file in staged/tracked status of working directory
+
+    git reset HEAD <file>   Remove file from staged/tracked status of working directory
+
+    git commit -m ''        Snapshot the tracked changes in current working directory; with message
+
+    git push                Push local commits to GitHub
+
+
+##+++++Reminder: Add, Commit, Push (Git Workflow)+++++
+
+###Create a new GitHub Repository
+If you have not already, create a new GitHub Repository called guessing-game on GitHub, and clone that repository to your local computer. Your cloned repository folder should be inside your class assignments folder (codefellows or projects or whatever).
+
+###Scaffold your guessing game
+Inside of the guessing-game directory on your computer, create an index.html file or move your existing file to this folder.
+
+Make it look similar to the one we created in class today:
+- Place your three guessing game questions in prompts
+- Store the user input into a separate variable for each question
+- `console.log()` the response to each question with a useful message, like we did in class
+- In a sequence of alerts to the user, give a message repeating the answers that were given to the questions
+
+##+++++Reminder: Add, Commit, Push (Git Workflow)+++++
+
+###Respond to the user using if/else and 'alert'
+Design a script for an extended guessing game, which asks three questions using prompts, and responds to the user using alerts.
+  - The game will consist of three yes/no questions about you (example: "Did I grow up in South Dakota?")
+  - The questions will be presented in a 'prompt' with user feedback in an 'alert'
+  - Tell the user which questions they missed (such as "No, I did not grow up in South Dakota. I grew up in Alabama.")
+  - If they gave the correct answer, display a specific and personalized confirmation message in an 'alert' (such as "Yay! You got it right, Chris! I was indeed born in South Dakota!"), and if they gave an incorrect answer, display a specific and personalized alternate message (such as "No, sorry Chris, I was born in Liechtenstein, not South Dakota.").
+
+Do this for each of the three questions.
+
+###+++++
+
+Strive for clear and readable code style with proper indentation, line termination, and descriptive variable names.
+
+(If you want to extend this assignment, add a fourth question that takes a numeric input and then indicates to the user whether the answer is correct, too high, or too low. This part is not necessary for today, though... we'll cover it tomorrow.)

week_1-2/class-01/support.md

@@ -0,0 +1,37 @@
+# Week 1, Class 3
+[**Week 1 Feedback**](https://canvas.instructure.com/courses/1176151/modules/items/13085620)
+*You will receive an email from Code Fellows with a link to the survey. Once complete, please complete this assignment as well.*
+
+# Reading Reminder
+* [“Decisions and Loops” (JavaScript, Ch. 4)](https://canvas.instructure.com/courses/1176151/modules/items/13085617)
+* ["Lists" (HTML & CSS, Ch. 3)](https://canvas.instructure.com/courses/1176151/modules/items/13085618)
+* ["Tables" (HTML & CSS, Ch. 6)](https://canvas.instructure.com/courses/1176151/modules/items/13085619)
+
+# Assignment for Class
+Today we'll be extending/refining the guessing game and working from a GitHub branch.
+
+In your guessing-game directory, your HTML should be in a file called index.html, your JS in a file called game.js, and you should have a README.md file as well.
+
+[Submit Your Work](https://canvas.instructure.com/courses/1176151/modules/items/13085621)
+
+[Verify Your Understanding with a Quiz](https://canvas.instructure.com/courses/1176151/modules/items/13085622)
+
+## User Stories (MVP)
+ - As a developer, I want to work on a new branch in my repo, so I do not effect the state of my Master branch
+ - As a developer, I want to update my README.md file, so my repo is well documented and my sources are cited
+ - As a developer, I want to validate that my user input is in the correct format, so I can accept uppercase/lowercase or shorthand answers
+ - As a developer, I want to add a fourth question that takes a numeric input, and indicates to the user whether the guess is 'too high' or 'too low'.
+ - As a developer, I want to notify the user at the end of the game how many questions they guessed correctly, so they can celebrate their awesomeness.
+
+## Technical Requirements
+ - Work on a branch and push to GitHub
+ - Updated and cleanly documented README
+ - Implement a new form of control flow for the fourth question
+ - Implement counter to track right/wrong answers
+ - Logical Operators (and possibly string methods) used effectively
+
+## User Stories (Stretch)
+- As a developer, I want to add a fifth question to my game, which prompts the user to guess my number (hint: using a while loop) until they have guessed correctly
+
+## Helpful Resources
+- [**Supporting Information**](support.md)

week_1-2/class-02/.DS_Store

@@ -0,0 +1,31 @@
+# Supporting Information
+### Start today's work on a new Branch:
+We reviewed how to create and work from a branch during lecture today, so you'll start today by creating a new branch called class-03 for your work. To create a branch, starting from Master:
+
+`git checkout -b class-03`
+
+This will create a new branch (`-b`) and move to your new branch (`checkout`) at the same time.
+
+### We'll be doing a lot of add-commit-push today (a-c-p)
+    git add .     (Don't forget 'git status' to check your current state)
+    git commit -m "some kind of meaningful message about the code you are committing"
+    git push origin class-03   (REMEMBER: Do not push directly to master)
+
+Always think of writing code in a series of steps, making sure that everything works in one step before moving to the next one. After each step, add-commit-push your work with a brief but descriptive commit message. This gives you a preserved backlog of your work with a descriptive history. This is useful for looking back at your code to see where problems emerged. We will review your commit history and your commit messages, so be sure to be attentive to this step.
+
+## +++Add, Commit, Push+++
+
+###Add in error correction
+What if your user enters 'Y' instead of 'yes'? Or 'y' or 'YES'? Does your game still work correctly? It shouldn't. We need to build in some error correction. In your 'if' statements, where you are testing the user response, you need to add in && cases to your condition, such that Y/y/YES/yes or N/n/NO/no are all accounted for.
+
+## +++Add, Commit, Push+++
+
+###Add a counter
+After the three questions are finished, tell the user how many answers they got correct ("You got 2 correct answers out of 3 questions" or the like). You will need to manage some form of counter for this goal; e.g. track the amount of correct vs incorrect answers, or correct vs total answers, or...?
+
+Be sure to consider in your logic where the incremental counting should and does happen.
+
+### Update your README file
+Every repo needs a good README file. There's a lot of debate about what goes into a good README (take a look at http://stackoverflow.com/questions/2304863/how-to-write-a-good-readme), but at the least, you should have your name, the name of the project/assignment, a brief description of it, and citations to any code or sources you utilized in creating the code.
+
+When you've got a good README finished, add-commit-push your repo to GitHub. Remember... the TA's will be checking for these intermediate commits when evaluating your assignment!

week_1-2/class-02/README.md

@@ -0,0 +1,27 @@
+# Week 1, Class 4
+
+# Reading Reminder
+* ["Introducing CSS" (HTML & CSS, Ch. 10)](https://canvas.instructure.com/courses/1176151/modules/items/13085624)
+* ["Color" (HTML & CSS, Ch. 11)](https://canvas.instructure.com/courses/1176151/modules/items/13085625)
+* [“Functions, Methods & Objects” (JavaScript, Ch. 3)](https://canvas.instructure.com/courses/1176151/modules/items/13085626)
+
+# Assignment for Class
+Today we will be expanding our javascript to include functions so that we can execute code blocks more logically, and later on, in a more controlled manner.
+
+[Submit Your Work](https://canvas.instructure.com/courses/1176151/modules/items/13085627)
+
+## User Stories (MVP)
+ - As a developer, I want my code written in a modular way, so that I can reuse functionality without duplicating code.
+ - As a developer, I want my user to see the answers and responses on the web page, so we do not have to constantly interact with alerts.
+
+## Technical Requirements
+ - Updated and cleanly documented README
+ - Game functionality is encapsulated in functions
+ - Alerts have been removed from the game, and replaced by printing answers to the DOM.
+
+## User Stories (Stretch)
+- As a developer, I want to add a sixth question to my game, which has multiple possible answers (hint: using an array and for loop)
+- As a developer, I want to add some basic styling to my site, so that I can increase the happiness and engagement of my users (hint: do not use inline styling for this; you should link to another file for your styling)
+
+## Helpful Resources
+- [**Supporting Information**](support.md)

week_1-2/class-02/support.md

@@ -0,0 +1,12 @@
+#Supporting Information
+###Move logic into functions:
+As we demonstrated in class today, move the logic for the individual questions into separate functions, and call those functions to initiate the game. Use the code from class today as a model. After completing this step the game should behave exactly as it did before. **a-c-p**
+
+###Move the alerts into the browser window:
+Using the code from class today (`document.getElementById()`) as a model, move the alert feedback to the game player into `<p>`  or `<h2>` tags or similar that display in the browser window. **a-c-p**
+
+###Update the README file:
+Always take a look at your README file and see if it needs updating based upon your most recent work.
+
+###Code style:
+As always, strive for readable and maintainable code. Fix any issues with indenting and other code style, such as improving variable names and ensuring that line terminations are done properly. **a-c-p**

week_1-2/class-03/.DS_Store

@@ -0,0 +1,37 @@
+# Week 1, Class 5
+[**Week 2 Feedback**](https://canvas.instructure.com/courses/1176151/modules/items/13085632)
+*You will receive an email from Code Fellows with a link to the survey. Once complete, please complete this assignment as well.*
+
+# Reading Reminder
+* ["Extra Markup" (HTML & CSS, Ch. 8)](https://canvas.instructure.com/courses/1176151/modules/items/13085629)
+* ["Boxes" (HTML & CSS, Ch. 13)](https://canvas.instructure.com/courses/1176151/modules/items/13085630)
+* ["Forms" (HTML & CSS, Ch. 7)](https://canvas.instructure.com/courses/1176151/modules/items/13085631)
+
+# Assignment for Class
+Today you will be further extending your guessing game by working with CSS and colors. Once complete you'll be working to deploy your code to the interwebs!
+
+[Submit Your Work](https://canvas.instructure.com/courses/1176151/modules/items/13085633)
+
+[Verify Your Understanding with a Quiz](https://canvas.instructure.com/courses/1176151/modules/items/13085634)
+
+## User Stories (MVP)
+ - As a developer, I want to further apply D.R.Y. to my code, so that I do not have duplicate and unnecessary code.
+ - As a developer, I want to add some basic styling to my site, so that I can increase the happiness and engagement of my users.
+ - As a developer, I want to include images in my game, when the user guesses correctly, so that the game is more informative and fun.
+ - As a developer, I want to color code the answers on-screen, so my user can visually see what answers were right or wrong.
+ - As a developer, I want to host my game online so that anyone can play!!
+
+## Technical Requirements
+ - Proper syntax and refactoring when applying D.R.Y.
+ - Proper use of arrays and functions when applying DRY
+ - CSS stylesheet linked to html
+ - Basic CSS properties and values used, such as color, font-size, and font-family
+ - Images are correctly sized and styled
+ - Color properly applied on right/wrong answers
+ - GH-Pages deployment fully functional
+
+## User Stories (Stretch)
+ - As a developer, I want my site to look more professional, so my users will enjoy their experience (hint: Add more specific CSS styling to make more pretty)
+
+## Helpful Resources
+- [**Supporting Information**](support.md)