Simplify navigation and change capstone to m1 prework

_includes/base-prework-instructions.md

@@ -0,0 +1,9 @@
+In order to make you as successful as possible during your time here, we have collected readings and exercises for you to complete prior to beginning Mod 1. This pre-work helps provide important context, vocabulary, and baseline of skills to help you hit the ground running on the first day of class. We've found that students who come into the program having invested time in familiarizing themselves with key concepts are able to maximize their time at Turing.
+
+## Mod 1 Pre-work Overview
+
+The Mod 1 Pre-work is divided into two sections: Professional Development and Technical. You are required to spend at least 8 days completing these assignments, however it is recommended that you start as soon as possible. If you have more than a week to dedicate to the mod 1 pre-work, make sure you continue to code every day after you have completed the assignments. You SHOULD NOT complete the mod 1 pre-work early and take an extended break from coding before your first day of class. This is very important to make sure you are in a routine that will keep your skills sharp and prepare you to hit the ground running on day 1.
+
+## Pre-work Assignments
+
+The following assignments are due based on your mod 0 section and can be found on the [mod 0 calendar](mod0.turing.io#calendar)

_includes/navigation.html

@@ -9,14 +9,12 @@
     <section class="sidebar-navigation">
       <h1>Module 0</h1>
       <ul>
+        <li><a href="{{ site.baseurl }}/calendar">Calendar</a></li>
         <li><a href="{{ site.baseurl }}{% link setup-instructions.md %}">Computer Setup</a></li>
-        <li><a href="{{ site.url }}/session1">Session 1</a></li>
-        <li><a href="{{ site.url }}/session2">Session 2</a></li>
-        <li><a href="{{ site.url }}/session3">Session 3</a></li>
-        <li><a href="{{ site.url }}/session4">Session 4</a></li>
-        <li><a href="{{ site.url }}/session5">Session 5</a></li>
-        <li><a href="{{ site.url }}/capstone/fe_engineering">Front End Capstone</a></li>
-        <li><a href="{{ site.url }}/capstone/be_engineering">Back End Capstone</a></li>
+        <li><a href="{{ site.url }}/sessions">Sessions</a></li>
+        <li><a href="{{ site.url }}/homework">Homework</a></li>
+        <li><a href="{{ site.url }}/prework/fe_engineering">Front-End Pre-work</a></li>
+        <li><a href="{{ site.url }}/prework/be_engineering">Back-End Pre-work</a></li>
       </ul>
     </section>
   </div>

_includes/pd-gu-capstone-instructions.md → _includes/pd-gu-prework-instructions.md

@@ -14,19 +14,10 @@ The assignments below will be submitted in gists that you will create on your Gi
 * click Create Public Gist
 * You can also visit [gist.github.com](https://gist.github.com/)
 
-We take these exercises seriously, and we ask that you do too. We expect at minimum 4-6 sentences in response to **each** question, but feel free to expand and elaborate as you deem necessary. Use Markdown to organize your gists clearly with the question above the response like so:
-<div class="try-it">
-  <h3>What is the value of a checklist?</h3>
-  <p>Your response here.</p>
-  <hr>
-  <h3>What do you plan to improve upon while at Turing?</h3>
-  <p>Your response here.</p>
-</div>
- Don't worry about the color or the boxes within the formatting, but the above has the heading and response format that will help us read through these clearly and efficiently, while giving you some practice with ```.md``` files.
-
- Use these exercises to start telling your unique story with your distinct experiences. This is something we will continue to practice during your time at Turing.
+We take these exercises seriously, and we ask that you do too. We expect at minimum 4-6 sentences in response to **each** question, but feel free to expand and elaborate as you deem necessary. Use Markdown (this is a programming language used for writing) to format your gists.
+
+Use these exercises to start telling your unique story with your distinct experiences. This is something we will continue to practice during your time at Turing.
 
 #### [Professional Development Assignment](https://github.com/turingschool/career-development-curriculum-site/blob/master/module-0-capstone/career_development_capstone.md)
 
 #### [Gear Up Assignment](https://github.com/turingschool/gear-up/blob/master/pre-work/intro_with_empathy.markdown)
-

calendar/index.md

@@ -0,0 +1,6 @@
+---
+layout: page
+title: Mod 0 Calendar
+---
+
+<iframe src="https://calendar.google.com/calendar/embed?src=casimircreative.com_12p4693hmer1orcepp74vg77pg%40group.calendar.google.com&ctz=America%2FDenver" style="border: 0" width="100%" height="500" frameborder="0" scrolling="yes"></iframe>

homework/index.md

@@ -0,0 +1,12 @@
+---
+layout: page
+title: Homework
+---
+
+All of the homework for mod 0 can be found on the [mod 0 project board](https://github.com/turingschool/mod-0/projects/1)
+
+This project board uses a methodology called kanban (I would google the term if you're unfamiliar)
+
+You'll be using an app called [conveyor belt](http://conveyorbelt.herokuapp.com/) to create your own copy of the board above. This will allow you to track your progress on the homework over time by moving each card to the done column when you've completed it.
+
+When you've finished your homework, and you're looking for something to do, you can always rely on the mod 1 pre-work as that outlet! Just find the link in the sidebar for your program.

index.md

@@ -7,7 +7,7 @@ Hi there and welcome!
 
 ## What is Mod 0?
 
-Mod 0 is a prerequisite course for both of the programs at Turing. It is a structured series of 5 classes which take place remotely during the evening, and ideally starts 6 weeks before you begin your full-time FEE or BEE course at Turing. These classes are not in person, and are conducted fully remotely via Zoom. Please check the [calendar](https://sites.google.com/casimircreative.com/enrollment/documents-and-info/events-mod-0-calendar) for session dates.
+Mod 0 is a prerequisite course for both of the programs at Turing. It is a structured series of 5 sessions which take place remotely during the evening, and ideally starts 6 weeks before you begin your full-time FEE or BEE course at Turing. These classes are not in person, and are conducted fully remotely via Zoom. Please check the [calendar]({{ site.baseurl }}/calendar) for session dates.
 
 The goals of mod 0 are to:
 * Understand the systems and behaviors needed to be successful at Turing and as a software developer
@@ -31,7 +31,3 @@ The key tools and concepts we go over in mod 0 are:
 ## Next steps
 
 When you're ready to get started, click over to [environment setup instructions]({{ site.baseurl }}{% link setup-instructions.md %}) and start installing!
-
-## Calendar
-
-<iframe src="https://calendar.google.com/calendar/embed?src=casimircreative.com_12p4693hmer1orcepp74vg77pg%40group.calendar.google.com&ctz=America%2FDenver" style="border: 0" width="100%" height="500" frameborder="0" scrolling="yes"></iframe>

capstone/be_engineering/index.md → prework/be_engineering/index.md

@@ -1,33 +1,32 @@
 ---
 layout: page
-title: Module 0 Capstone
+title: Module 1 Pre-work
 subheading: Back End Engineering
 ---
 
-{% include base-capstone-instructions.md %}
+{% include base-prework-instructions.md %}
 
-{% include pd-gu-capstone-instructions.md %}
+{% include pd-gu-prework-instructions.md %}
 
-### Technical Capstone
+### Technical Pre-work
 
-The technical capstone can be completed in 8 days, with one day for setup. However, it is highly recommended that you begin  immediately. It is expected that you spend a few hours of concentrated effort on the tasks for each day - about 30 hours total. This should help you to establish a routine of coding every day.
+The technical mod 1 pre-work can be completed in 8 days, with one day for setup. However, it is highly recommended that you begin  immediately. It is expected that you spend a few hours of concentrated effort on the tasks for each day - about 30 hours total. This should help you to establish a routine of coding every day.
 
-At Turing, you will have to code every single day to stay on top of the workload and build muscle memory for everything you've learned. This capstone is designed to get you into that essential routine before day one of class.
+At Turing, you will have to code every single day to stay on top of the workload and build muscle memory for everything you've learned. This pre-work is designed to get you into that essential routine before day one of class.
 
-After completing the capstone, you should be able to do the following:
+After completing the pre-work, you should be able to do the following:
 
 * Be comfortable navigating your development environment and using your tools (Atom, Chrome, the console, and the command line)
 * Develop a basic knowledge of Ruby in order to build a simple program (for show and tell)
 
-If you have more than 7 days to work on the capstone, you should break up the work and complete the Next Steps section below so that you are coding every day!
+If you have more than 7 days to work on the pre-work, you should break up the work and complete the Next Steps section below so that you are coding every day!
 
 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.
 
-#### [Click here to get started with the Technical Capstone](https://github.com/turingschool-examples/backend_module_0_capstone)
+#### [Click here to get started with the Technical Mod 1 Pre-work](https://github.com/turingschool-examples/backend_mod_1_prework)
 
 ### Next Steps
 
-Before moving any further, complete all of the projects listed in Day 7 of the Module 0 Capstone Repository.
+Before moving any further, complete all of the projects listed in Day 7 of the Module 1 Back-End Pre-work Repository.
 
 If you have more time, review the [Back End Curriculum Site](http://backend.turing.io/) for additional resources.
-

capstone/fe_engineering/index.md → prework/fe_engineering/index.md

@@ -1,40 +1,41 @@
 ---
 layout: page
-title: Module 0 Capstone
+title: Module 1 Pre-work
 subheading: Front End Engineering
 ---
 
-{% include base-capstone-instructions.md %}
+{% include base-prework-instructions.md %}
 
-{% include pd-gu-capstone-instructions.md %}
+{% include pd-gu-prework-instructions.md %}
 
-### Technical Capstone
+### Technical Pre-work
 
-The technical capstone can be completed in 8 days, with one day for setup. However, it is highly recommended that you begin  immediately. It is expected that you spend a few hours of concentrated effort on the tasks for each day - about 30 hours total. This should help you to establish a routine of coding every day.
+The technical pre-work can be completed in 8 days, with one day for setup. However, it is highly recommended that you begin  immediately. It is expected that you spend a few hours of concentrated effort on the tasks for each day - about 30 hours total. This should help you to establish a routine of coding every day.
 
-At Turing, you will have to code every single day to stay on top of the workload and build muscle memory for everything you've learned. This capstone is designed to get you into that essential routine before day one of class.
+At Turing, you will have to code every single day to stay on top of the workload and build muscle memory for everything you've learned. This pre-work is designed to get you into that essential routine before day one of class.
 
-After completing the capstone, you should be able to do the following:
+After completing the pre-work, you should be able to do the following:
 
 *   Be comfortable navigating your development environment and using your tools (Atom, Chrome, the console, and the command line)
 *   Develop a basic knowledge of HTML, CSS, and JavaScript code in order to build a simple, static web page (for show and tell in week 1!)
 
-If you have more than 7 days to work on the capstone, you should break up the work and complete the Next Steps section below so that you are coding every day!
+If you have more than 7 days to work on the pre-work, you should break up the work and complete the Next Steps section below so that you are coding every day!
 
 #### What You'll Need
 
-Items you need to complete the mod 0 capstone:
+Items you need to complete the mod 1 pre-work:
 
 *   The books: [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)
-*   A consistent internet connection
+  * These can be found online for free. After some quick googling it looks like they can be found here
+  * [html & css](https://www.pdfdrive.com/html-css-e16578853.html)
+  * [javscript & jquery](https://www.pdfdrive.com/javascript-and-jquery-interactive-front-end-web-development-e195248768.html)
 
 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.
 
-#### [Click here to get started with the Technical Capstone](https://github.com/turingschool-examples/frontend-module-0-capstone)
+#### [Click here to get started with the Technical Mod 1 Pre-work](https://github.com/turingschool-examples/frontend-mod-1-prework)
 
 ### Next Steps
 
-Before moving any further, complete all of the exercises listed [here](https://github.com/turingschool-examples/frontend-module-0-capstone#month-of-module-0-capstone-extended-resources).
+Before moving any further, complete all of the projects listed in Day 7 of the Module 1 Front-End Pre-work Repository.
 
 If you have more time, review the [Front End Curriculum Site](http://frontend.turing.io/) for additional resources.
-

session1/index.md

@@ -105,7 +105,7 @@ Turing is a very challenging experience for most people. To be successful here,
 
 ### Communication
 
-Make sure that you've added the **[Mod 0 Calendar](https://calendar.google.com/calendar?cid=Y2FzaW1pcmNyZWF0aXZlLmNvbV8xMnA0NjkzaG1lcjFvcmNlcHA3NHZnNzdwZ0Bncm91cC5jYWxlbmRhci5nb29nbGUuY29t)** to your own calendar. This is where you will find all mod 0 related events, including sessions, capstone study sessions, and other community wide events.
+Make sure that you've added the **[Mod 0 Calendar](https://calendar.google.com/calendar?cid=Y2FzaW1pcmNyZWF0aXZlLmNvbV8xMnA0NjkzaG1lcjFvcmNlcHA3NHZnNzdwZ0Bncm91cC5jYWxlbmRhci5nb29nbGUuY29t)** to your own calendar. This is where you will find all mod 0 related events, including sessions, mod 1 pre-work study sessions, and other community wide events.
 
 We will also remind you when these events are via **[slack](https://turingschool.slack.com/)**, which is the **primary mode of communication** we use at Turing. Make sure that you're checking it once a day so that you can stay up to date. It's also a great place to ask questions if you are running into issues, as people are likely experiencing the same issue that you are.
 
@@ -664,5 +664,3 @@ In addition, consider the following questions:
 ## Homework
 
 Find the homework in your Mod 0 Project Board. Contact David, Ellen, or Mason if you're stuck (or better yet, post in the public slack channel as you're likely not the only one running in to that issue)
-
-Capstones (program specific pre-work) are another good thing to get a head start on. They can be found on the mod 0 website in the sidebar and are due 6/10. Plan on ~40 hours in total.

session2/index.md

@@ -54,7 +54,7 @@ subheading: Terminal, File/folder Structure, Git Basics
 
 - We'll stay on the call at the end of today's session for any Qs that are not addressed during the lesson.
 - You'll receive feedback on homework from either Alice, Margo, Mason, or David. Check your homework gists!!!
-- Where are you on your capstone? They're due June 10th!
+- Where are you on your pre-work? It's due June 10th!
 
 ### Today's Goals
 

session3/index.md

@@ -409,5 +409,3 @@ git push origin master
 ## Homework and GitHub Projects
 
 Business as usual. Reach out on slack if you're stuck!
-
-Capstone is due next Wednesday! Aim to be finished with day 5 by the weekend!

session4/index.md

@@ -46,7 +46,6 @@ subheading: Scavenger Hunt, Modeling OOP, Assessment Expectations
 
 - Leaving feedback directly on homework gists. Make sure you're checking them. We'll have session 2 + 3 feedback to y'all be end of the weekend.
 - Remember to be aware of where you are in your directory structure of the terminal before you clone anything down or start running git commands. Always run ls after cloning
-- We don't expect you to be masters at all the things in your capstone. It's really your mod 1 prework
 - We understand that things are crazy right now. Be kind and gentle with yourselves and others. If you need anything from us, don't hesitate to reach out. Remember that proactive communication is always best.
 
 ### Other Notes
@@ -328,7 +327,7 @@ This is our final Mod 0 technical session. Your assignment between now and Sessi
 
   <ol>
     <li>Open up your <code>...</code> file in your text editor.</li>
-    <li>You'll be given directions for some exercises that are program specific. Looking for something to study? Check out session 1 on data types and variable assignment. The capstone is also a good resource.</li>
+    <li>You'll be given directions for some exercises that are program specific. Looking for something to study? Check out session 1 on data types and variable assignment. The mod 1 pre-work is also a good resource.</li>
     <li>If you are really solid with data types and variable assignment, it shouldn't be too bad</li>
     <li>Save your file.</li>
     <li>Add and commit your changes.</li>

session5/index.md

@@ -43,8 +43,8 @@ subheading: Attention to Detail and Iteration
 
 ### Follow-Ups
 
-- Capstones are due this Wednesday! Get on it!
-- We will have assessment and capstone feedback to everyone by EOD Monday
+- Prework is due this Wednesday! Get on it!
+- We will have assessment and prework feedback to everyone by EOD Monday
 
 ### Today's Goals
 
@@ -334,8 +334,8 @@ We'll go into breakout rooms to briefly discuss the syntax for iterating in Ruby
   * Keep up the hard work
   * Keep asking questions in your cohort channels
   * Ellen, Mason and David are still around if you need us
-  * Capstone is due Wednesday (see your mod 0 calendar)
+  * Prework is due Wednesday (see your mod 0 calendar)
 
 * Learning to code is much more like exercise than epiphanies - Think about MJ!
 
-> Quote from Meg Stang (BE instructor) - "I've noticed that the students that do the bare minimum on their mod 0 capstone are the ones that usually struggle for at least the first half of the mod."
+> Quote from Meg Stang (BE instructor) - "I've noticed that the students that do the bare minimum on their mod 1 pre-work are the ones that usually struggle for at least the first half of the mod."