Rachael Carroll

README.md

@@ -1,41 +1,50 @@
-# Frontend Mod 1 Pre-work Repository
+# Front-End Mod 1 Pre-work Guide
 
-This repository will walk you through the Mod 1 Pre-work for the Frontend program at Turing.
+This repository will guide you through the Mod 1 Pre-work for the Front-End program at Turing. **Read this page thoroughly** to find the instructions for getting your computer setup and getting started.
 
-Each day has a folder containing a `README.md` file with instructions for the day, exercises, and questions. You must complete all the exercises and questions.
+Each section has a folder containing a `README.md` file with instructions and deliverables for the section, exercises, and reflections. You must complete all the exercises and reflections.
 
-### Pre-work Index
+## Pre-work Index
 
-* [Day 0 - More Terminal Practice](day_0)
-* [Day 1 - Strings, Numbers, And Booleans](day_1)
-* [Day 2 - Arrays and Iteration](day_2)
-* [Day 3 - If Statements](day_3)
-* [Day 4 - Functions and Return Values](day_4)
-* [Day 5 - Objects](day_5)
-* [Day 6 - Classes](day_6)
-* [Day 7 - Build A Thing](day_7)
+* [Section 1 - SUPER LEARNERS, Terminal and JavaScript Foundations](section1)
+* [Section 2 - ASKING QUESTIONS, Conditionals and Functions](section2)
+* [Section 3 - GROWTH MINDSET, Arrays and Iteration](section3)
+* [Section 4 - HOW YOU USE YOUR TIME, Objects and Classes](section4)
+* [Final Project - Final Project and Submission](finalProject)
 
-# Materials
+## Materials
 
-Items you need to complete the mod 1 pre-work:
+📒The only material, outside of your computer and an internet connection that you need to complete your pre-work is the `JAVASCRIPT & JQUERY: Interactive Front-End Web Development` book by John Duckett. You can [download it for free here](https://www.pdfdrive.com/javascript-and-jquery-interactive-front-end-web-development-e184606066.html) or [purchase a hard copy here](https://www.amazon.com/Web-Design-HTML-JavaScript-jQuery/dp/1118907442/ref=sr_1_2?ie=UTF8&qid=1541193719&sr=8-2&keywords=duckett) (or elsewhere).
 
- * These can be found online for **free**. Find links to each book below:
-   -  [HTML & CSS](https://www.pdfdrive.com/html-css-e16578853.html)
-   -  [JavaScript & jQuery](https://www.pdfdrive.com/javascript-and-jquery-interactive-front-end-web-development-e195248768.html)
- *   Hard copies of the books can be purchased here: [Web Design with HTML, CSS, JavaScript and jQuery Set](https://www.amazon.com/Web-Design-HTML-JavaScript-jQuery/dp/1118907442/ref=sr_1_2?ie=UTF8&qid=1541193719&sr=8-2&keywords=duckett)
+>Please be aware, when page numbers for this book are referenced, it is the page number in the printed book. They don't quite match up with the ways the pages in the PDF are numbered, so make sure to reference the printed page number in the bottom corner of a page in the book.
 
-The link below will take you to the GitHub page that contains all the Technical work. Scroll through the page to find the instructions for getting your computer setup and getting started.
+## What to Expect
 
-# Environment
+Through completing this pre-work, you can expect to get practice re-inforcing what you learned/are learning in Mod 0, learn more technical content, and deeply reflect on your mindsets and habits and start thinking about which of those mindsets and habits will help you learn to code, and which of those you may need to change.
 
-## Install Node.js and NPM using homebrew
+We will remind you of the best practices that follow from time-to-time, but to ground yourself in the work ahead, read them carefully.
 
-Before we're able to write javascript that can be run from the command line (you'll be doing this in Mod 1), we need to install `Node.js` and `NPM` and it'll be expected that you've run through these instructions.
+## Best Practices: Learning to Write Code
+
+**If you are stuck for longer than 30 minutes, know that it is always ok to ask for help!** The process of becoming a software developer is difficult, and learning to code is hard. At some point, everyone struggles. Struggle is a normal, healthy part of the learning process - don't give up if you hit a hard spot. If you consistently practice every day and don't take shortcuts, you will be on the path to learning how to code. When you reach out for help, challenge yourself to ask clear questions and use technical vocabulary. Speaking accurately about code is a great way to help lock in technical understanding. Use [this guide](https://gist.github.com/ericweissman/fb0241e226227867b6bc70a4d49227f5) to learn the optimial way to ask for help when you get stuck!
+
+**Process over Product.** When asking for help, do your best to seek understanding rather than `the answer` or `the solution`. Even if your helper gets you a solution that works, make sure to spend time on *why* it works, rather than just accepting the solution and moving on.
+
+**Type every line of code.** One of the best things you can do to set yourself for success is to make sure you type out all the code examples you see in the readings and exercises in this pre-work, *do not* copy and paste. The more hands-on-keyboard practice you can give yourself, the better. Copying and pasting won't help you solidify these concepts, manually typing all the code in will. This also applies to auto complete features in popular text editors. They are helpful, no doubt, but doing things the hard way at the beginning is a great way to hone your workflow later on.
+
+**Details matter.** Pay close attention to small details in syntax, spacing, and language. The most detailed oriented you are as you're working, the more reliable and well-crafted your code will be. In programming, being detail oriented helps cut down on buggy code and difficult to use systems. It can also help you notice differences in your code, enabling you to identify typos and mistakes more quickly.
+
+## Environment
+
+### Install Node.js and NPM using homebrew
+
+Before we're able to write JavaScript that can be run from the command line (you'll be doing this in Mod 1), we need to install `Node.js` and `NPM` and it'll be expected that you've run through these instructions.
 
 These setup instructions assume that you have completed the setup for Mod 0, like installing Atom, xcode-select, Homebrew, git, and Chrome. If you haven't done that yet, please see [the mod-0 environment setup instructions](http://mod0.turing.io/setup-instructions).
 
-## Install Node.js:
-JavaScript was originally intended to be run in the browser (ie. Chrome). But over time there were a lot of good reasons to allow it to be run server side. Node.js is a framework that allows us to to do just that.
+### Install Node.js:
+
+JavaScript was originally intended to be run in the browser (i.e., Chrome). But over time there were a lot of good reasons to allow it to be run server side. Node.js is a framework that allows us to to do just that.
 
 Additionally, there's some very useful "packages" we use while writing code and we cannot install without first installing `node`.
 
@@ -60,7 +69,7 @@ Now enter:
 $ node -v
 ```
 
-This shows us what version of Node.js we are running. You should see something like:
+This shows us what version of Node.js we are running. You should see _something_ like:
 
 ```
 v12.8.0
@@ -82,11 +91,11 @@ This shows us what version of NPM we are running. You should see something like:
 
 ## Terminal
 
-We will be referencing many terminal commands throughout the pre-work. It is recommended that you practice using terminal commands before getting started. See the `terminal.md` lesson located in the day_0 directory.
+We will be referencing many terminal commands throughout the pre-work. It is recommended that you practice using terminal commands before getting started. See the `terminal.md` lesson located in the `part1` directory.
 
 ### Forking the Module 1 Pre-work Repository
 
-Next, we are going to *fork this repository that you're reading right now*. Forking is when you copy a GitHub repository to your GitHub account to make your own changes. Think of it like a fork in the road -- you're about to make changes that differ from the main path.
+Next, we are going to *fork this repository that you're reading right now*. Forking is when you copy a GitHub repository to your GitHub account so that you can make changes to your copy without affecting the original repository.
 
 In this scenario, the [Turing GitHub account](https://github.com/turingschool) owns this `frontend-mod-1-prework` repository. You do not have permission to change anything in this repository, so you need your own copy to work on. In order to fork the repository, follow these steps:
 
@@ -112,14 +121,12 @@ Cloning is when you copy a remote GitHub repository to your local computer.
 
 ![clone down your copy](/images/fork_03.jpg)
 
-
 #### 2. If you see `Clone with HTTPS` click on `Use SSH`
 
 #### 3. Click on the copy icon to copy the SSH link to your clipboard.
 
 #### 4. Use your terminal to copy down this repository
 
-
 1. Open your terminal
 
 ```
@@ -145,6 +152,8 @@ nothing to commit, working tree clean
 
 From here on out, all the work you do will be in your copy of this repository. Other text you read here might refer to this as the "prework repository" or "frontend prework", and they all refer to your forked copy of this `frontend-mod-1-prework` repository.
 
-Each day's `README` will walk you through the steps you need to take to save your work.
+## Get Started
+
+Each sections `README` will walk you through the steps you need to take to save your work.
 
-To start, in your terminal, `cd` into the `day_0` directory. Follow the instructions contained in the `readme.md` file, and have a great time!
+To start, in your terminal, `cd` into the `section1` directory. Follow the instructions contained in the `README.md` file, and have a great time learning and exploring!