Change lesson links and add front matter to some lessons causing link…

…s to break
Kalikoze · Jul 8, 2019 · 6903b02 · 6903b02
1 parent da95951
commit 6903b02
Show file tree

Hide file tree

Showing 5 changed files with 14 additions and 12 deletions.
diff --git a/README.md b/README.md
@@ -61,7 +61,7 @@ This hoisting behavior adds some complexity to the JavaScript language, and is i
 </section>
 ```
 
-![yellow-box](https://user-images.githubusercontent.com/17582916/60548280-f2b2fd00-9cde-11e9-848c-6d58f4b6ebde.png)
+![note-box](https://user-images.githubusercontent.com/17582916/60548280-f2b2fd00-9cde-11e9-848c-6d58f4b6ebde.png)
 
 #### CFU/Exit Ticket Box:
 

diff --git a/lessons/index.html b/lessons/index.html
@@ -127,10 +127,10 @@ <h3>General Web, Tooling & Workflow</h3>
 
   <h3>Design & UI/UX</h3>
   <ul>
-    <li class="lesson"><a href="http://frontend.turing.io/lessons/module-2/intro-ui-ux-empathy-in-design.html">Introduction to UI/UX; Empathy in Design</a></li>
-    <li class="lesson"><a href="http://frontend.turing.io/lessons/module-2/ux-ui-intro-to-personas.html">Introduction to Personas</a></li>
-    <li class="lesson"><a href="http://frontend.turing.io/lessons/module-2/intro-to-accessibility.html">Intro to Accessibility</a></li>
-    <li class="lesson"><a href="http://frontend.turing.io/lessons/module-2/web-accessibility.html">WAI ARIA</a></li>
+    <li class="lesson"><a href="module-2/intro-ui-ux-empathy-in-design.html">Introduction to UI/UX; Empathy in Design</a></li>
+    <li class="lesson"><a href="module-2/ux-ui-intro-to-personas.html">Introduction to Personas</a></li>
+    <li class="lesson"><a href="module-2/intro-to-accessibility.html">Intro to Accessibility</a></li>
+    <li class="lesson"><a href="module-2/web-accessibility.html">WAI ARIA</a></li>
   </ul>
 
   <h3>JavaScript</h3>

diff --git a/lessons/module-2/intro-ui-ux-empathy-in-design.md b/lessons/module-2/intro-ui-ux-empathy-in-design.md
@@ -1,4 +1,8 @@
-# Intro to UI/UX
+---
+title: Intro to UI/UX
+module: 2
+---
+
 ## aka Empathy &  Usability in Design
 
 [slides](https://docs.google.com/presentation/d/1V2Pn6ejC78e0u9T4e9rP8fDpZ29Vm7G-eLVAxFdMDBU/edit#slide=id.g1c033f9cd5_0_35)

diff --git a/lessons/module-2/scope-1.md b/lessons/module-2/scope-1.md
@@ -132,12 +132,7 @@ Our function is also hoisted to the top of our code block, with its entire defin
 
 When functions are hoisted to the top of our code block, it hoists not just the function name, but the code inside of it as well. This means we can invoke functions before we've declared them without running into errors. 
 
-
-<section class="note">
-### Note
-
 This hoisting behavior adds some complexity to the JavaScript language, and is important to understand thoroughly in order to anticipate the values of your variables at any given time.
-</section>
 
 
 <section class="call-to-action">

diff --git a/lessons/module-2/ux-ui-intro-to-personas.md b/lessons/module-2/ux-ui-intro-to-personas.md
@@ -1,4 +1,7 @@
-# UX/UI: Intro to Personas
+---
+title: "UX/UI: Intro to Personas"
+module: 2
+---
 
 Thinking back to [last week's lesson](https://docs.google.com/presentation/d/1V2Pn6ejC78e0u9T4e9rP8fDpZ29Vm7G-eLVAxFdMDBU/edit?usp=sharing), what are some hallmarks of good, user-focused design?
 - Doesn't just look nice - it has to work well