added checkpoint stuff

Author: tguyenn

docs/_sections/_guide-FAQ/technical.md

@@ -8,6 +8,11 @@ nav_order: 1
 # Technical FAQ
 
 ## Why does my build fail?
+Ensure their portable vscode installation is located in a path without spaces
+Document instance where they have spaces in name
+- Solution is to move project directory to C drive
+Document reading the error messages (i.e. starting from the first error culprit fixes ones below etc etc)
+
 
 ## What is the difference between cloning using HTTPS and SSH?
 HTTPS (Hypertext Transfer Protocol Secure) and SSH (Secure Shell) are both data transfer protocols used in networking
@@ -62,4 +67,11 @@ If *that* fails, then check if there are any other applications on your computer
 ## How to calibrate the QTR line sensor?
 
 <!-- ## Why doesn’t anything show up when I try printing to the serial monitor? -->
-<!-- idk if this is actually na issue?? -->
+<!-- idk if this is actually na issue?? -->
+
+
+# How does the ESP-IDF build system work?
+
+This information is not required for the competition, but it can be good to know if you'd like to continue IoT develpoment with Espressif MCU's.
+
+Here is a link to their official documentation: [https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-guides/build-system.html#component-requirements](https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-guides/build-system.html#component-requirements)

docs/_sections/_guide-checkpoints/color-challenge.md

@@ -13,7 +13,7 @@ To pass this checkpoint, your robot should meet the following requirements:
 
 * Have the color sensor attached to the robot in some way
 * Be able to sample and store the color of the initial tile
-* Autonomously drive until the identical tile is found
+* Autonomously drive until the matching tile color is found
 
 Some questions we might ask about this checkpoint are:
 

docs/_sections/_guide-checkpoints/design.md

@@ -1,9 +1,30 @@
 ---
 layout: default
-title: Design Check
+title: Design
 nav_include: true
-nav_order: 2
+nav_order: 4
 ---
 
+<img src="{{ '/_assets/images/my_image.png' | prepend: site.baseurl }}" alt="my_image.png :(">
+***replace with smth smth design***
 
-goo goo gaga
+
+To pass this checkpoint, your design should meet the following requirements:
+* A drawn picture (does not have to be detailed) that shows where you plan to place each component
+
+Component list: TODO update
+1 Battery pack
+1 Dual Motor Driver
+2 DC Motors
+1 Servo
+1 Caster Wheel
+1 Line Sensor
+1 Color Sensor
+1 IR Distance Sensor
+1 White LED (color sensor) TODO elaborate or link smth here
+1 ESP32 on breadboard
+
+Questions:
+* What materials are you going to use to build your robot chassis? (recommend TIW laser cut for main body and 3D print for other parts)
+* Is your design within the required dimensions?
+* Does your design account for the mechanical challenge?

docs/_sections/_guide-checkpoints/environment-setup.md

@@ -5,5 +5,16 @@ nav_include: true
 nav_order: 3
 ---
 
+<img src="{{ '/_assets/images/my_image.png' | prepend: site.baseurl }}" alt="my_image.png :(">
+***replace with smth smth enviro setup***
 
-goo goo gaga
+To pass this checkpoint, your team should meet the following requirements:
+
+* Use your controller to control the ESP32's onboard LED (i.e. button pressed = on, button released = off)
+* Have your teammates added to your team's forked GitHub repository
+
+Questions:
+* What does it mean to build your project?
+* What does it mean to flash your project?
+* What is the process for putting your code onto your team's GitHub repo?
+* What is a GPIO?

docs/_sections/_guide-checkpoints/introduction.md

@@ -5,5 +5,18 @@ nav_include: true
 nav_order: 1
 ---
 
+<img src="{{ '/_assets/images/my_image.png' | prepend: site.baseurl }}" alt="my_image.png :(">
+***replace with smth smth introduction***
 
-goo goo gaga
+To pass this checkpoint, your team should meet the following requirements:
+
+* Create a groupchat with your team on any platform (Discord, iMessage, etc.)
+* Take selfie with your team and send it in your own team's group chat
+* Come up with a fun name and have it approved by your mentor (professors will see it😄)
+
+Questions:
+* Why did you choose your team's name? tbh idt we should have/need this lol
+
+Next Steps:
+* Divide up tasks (software/mechanical)
+* Find a weekly work session time with your team

docs/_sections/_guide-checkpoints/moving-base.md

@@ -5,5 +5,22 @@ nav_include: true
 nav_order: 4
 ---
 
+<img src="{{ '/_assets/images/my_image.png' | prepend: site.baseurl }}" alt="my_image.png :(">
+***replace with smth smth moving base***
 
-goo goo gaga
+
+To pass this checkpoint, your robot should meet the following requirements:
+
+* Motors attached to a chassis (can be literally anything)
+* Robot chassis moves when given controller input (i.e. pushing joystick moves forward, letting go stops)
+
+
+Next Steps:
+* Use CADed materials for your chassis (laser-cut for main chassis, 3D-print for other parts recommended)
+* Be able to control your robot more precisely with the controller (turn left, right, back, forward)
+* Be able to change your robot's mode when you press a button (TODO insert smth about mentorbot)
+
+
+Some questions we might ask you:
+* How is your robot powered?
+*