diff --git a/_data/sidebar_tree.yaml b/_data/sidebar_tree.yaml index 2a88a6f7..67614bea 100644 --- a/_data/sidebar_tree.yaml +++ b/_data/sidebar_tree.yaml @@ -80,6 +80,8 @@ tree: - url: /robots_101/ title: Robots 101 tree: + - url: /robots_101/programme_structure + title: Programme Structure - url: /robots_101/post_kickstart title: After Kickstart - url: /robots_101/design diff --git a/robots_101/programme_structure.md b/robots_101/programme_structure.md new file mode 100644 index 00000000..3600276c --- /dev/null +++ b/robots_101/programme_structure.md @@ -0,0 +1,82 @@ +--- +layout: page +title: Robots 101 - Programme Structure +--- + +# Robots 101 - Programme Structure + +Student Robotics is an annual robotics competition for people aged 16-19. +But what actually happens during the course of the competition year? + +## Registration + +Registration for the competition usually open in late summer. Teams usually +consist of 4-8 competitors attending a school or college, though other groups +are also free to enter. Your team must have a responsible adult who will oversee +the team -- a role we call the [team supervisor][team-supervisor]. + + + +## Kickstart + +Kickstart is the event which kicks off a competition year. The structure of the +competition and the game rules are announced and any questions you have will be +answered. + +Typically this is a one day in-person event in October (usually a Saturday). +Throughout the day there are Blueshirts (our awesome volunteers!) around in +person, ready to answer any questions and to help you through the +[microgames][microgames]. The microgames help you become familiar with the +[kit][kit] which is loaned to all teams and should kickstart some ideas for your +robot’s design. + +## Mentoring + +Shortly after Kickstart we aim to pair up teams with a volunteer mentor who can +guide the team and help them with any technical questions. Where possible the +mentor will join the team's meetings in person, though we also offer remote +mentors if that is not possible. + +All teams also have access to our [Discord][discord] server where they can chat +with all our volunteers (as well as other teams) at any time. + +## Your time + +Most teams work on their robot for at least two hours a week, with some teams +spending four hours or more. How this time is scheduled varies between teams -- +some have more than one meeting a week, others have less frequent but longer +sessions. + +To get the most out of the time, ensure sessions are long enough to make useful +progress after allowing for setting up beforehand and tidying away afterwards. + +## Tech Days + +Throughout the year [Tech Days][tech-days] provide opportunities to spend a +whole day (usually a Saturday) working on your robot, with lots of help +available. They’re also an opportunity to see how other teams are doing or get +more direct help with your robot. + +We provide a space for you to work in, with power and internet access, as well +as volunteers able to help with the kits and hands-on guidance with your robot. + +## Competition + +The Competition event is a two day event in spring. You'll put your robot to the +test in a weekend of tinkering and matches. + +You'll have a team pit for you to work in, with power and internet access, and +throughout the weekend there are volunteers around to help with the kits and +hands-on guidance with your robot. We also provide a test arena which you can +use to check the improvements you're making to your robot. + +Typically there are blocks of league matches on the Saturday and on Sunday +morning, with time to improve your robot between appearances. On Sunday +afternoon you'll advance into the knockout stages, and can go on to win prizes. + + +[team-supervisor]: {{ site.baseurl }}/robots_101/team_supervisor +[microgames]: {{ site.baseurl }}/competitor_resources/microgames +[kit]: {{ site.baseurl }}/kit/ +[discord]: {{ site.baseurl }}/tutorials/discord +[tech-days]: {{ site.baseurl }}/robots_101/tech_days