Rename lesson-segment style name to call-to-action

Kalikoze · Jul 8, 2019 · da95951 · da95951
1 parent 448c3bb
commit da95951
Show file tree

Hide file tree

Showing 4 changed files with 23 additions and 21 deletions.
diff --git a/README.md b/README.md
@@ -38,8 +38,8 @@ You can add styled boxes to your lesson plans for different areas of content.
 
 #### Standard Box:
 
-```js
-<section class="lesson-segment">
+```html
+<section class="call-to-action">
 ### In Your Notebook
 
 What would you expect to be logged when we get to line 10? Why?
@@ -53,7 +53,7 @@ Will result in the following styled box:
 
 #### Note Box:
 
-```js
+```html
 <section class="note">
 ### Note
 
@@ -65,11 +65,11 @@ This hoisting behavior adds some complexity to the JavaScript language, and is i
 
 #### CFU/Exit Ticket Box:
 
-```js
+```html
 <section class="checks-for-understanding">
-  <h3 id="check-for-understanding">Exit Ticket</h3>
+### Exit Ticket
 
-  <p>What are 3 easy and actionable accessibility steps you can take in all of your projects from here on out?</p>
+What are 3 easy and actionable accessibility steps you can take in all of your projects from here on out?
 </section>
 ```
 

diff --git a/_sass/content.scss b/_sass/content.scss
@@ -28,26 +28,26 @@
   display: block;
 }
 
-%lesson-segment-shared {
+%call-to-action-shared {
   margin-top: 30px;
   box-shadow: 0 2px 8px 0 rgba(0,0,0,0.15);
   margin-bottom: 40px;
   padding: 5px 30px;
 }
 
-.lesson-segment {
-  @extend %lesson-segment-shared;
+.call-to-action {
+  @extend %call-to-action-shared;
   border-left: 8px solid lighten($turing-secondary, 25%);
 }
 
 .checks-for-understanding {
-  @extend %lesson-segment-shared;
+  @extend %call-to-action-shared;
   border-left: 8px solid lighten($turing-secondary, 25%);
   background-color: lighten($turing-primary, 40%);
 }
 
 .note {
-  @extend %lesson-segment-shared;
+  @extend %call-to-action-shared;
   border-left: 8px solid lighten($front-end-secondary, 25%);
   background-color: lighten($front-end-primary, 40%);
 }

diff --git a/lessons/module-2/intro-to-accessibility.md b/lessons/module-2/intro-to-accessibility.md
@@ -61,7 +61,7 @@ For each of these types of limitations:
 ## Station One
 
 
-<section class="lesson-segment">
+<section class="call-to-action">
 ### Experiment I - Using a Screen Reader
 
 * Watch the following [video to see how a screen reader understands a page](https://youtu.be/qdB8SRhqvFc?t=417) up until the 9:40 mark.
@@ -86,7 +86,7 @@ Here are some helpful VoiceOver commands:
 * Did you cheat and open your eyes?
 </section>
 
-<section class="lesson-segment">
+<section class="call-to-action">
 ### Experiment II - Color Blindness
 
 Install a colorblind simulator for Chrome. Try one (or both) of the following:
@@ -109,7 +109,7 @@ Navigate to some of your most visited sites -- especially those that have some s
 
 ## Station Two
 
-<section class="lesson-segment">
+<section class="call-to-action">
 ### Experiment I - Tabbing
 
 Watch the following [video](https://youtu.be/hKIQkgPVXH4?t=307) up until the 9:50 mark.
@@ -125,7 +125,7 @@ Go to the [Enterprise Car Sales](https://www.enterprisecarsales.com//) website a
 * How was the focus on your current selection? Did you tab into the drop down menus for selecting a car make and model?
 </section>
 
-<section class="lesson-segment">
+<section class="call-to-action">
 ### Experiment II - Accessible Text
 
 Check out the following [site](http://geon.github.io/programming/2016/03/03/dsxyliea) that replicates what it *could* be like to read text with Dyslexia. 
@@ -164,7 +164,7 @@ Read through the passing, failing and manual audits:
 
 
 <section class="checks-for-understanding">
-  <h3 id="check-for-understanding">Exit Ticket</h3>
+### Exit Ticket
 
-  <p>What are 3 easy and actionable accessibility steps you can take in all of your projects from here on out?</p>
+What are 3 easy and actionable accessibility steps you can take in all of your projects from here on out?
 </section>
diff --git a/lessons/module-2/scope-1.md b/lessons/module-2/scope-1.md
@@ -55,7 +55,7 @@ Let's look at a more complex example:
 10  console.log(numEvals);
 ```
 
-<section class="lesson-segment">
+<section class="call-to-action">
 ### In Your Notebook
 
 What would you expect to be logged when we get to line 10? Why?
@@ -85,7 +85,9 @@ Let's look at another example:
 7  console.log('Animal Sound: ', moo);
 ```
 
-<section class="lesson-segment">
+<section class="call-to-action">
+### On Your Own  
+
 What would we expect to be logged when line 7 executes? Why? Is the actual behavior different than you expected?
 </section>
 
@@ -138,7 +140,7 @@ This hoisting behavior adds some complexity to the JavaScript language, and is i
 </section>
 
 
-<section class="lesson-segment">
+<section class="call-to-action">
 ### Turn and Talk
 
 With a partner, take turns explaining how the following JavaScript code would be translated by the interpreter. We will come back together as a class to discuss:
@@ -200,7 +202,7 @@ As the call stack builds up, each function has its own execution context.
 
 ![callstack building up](https://media.giphy.com/media/3ohs4rkYvzISB83cqY/giphy.gif) 
 
-<section class="lesson-segment">
+<section class="call-to-action">
 ### Turn and Talk 
 
 With a partner, take turns explaining how the the following JavaScript code would be translated by the interpreter. While one person is speaking, the other person should be diagramming this process.