<commit_before>[Week 2 Home](../)

##U1.W2: GPS 1.1: Your First Pairing Session! 

**DO NOT LOOK AT THIS CHALLENGE UNTIL YOUR FIRST GUIDED PAIRING SESSION!!**

#### Learning Objectives
  - Use HTML tags to place content on a website
  - Apply CSS to position elements on an HTML page
  - Compare different HTML tags to one another
  - Examine pair-programming concepts

#### Purpose
  Welcome to your first Guided Pairing Session (GPS!)
  We are excited to have you in Phase 0 and to work with
  you to get you prepared for an exciting time at DBC. 

  This GPS is designed to help you examine pair programming and the roles of driver and 
  navigator. 
  
  **Since this is your first pairing session, it is important
  to have a good check-in (so don't forget!).**

#### Directions
  - You need to fork this gist so you have it in your GitHub account. 
    Check to make sure you can navigate to your gists from your main 
    GitHub account page.
  - You will then be directed to Stypi.com, where your instructor
     will have a stypi file ready for you. Because we cannot actually link 
     a stylesheet to an HTML page in stypi, we will be placing CSS 
     between the `<style>` tags. It will be your job to put the correct 
     material in the correct file after the session. 
     **This is not good practice, we are only doing it because of stypi.**
  - Now you are ready to begin! Your goal is to design a website that
     introduces the concept of pair programming!  (You get to figure out how to 
     present it on the page) 

***

  1. Discuss how you want the page to look. Draw a wireframe and write pseudocode with your pair.
  2. Include: a title and your names.
  3. Together, discuss and describe why you think pair-programming is important to DBC.
    Introduce the concept and explain why it's important on your site.
  3. Finally, discuss what pairing means and explain what driver and
    navigator mean. You will want to compare these on the website.
  5. Dress it up! Make it look nice. Include pictures, outside fonts, etc. 
  6. Now, reflect with your pair. What was it like to pair for the first
     time? Did you enjoy it? What worked? What didn't work? Add that
     to your page and style it as well. 

When you are finished, copy your code into the two files. Make sure your css 
from the `<style>` section is in the CSS file and remove it from the HTML section. 
Update your gist. Then, test that everything is still  working by saving them 
and running them together from your computer. <commit_msg>update instructions from gist version to repo<commit_after>[Week 2 Home](../)

##U1.W2: GPS 1.1: Your First Pairing Session! 

**DO NOT LOOK AT THIS CHALLENGE UNTIL YOUR FIRST GUIDED PAIRING SESSION!!**

#### Learning Objectives
  - Use HTML tags to place content on a website
  - Apply CSS to position elements on an HTML page
  - Compare different HTML tags to one another
  - Examine pair-programming concepts

#### Purpose
  Welcome to your first Guided Pairing Session (GPS!)
  We are excited to have you in Phase 0 and to work with
  you to get you prepared for an exciting time at DBC. 

  This GPS is designed to help you examine pair programming and the roles of driver and 
  navigator. 
  
  **Since this is your first pairing session, it is important
  to have a good check-in (so don't forget!).**

#### Directions
  - After you finish this exercise, copy and paste your collaborative code
    into a local HTML and CSS document and push this new page up to your
    github.io website.
  - You will be directed to Stypi.com, where your instructor
     will have a stypi file ready for you. Because we cannot actually link 
     a stylesheet to an HTML page in stypi, we will be placing CSS 
     between the `<style>` tags. It will be your job to put the correct 
     material in the correct file after the session. 
     **This is not good practice, we are only doing it so you can preview your page using stypi.**
  - Now you are ready to begin! Your goal is to design a website that
     introduces the concept of pair programming!  (You get to figure out how to 
     present it on the page) 

***

  1. Discuss how you want the page to look. Draw a wireframe and write pseudocode with your pair.
  2. Include: a title and your names.
  3. Together, discuss and describe why you think pair-programming is important to DBC.
    Introduce the concept and explain why it's important on your site.
  3. Finally, discuss what pairing means and explain what driver and
    navigator mean. You will want to compare these on the website.
  5. Dress it up! Make it look nice. Include pictures, outside fonts, etc. 
  6. Now, reflect with your pair. What was it like to pair for the first
     time? Did you enjoy it? What worked? What didn't work? Add that
     to your page and style it as well. 

When you are finished, copy your code into the two files. Make sure your css 
from the `<style>` section is in the CSS file and remove it from the HTML section. 
Update your gist. Then, test that everything is still  working by saving them 
and running them together from your computer. 
{'fraction_non_alphanumeric': 0.04888975457732762, 'fraction_numerical': 0.004674717569146864, 'mean_word_length': 3.1714053614947195, 'pattern_counts': {'":': 0, '<': 7, '<?xml version=': 0, '>': 7, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '783055', 'n_tokens_mistral': 1419, 'n_tokens_neox': 1329, 'n_words': 856}