Added some missing dates on schedule. Added unedited wall checkpoint …

…text

docs/_sections/_guide-general/forms.md

@@ -1,8 +1,16 @@
 ---
 layout: default
-title: Forms
+title: Links and Forms
 nav_include: true
 nav_order: 4
 ---
 
-TBD
+# Forms TODO: add actual links 
+
+This page contains all the links and forms that you might need!
+
+<!-- change colors to whatever idc -->
+[Robotathon Linktree](a){: .btn .btn-purple } 
+[Robotathon Interest Form](a){: .btn .btn-purple } 
+[Robotathon Dues Form](a){: .btn .btn-green }
+[RAS Membership Form](a){: .btn .btn-blue }

docs/_sections/_guide-general/schedule.md

@@ -10,22 +10,21 @@ nav_order: 2
 
 ## Dates List:
 
+**Kickoff** - Sept 17th
+**Team Assembly Checkpoint** - Sept 17th (at kickoff)
+**Design Checkpoint** - Sept 22nd
+**Programming Workshop I** - Sept 23
+**LED Blink Checkpoint** - Sept 29
+**Programming Workshop II** - Sept 30
 **Moving Base Checkpoint** - Oct 6
-
 **Solidworks Workshop** - Oct 7
-
 **Line/Wall/Color Checkpoint** - Oct 13
-
 **Breadboarding Workshop** - Oct 14
-
 **Line/Wall/Color Checkpoint** - Oct 20
-
 **Color Sensor Workshop** - Oct 21
-
 **Line/Wall Follow Workshop** - Oct 28
-
 **Mechanical Design Checkpoint** - Nov 3
-
 **Line/Wall/Color Checkpoint** - Nov 10
-
 **Competition Day** - Nov 16
+
+Note: Line/Wall/Color means your team has a choice between the three different sensors to demo for the checkpoint

docs/_sections/_guide-general/welcome.md

@@ -6,4 +6,5 @@ nav_include: true
 nav_order: 1
 ---
 
-TBD
+# Robotathon Docs TODO: move stuff from preface to here
+

docs/_sections/_guide-primaries/checkpoints/mechanical-checkpoint.md

@@ -0,0 +1,57 @@
+---
+layout: default
+title: Mechanical Checkpoint
+nav_include: true
+parent: Checkpoints
+nav_order: 4
+---
+# Mechanical Checkpoint
+Your team has to come up with a mechanical design that translates individual robot components into how you envision your robot completing particular tasks. 
+A lil intro to engineering projects! Along with your team, these are the bare bones of what it takes to create a project (ahem ahem like a robot?? ahem ahem) from start to finish. For more elaboration on these key steps, I recommend checking out our tutorial on the Engineering Design Process here. 
+
+1- Identify the tasks/functions needed for the challenge
+It would be wise to take a look at the RAScade competition rules, my dear. In particular, start thinking about your team’s game plan for each match.
+2- Identify how parts can be used
+Take a look at the provided parts list. Look up things like what a servo motor is used for or how to operate different sensors! 
+3- Brainstorm how you can combine parts to achieve that goal; no wrong ideas!
+4- Build/Test/Improve a Prototype
+
+Your robot is faced with the challenge of throwing an object. Here are some “template” designs that might be appealing to look more into! Here’s a separate link that might help with your research. 
+
+A Few Robot Arm Designs
+
+Basic Claw Bot
+It gets the job done.
+
+- Up up down down left right left right- I mean use motors to move wheels, lift your bot’s arm(s), and grip or release something.
+- Usually done for controlled robots rather than autonomous. 
+
+Conveyor Belt Lift/Drop
+Going up? Or down?
+
+- Using flaps, chains, gears, etc, guide stuff from point A to B.
+- Can be used to transfer something front to back or vice versa as well. 
+-Make sure the objects are supported by the system!
+
+Flywheel Shooter
+There is a need for speed in order to fly.
+
+-With a wheel (or two!) and a fast enough motor and friction, your bot can send stuff flying!
+-Whatever is holding the wheel and axle that spins needs to be held steady! Don’t need your whole bot shaking now do we?
+
+Fling/Catapult
+An oldie but a goodie.
+
+-A strong enough flick of the wrist can project an object away from the bot. 
+- Rubber bands could be used like a slingshot. 
+-Be careful to balance the weights of the bot and what the lever arm is flinging!
+
+Pusher/Intake
+To hold objects or let them go.
+
+- Get creative for how your bot wrangles objects closer to or away from itself near to the ground. 
+- Can be passive or active with motors. 
+- Avoid scenarios where objects could get stuck! 
+
+The engineering design process is just that- a process! Designs don’t always work they way you planned, so be prepared to do a lot (and I mean a lot) of revising to end up achieving the goal you originally intended. Keep an open mind and think outside of the box! :) 
+

docs/_sections/_guide-primaries/checkpoints/wall-checkpoint.md

@@ -4,4 +4,31 @@ title: Wall Checkpoint
 nav_include: true
 parent: Checkpoints
 nav_order: 2
----
+---
+
+# Wall Checkpoint/Challenge UNEDITED
+
+Below is the premise for this checkpoint:
+Checkpoint 4: I’m Dumb, Not Stupid (Wall Following)
+Have your robot stop for walls that are placed in front of it
+OR have your robot go around obstacles in its way (optional)
+
+Some things you should look out for:
+IR sensor placement
+There is a previous page in this guide that discusses sensor placement so be sure to take a look at this when working on the checkpoint
+You can always experiment with different IR sensor placement since you will be given 2! 
+Touch Sensor Use
+It is up to your group whether or not you would like to utilize the touch sensor for this challenge as well. It could serve to help change direction if your robot were to run into a wall (hint hint)
+Your code (dun dun dun)
+This is of course a very  important aspects of this checkpoint!! I know this part is one of the hardest and most time consuming so try to get a head start and come to office hours if you need help!
+
+Once you have completed this checkpoint you will have a better idea of what to expect from the Pacman Maze. 
+Below is a sneak peak of the design for the maze…
+
+
+Your robot will have to traverse this area and reach the end accordingly. This challenge will specifically test your ability to validate the IR sensors and either error correct or have good control loops to remain in range of good data. The maximum amount of points you can obtain by completing this challenge is 24. If your robot gets stuck or cannot complete the maze then you can still receive partial points for the amount of pellets you cross.
+
+
+
+
+One thing that helps is making sure that your robot can execute  accurate 90 degree turns. Try to think of some ways that you could experiment with wheel direction and speed. Maybe one motor going slower than the other or rotating the opposite direction o_o

docs/_sections/_guide-primaries/sensors-and-actuators/motors.md

@@ -4,4 +4,6 @@ title: Motors
 nav_include: true
 parent: Sensors and Actuators
 nav_order: 1
----
+---
+
+TBD

docs/_sections/_guide-primaries/sensors-and-actuators/pid-control.md

@@ -4,4 +4,6 @@ title: PID Control
 nav_include: true
 parent: Sensors and Actuators
 nav_order: 1
----
+---
+
+TBD

docs/_sections/_guide-primaries/sensors-and-actuators/sensors-and-actuators.md

@@ -4,4 +4,6 @@ title: Sensors and Actuators
 nav_include: true
 has_children: true
 nav_order: 2
----
+---
+
+TBD