curriculum and challenge names updated

readme.md

@@ -6,11 +6,12 @@ Welcome to Phase 0! Below you will find links to the curriculum for each week. E
 ### [Week 2: More HTML/CSS](week_2)
 ### [Week 3: JavaScript](week_3)
 
-## Unit Goals
-- [Peer-Pair program](https://github.com/Devbootcamp/phase_0_handbook/blob/master/peer-pairing_sessions.md) at least 3 times with people in your accountability group. Read about [pairing](https://github.com/Devbootcamp/phase_0_handbook/blob/master/pairing_in_phase_0.md) before hand. 
+## Unit Requirements
+- [Peer-Pair program](https://github.com/Devbootcamp/phase_0_handbook/blob/master/peer-pairing_sessions.md) at least 4 times this unit. Read about [pairing](https://github.com/Devbootcamp/phase_0_handbook/blob/master/pairing_in_phase_0.md). 
 - [Submit feedback](https://socrates.devbootcamp.com/feedback/new) for all pairing sessions. (You should submit at least 3 for peer sessions and 2 for [GPS 1.1 and 1.2](https://github.com/Devbootcamp/phase_0_handbook/blob/master/guided_pairing_sessions.md))
 - [Rate Feedback](https://socrates.devbootcamp.com/feedback) at least 20 pieces of other people's feedback. 
 
 #### How to navigate this repository
 If you would like to open tabs in a new window, please either right click or hold command while you click. 
 
+

week_1/4_beginning_HTML_CSS/readme.md

@@ -69,4 +69,4 @@ Create a new css file in your repository called `dbc1.css` and save it to the `s
 
 
 ## Release 4: Reflect 
-On your local `phase_0_unit_1` repo, edit the [my_reflection.md](./my_reflection.md) file associated with this challenge. Commit your changes and save them to GitHub. 
+On your local `phase_0_unit_1` repo, edit the [my_reflection.md](my_reflection.md) file associated with this challenge. Commit your changes and save them to GitHub. 

week_1/5_HTML_CSS_solo_challenge/readme.md

@@ -61,7 +61,7 @@ Add the following to `dbc2.css`:
 
 
 ## Release 2: Reflect
-On your local `phase_0_unit_1` repo, edit the [my_reflection.md](./my_reflection.md) file associated with this challenge. Commit your changes and save them to GitHub. 
+On your local `phase_0_unit_1` repo, edit the [my_reflection.md](my_reflection.md) file associated with this challenge. Commit your changes and save them to GitHub. 
 
 <hr>
 

week_1/8_technical_blog/readme.md → week_1/6_technical_blog/readme.md

@@ -36,5 +36,5 @@ Copy the code from your blog template to a new HTML file called `week1_technical
 Write a blog post analyzing the 3 sites in terms of user experience and design.  Add a link to the `index.html` file for your new blog post! Don't forget to sync your changes to make them live on your github.io site!
 
 ## Release 3: Reflect
-On your local `phase_0_unit_1` repo, edit the [my_reflection.md](./my_reflection.md) file associated with this challenge. Commit your changes and save them to GitHub. 
+On your local `phase_0_unit_1` repo, edit the [my_reflection.md](my_reflection.md) file associated with this challenge. Commit your changes and save them to GitHub. 
 

week_1/7_cultural_blog.md

@@ -0,0 +1,25 @@
+[Week 1 Home](./)
+
+# U1.W1: Cultural Blog: Chefs in the Kitchen
+
+## Learning Competencies
+- Consider DBC's culture and approach to learning
+- Predict how you will react to DBC's approach
+
+## Release 0: Copy your Blog Template
+First, create a new HTML file for your this post in your [USERNAME].github.io website. Create a new HTML file and use the date to name it `week3_cultural_blog.html`. Copy the Code from your `blog_template`.  
+
+## Release 1: Kitchen vs. Table
+Watch [Shereef's Fireside Chat](http://vimeo.com/85001014)
+
+## Release 2: Write your Blog!
+Based on the video, what's your take on the DBC experience? What is your impression of DBC? How do you see yourself engaging with this type of culture?
+Have your expectations of DBC changed? If so, how? Are you excited to participate in this kind of learning environment? Does it make you nervous? 
+
+Talk about what came up for you and anything you want in addition to the questions above. 
+
+
+## Release 3: Submission
+Link to your blog on the index of your github.io site and sync your changes. 
+
+Share your blog on the google+ community under "Blog Posts!" Read others blogs. What did you like about them? 

week_1/6_wireframing/readme.md → week_1/8_wireframing/readme.md

@@ -1,6 +1,5 @@
 # U1.W1: Wireframing
 
-
 ## Learning Competencies
 - Explain wireframing
 - Identify the benefits of wireframing
@@ -19,7 +18,7 @@ is often to wireframe it. This process should also help you learn to separate di
 ## Release 0: Intro to Design Thinking
 
 While designers may be "creative" or "artistic", they are also, like
-software engineers problem solvers.  They just solve problems visually
+software engineers, problem solvers.  They just solve problems visually
 instead of with code.  For some of you, this may come really naturally;
 for others it may not.  Either is OK. 
 
@@ -54,5 +53,5 @@ image sharing site.
 * Add the image to your html page.
 
 ## Release 3: Reflection
-On your local `phase_0_unit_1` repo, edit the [my_reflection.md](./my_reflection.md) file associated with this challenge. Commit your changes and save them to GitHub. 
+On your local `phase_0_unit_1` repo, edit the [my_reflection.md](my_reflection.md) file associated with this challenge. Commit your changes and save them to GitHub. 
 

week_1/7_get_to_know_your_group/readme.md → week_1/9_get_to_know_your_group/readme.md

@@ -14,17 +14,20 @@ Despite popular belief, most software engineers work in teams and there is a str
 
 ## Release 0: Intro Email
 
-Once you know who is in your accountability group, send everyone in your group and email **and** edit the [my_reflection.md](./my_reflection.md) file associated with this challenge in your local `phase_0_unit_1` repo,. Commit your changes and save them to GitHub. 
+Once you know who is in your accountability group, send everyone in your group and email **and** edit the [my_reflection.md](my_reflection.md) file associated with this challenge in your local `phase_0_unit_1` repo,. Commit your changes and save them to GitHub. 
 
-* name
-* location
-* favorite websites
-* learning style
+* Name
+* Location
+* Favorite websites
+* Gregorc Thinking Style (Abstract Random, Abstract Sequential, Concrete Random, Concrete Sequential)
+* Learning style (Visual, Aural, Kinesthetic, Multimodal)
 
 ## Release 1: Share your work
+**DOUBLE CHECK THAT YOU HAVE ISSUES ENABLED AS A FEATURE ON BOTH OF YOUR REPOSITORIES**
+
 Once you've completed the week's work, send them:
-* link to your reflection file
+* link to your forked `phase_0_unit_1` repository
 * link to your [USERNAME].github.io site
 * link to your wireframe html page
 
-Once you receive someone's reflection, take a look at it and write a comment as an issue on it. 
+Once you receive someone's work, take a moment to [review](https://github.com/Devbootcamp/phase_0_handbook/blob/master/coding_references/review.md) it and leave comments as issues on their repositories. 

week_1/readme.md

@@ -11,32 +11,29 @@ If you would like to open tabs in a new window, please either right click or hol
 #### 2. [Set Up Repo](2_set_up_repo)
 #### 3. [Web Basics](3_web_basics)
 #### 4. [Beginning HTML & CSS](4_beginning_HTML_CSS)
-#### 5. [More HTML & CSS](5_HTML_CSS_solo_challenge) **SOLO Challenge**
-#### 6. [Wireframing](6_wireframing/)
-#### 7. [Get to know your group](7_get_to_know_your_group)
-#### 8. [Technical Blog](8_technical_blog)
-#### 9. [Affirming your values](9_cultural_blog.md)
+#### 5. [More HTML & CSS SOLO CHALLENGE](5_HTML_CSS_solo_challenge)
+#### 6. [Technical Blog](6_technical_blog)
+#### 7. [Cultural Blog](7_cultural_blog.md)
+#### 8. [Wireframing](8_wireframing/)
+#### 9. [Get to know your group](9_get_to_know_your_group)
 
 ## Submitting your work
-
 You need to submit your work through on [apply.devbootcamp.com](http://apply.devbootcamp.com) by Sunday at 11:59pm. When you log in, look at your profile page. There should be a "Unit 1 Week 1 Form." Expect to submit your links for each of the following:
 
 * Your new website
 * Each html page created in `unit1_projects` folder
-* Your reflection file
-* Comparing websites and values blog posts
+* Your forked `phase_0_unit_1` repository link
+* Your technical and cultural blog posts
 * Your response to "getting to know your group" 
 
-### Fetching changes from DBC's master repo
-Sometimes we will make changes to the original repository to clarify instructions. You will need to fetch these changes from the master branch when we announce changes on the google+ community.
+NOTE: You will have two separate repositories in Github for Unit 1: Your Github.io site and your phase_0_unit_1 repository. 
+
+## Fetching changes from DBC's master repo
+Sometimes we will make changes to the original (Devbootcamp) repository to clarify instructions or add new curriculum. You will need to "fetch" these changes from the master branch when we announce changes on the google+ community. Follow [these](https://github.com/Devbootcamp/phase_0_handbook/blob/master/fetching_changes.md) directions to do this. If you are using a windows or linux, you will need to use the command line instructions.
 
-- If you are doing this from the Github Desktop App, follow [these](http://stackoverflow.com/questions/11394349/upstream-pulls-with-the-github-desktop-client
-)
-directions. 
-- If you are doing it from the command line, follow [these](https://help.github.com/articles/syncing-a-fork) directions.
 
 ## Remember your Unit Goals!
-- Pair at least once this week with a member of your accountability group.  *You need to pair 3 times on your own this unit*
 - Give feedback for each person you paired with. *You need to submit at least 5 pieces of feedback in this unit*
 - Rate at least 7 pieces of [Meta Feedback](https://socrates.devbootcamp.com/feedback) on Socrates. *You need to rate 20 pieces of feedback per unit*
+- Make sure you've signed up for GPS 1.1 and 1.2 (These must be done in a session with guide. They may not be done any other way, so make sure you sign up early!)
 

week_2/1_Chrome_Dev_Tools/readme.md

@@ -37,7 +37,7 @@ Then, visit any blog on [wordpress.com](http://www.wordpress.com) or create your
 
 
 ## Release 3: Reflect 
-Go to your [Reflection file](my_reflection.md) to write your reflection - include answers to the questions in the file in addition to the [reflection guidelines](../reflection_guidelines.md).
+Go to your [Reflection file](my_reflection.md) to write your reflection - include answers to the questions in the file in addition to the [reflection guidelines](https://github.com/Devbootcamp/phase_0_handbook/blob/master/coding_references/reflection_guidelines.md).
 
 ## Release 4: Sync and Submit!
 

week_2/readme.md

@@ -1,5 +1,7 @@
 # HTML and CSS cont. 
 
+Please do not start week 2 until May 19. We will make changes to curriculum and update DBC's master repository. 
+
 This week you will go into more depth on HTML and CSS and get more practice. You will also get to play with Dev Tools and consider the implications of responsive Design. Overall, this week's curriculum should give you the opportunity to go into more depth with HTML and have fun solidifying your knowledge!
 
 You have a [Cultural Assignment](7_cultural_assignment.md) this week you should look at first. 
@@ -18,6 +20,7 @@ You have a [Cultural Assignment](7_cultural_assignment.md) this week you should
 ## Sync DBC's Changes
 ####It's time to sync changes from DevBootcamp's phase_0_unit 1 master repo!
 Follow [these instructions](https://github.com/Devbootcamp/phase_0_handbook/blob/master/fetching_changes.md)!
+
 ## Working through the challenges
 Once you have the entire local repository on your computer, you don't need to read the challenges on github anymore (although we admit, it's prettier). You can open the entire repository in sublime and read the challenges in their original markdown. It will also help you find any link issues, since you can see where they are pointing. If you do find broken links, please let us by posting on the community, but also try to figure out a fix. It will help your markdown skills!
 

week_3/1_git_started/readme.md

@@ -36,8 +36,8 @@ Give yourself a little cheatsheet (in order) of commands you'll need to:
 - Commit locally
 
 ## Release 5: Reflect
-In the reflection section of your 'my_solution.js` file, reflect on your learning using the [reflection guidelines](../reflection_guidelines.md). ***NOTE: Reflections are mandatory!***
+In the reflection section of your 'my_solution.js` file, reflect on your learning using the [reflection guidelines](https://github.com/Devbootcamp/phase_0_handbook/blob/master/coding_references/reflection_guidelines.md). ***NOTE: Reflections are mandatory!***
 
 ## Release 6: Review
-[Review others' solutions](../reviewing_solutions.md) by leaving an issue. Compare their definitions and workflow to yours. Did you have trouble understanding Git or Github? Did they have trouble? Provide actionable, specific, and kind feedback. (You are expected to leave at least two comments for this challenge).
+[Review others' solutions](https://github.com/Devbootcamp/phase_0_handbook/blob/master/coding_references/review.md) by leaving an issue. Compare their definitions and workflow to yours. Did you have trouble understanding Git or Github? Did they have trouble? Provide actionable, specific, and kind feedback. (You are expected to leave at least two comments for this challenge).
 

week_3/2_code_combat/readme.md

@@ -35,7 +35,7 @@ When you are finished with all of the campaigns, answer the following questions.
   - What is the point of the semicolons?
 
 ## Release 4: Reflect
-In the reflection section of your 'my_solution.js` file, reflect on your learning using the [reflection guidelines](../reflection_guidelines.md). ***NOTE: Reflections are mandatory!***
+In the reflection section of your 'my_solution.js` file, reflect on your learning using the [reflection guidelines](https://github.com/Devbootcamp/phase_0_handbook/blob/master/coding_references/reflection_guidelines.md). ***NOTE: Reflections are mandatory!***
 
 
 

week_3/3_js_variables_objects/my_solution.js

@@ -37,7 +37,7 @@
 
 
 // __________________________________________
-// Driver Code:  Do not alter code below this line.
+// Driver Test Code:  Do not alter code below this line.
 
 function assert(test, message, test_number) {
   if (!test) {