replaced engineering with mechanical engineering

src/components/leadership/LeadershipContainer.astro

@@ -58,7 +58,7 @@ const { leadership, height, width, tSize, hSize } = Astro.props;
             {
               [
                 "Software Engineering",
-                "Engineering",
+                "Mechanical Engineering",
                 "Business",
                 "Strategy",
               ].includes(leadership.department) ? (

src/content/history/2010.md

@@ -18,7 +18,7 @@ awards:
 
 2010 was, without a doubt, our most successful season. At our first event, the New York City Regional, all the teams were walking around saying that we would be their first pick. We ended up being the first pick of the number 1 alliance captain, 341. We joined forces with 341 and blazed a trail through every alliance in the elimination rounds, winning the New York City Regional for the second time.
 
-For our amazing autonomous mode, which often scored both the balls it picked up, we earned the Rockwell Automation Innovation in Control Award. If that was not enough, we also were an alliance captain at the Connecticut regional and won the most prestigious award in F.I.R.S.T., the Chairman's award, at the Connecticut Regional making 2010 the first year we qualified 2 times for the championship. Then at the Championship in Atlanta our President of Engineering, Seth Berg, was chosen as part of the first group of Dean's List honorees. He has gone on to be one of many 694 graduates that has studied at MIT. In 2010 the team saw a large influx of newbies who were just as passionate and hard working as the veterans. During the six week Build Season, the team often stayed until 8 PM to work on the bot. The designs for the robot were finished within the first 2 weeks, while team pressed to build the robot in the remaining time. Our six-wheel drive train had a dropped center wheel built to allow easy movement across bumps. Our kicker was inspired by a cam design from an MIT project, and was capable of kicking soccer balls from one end of the field to the other. The team initially decided to ignore the hanging aspect of the game, but a few team members and mentors stubbornly continued building an award-winning hanger. The ability of Donovan to hang at the end of each match scored us many points and contributed greatly to our victory at the New York City Regional.
+For our amazing autonomous mode, which often scored both the balls it picked up, we earned the Rockwell Automation Innovation in Control Award. If that was not enough, we also were an alliance captain at the Connecticut regional and won the most prestigious award in F.I.R.S.T., the Chairman's award, at the Connecticut Regional making 2010 the first year we qualified 2 times for the championship. Then at the Championship in Atlanta our President of Mechanical Engineering, Seth Berg, was chosen as part of the first group of Dean's List honorees. He has gone on to be one of many 694 graduates that has studied at MIT. In 2010 the team saw a large influx of newbies who were just as passionate and hard working as the veterans. During the six week Build Season, the team often stayed until 8 PM to work on the bot. The designs for the robot were finished within the first 2 weeks, while team pressed to build the robot in the remaining time. Our six-wheel drive train had a dropped center wheel built to allow easy movement across bumps. Our kicker was inspired by a cam design from an MIT project, and was capable of kicking soccer balls from one end of the field to the other. The team initially decided to ignore the hanging aspect of the game, but a few team members and mentors stubbornly continued building an award-winning hanger. The ability of Donovan to hang at the end of each match scored us many points and contributed greatly to our victory at the New York City Regional.
 
 While the engineers worked hard to design and build the robot, as well as the field, the programmers were also working hard at their end. Before the season began, the senior programmers taught newbies how to use and program in Java, making the change from C++. Then when build season kicked off, everyone was ready to go. New and old programmers worked together to convert old code into Java, as well as generate new code for the autonomous period and the robots camera function. Multiple routines for the autonomous period were developed anticipating many different situations. A combination of rotary encoders, a gyroscope and a camera targeting system was used to auto-align our robot to the goal. Our autonomous period was one of the best at the New York Regional.
 

src/content/history/2011.md

@@ -19,6 +19,6 @@ awards:
 
 2011 for StuyPulse could be described with two words: roller coaster. After kickoff in January, we started once more to design, build and program our robot from scratch. After six weeks of intense work, we were rewarded with DESdroid, our new robot for the season. We showed up at the New York City Regional with a lot of confidence and we got our teeth kicked in. Through great strategy we made it to the quarter finals but the robot was not up to par. We won the Autodesk Animation Award at the New York City Regional which was a giant step for our very young animation team. Also, to his complete surprise, Alex Carrillo, our Director of Programming, became a Dean's List Finalist at the New York Regional. We showed up in Connecticut with a new attitude and a new mini-bot known as the WildCard. We played as hard as we possibly could, but again did not advance past the quarter-finals. During the award ceremonies, however, we walked away with the very prestigious Chairman's award for the second year in a row which qualified us for the championship. At the championships we played better than ever after a coaching change and many minor adjustments to the robot. For the first time ever we were an alliance captain at the Championship. We joined forces with 195 and, for the second year in a row, 341. We finished in the quarter-finals, captaining the 5th alliance that gave the alliance it faced quite a run for their money.
 
-In designing our 2011 robot, DESdroid, we had two main goals: fluid inner-tube placement and quick mini-bot deployment. To accomplish our tube placement goal, our VP of Engineering, Jake Potter, designed and built a grabber that could acquire, manipulate, and place a tube. The arm's main component was a hand with four rollers wrapped in tread and connected by polycord. The rollers on top and bottom spun in different directions to acquire, rotate and place the tubes. For the first time in our team's history, we used a mechanum drivetrain setup. The mechanum wheels allowed the robot to strafe and easily change positions to place the tubes on the rack. We accomplished our mini-bot deployment goal with a drawbridge and a rack and pinion motor setup. The drawbridge was a guider that aligned the deployer with the pole. The drawbridge was kept up against the robot until the end game when it was lowered. The rack and pinion moved the minibot plate up to so it could attach to the pole.
+In designing our 2011 robot, DESdroid, we had two main goals: fluid inner-tube placement and quick mini-bot deployment. To accomplish our tube placement goal, our VP of Mechanical Engineering, Jake Potter, designed and built a grabber that could acquire, manipulate, and place a tube. The arm's main component was a hand with four rollers wrapped in tread and connected by polycord. The rollers on top and bottom spun in different directions to acquire, rotate and place the tubes. For the first time in our team's history, we used a mechanum drivetrain setup. The mechanum wheels allowed the robot to strafe and easily change positions to place the tubes on the rack. We accomplished our mini-bot deployment goal with a drawbridge and a rack and pinion motor setup. The drawbridge was a guider that aligned the deployer with the pole. The drawbridge was kept up against the robot until the end game when it was lowered. The rack and pinion moved the minibot plate up to so it could attach to the pole.
 
 Our mini bot, the WildCard, utilized an ultra light aluminum frame, a neodymium rare earth magnet pole attachment system, and direct drive shafts. Wildcard accelerated up the pole in two seconds and helped us to win numerous matches, quickly becoming one of our favorite robots.

src/content/news/2018-04-15-nyc-regional.md

@@ -9,7 +9,7 @@ Last weekend, we competed in the New York City Regional.
 Wildcard made team history by going undefeated throughout the entire regional.
 Along with teams 1796 and 743, we won the event, qualifying us for World Championships in Detroit later this month.In addition, we also qualified to compete at the championships by winning the Chairman’s Award, the most prestigious award that can be award to a FRC Team.
 
-Congratulations to our coach, James Lonardo, for winning the Woodie Flowers Finalist, and our Vice President of Engineering, Navid Kashem, for winning Dean’s List Finalist!
+Congratulations to our coach, James Lonardo, for winning the Woodie Flowers Finalist, and our Vice President of Mechanical Engineering, Navid Kashem, for winning Dean’s List Finalist!
 We are so happy for their accomplishments and thankful for their contributions to the team.
 Our success made us the 4th team to ever win three banners at the same regional.
 Let’s go StuyPulse!

src/data/leadership.yml

@@ -8,22 +8,22 @@
   description: The President of Software Engineering primarily manages the development of robot code and all related software. They also manage the design and development of all human interfaces and control systems. The PoSE is responsible for the production of documentation concerning the control system on all levels, such as pinout sheets and systems check guidelines. They work closely with the PoE to effectively manage the development of the control system alongside the hardware. The PoSE also collaborates with the strategy team to develop effective solutions for both the teleoperated and autonomous modes, as well as the Business team to coordinate events and regional activities, such as seminars. The PoSE must effectively manage the software development team in order to accomplish these responsibilities and must have the same level of familiarity with the robot as the PoE.
   department: Software Engineering
 - name: Harry B.
-  position: President of Engineering
+  position: President of Mechanical Engineering
   image: https://stuypulse.nyc3.cdn.digitaloceanspaces.com/site/img/leadership/HarryB.jpg
-  description: The President of Engineering is familiar with every part of the robot, able to explain the part to another team member or a judge, as well as able to repair any part of the robot if it is broken. They are also knowledgeable about the details of the Chairman’s Award submission and other award submissions.
-  department: Engineering
+  description: The President of Mechanical Engineering is familiar with every part of the robot, able to explain the part to another team member or a judge, as well as able to repair any part of the robot if it is broken. They are also knowledgeable about the details of the Chairman’s Award submission and other award submissions.
+  department: Mechanical Engineering
 - name: Cindy Z.
   position: President of Business
   description: The President of Business holds final responsibility for all outreach, logistics, and award submissions for the team. They have full knowledge of all awards and shall present the Chairman’s Award or assign the presentation to someone else deemed competent. The PoM also has adequate knowledge of the other two departments.
   department: Business
 - name: Kalimul K.
   position: Vice President of Software Engineering
-  description: The Vice President of Software Engineering is the second­-in-­command for the Software Engineering department. They have knowledge of what the President of Software Engineering is currently doing and should be able to direct the Software Engineering department in the event of the PoSE’s absence, as well as collaborate with the President of Engineering in managing the overall robot project.
+  description: The Vice President of Software Engineering is the second­-in-­command for the Software Mechanical Engineering department. They have knowledge of what the President of Software Engineering is currently doing and should be able to direct the Software Mechanical Engineering department in the event of the PoSE’s absence, as well as collaborate with the President of Mechanical Engineering in managing the overall robot project.
   department: Software Engineering
 - name: Henry Z.
-  position: Vice President of Engineering
-  description: The Vice President of Engineering is considered the second-in-command for the Engineering department. They have knowledge of what the Presidents are currently doing and is able to direct the Engineering department in the event of the PoE’s absence. The VPoE also has extensive knowledge of each part of the robot as well as basic knowledge of all awards submissions.
-  department: Engineering
+  position: Vice President of Mechanical Engineering
+  description: The Vice President of Mechanical Engineering is considered the second-in-command for the Mechanical Engineering department. They have knowledge of what the Presidents are currently doing and is able to direct the Mechanical Engineering department in the event of the PoE’s absence. The VPoE also has extensive knowledge of each part of the robot as well as basic knowledge of all awards submissions.
+  department: Mechanical Engineering
 - name: Rachel U.
   position: Vice President of Business
   image: https://stuypulse.nyc3.cdn.digitaloceanspaces.com/site/img/leadership/RachelK.jpg
@@ -50,52 +50,52 @@
   position: Director of Electronics
   image: https://stuypulse.nyc3.cdn.digitaloceanspaces.com/site/img/leadership/RainS.jpg
   description: The Director of Electronics sets up and manages the electronic systems on the robot to FIRST regulations. They cooperate with both engineers and software engineers to ensure that the electronic systems are organised and able to be modified if needed. The DoE is also responsible for the education of other members in the electronics subdepartment.
-  department: Engineering
+  department: Mechanical Engineering
 - name: Rachel K.
   position: Co-Assistant Director of Electronics
   image: https://stuypulse.nyc3.cdn.digitaloceanspaces.com/site/img/leadership/RachelK%20(3).jpg
   description: The Assistant Director of Electronics is familiar with all aspects of the electronic systems on the robot and be able to assume the jobs of Director of Electronics at any time.
-  department: Engineering
+  department: Mechanical Engineering
 - name: Elin K.
   position: Co-Assistant Director of Electronics
   image: https://stuypulse.nyc3.cdn.digitaloceanspaces.com/site/img/leadership/ElinK.jpg
   description: The Assistant Director of Electronics is familiar with all aspects of the electronic systems on the robot and be able to assume the jobs of Director of Electronics at any time.
-  department: Engineering
+  department: Mechanical Engineering
 - name: Ryan Z.
   position: Director of Lab Operations and Safety
   image: https://stuypulse.nyc3.cdn.digitaloceanspaces.com/site/img/leadership/RyanZ.jpg
   description: The Director of Lab Operations and Safety, at the highest level, is responsible for the smooth running of the team's workspaces. They are responsible for keeping a detailed inventory of the tools and construction materials in the laboratory as well as a record of materials used in the construction of the robot. The Co-DoLOS is also responsible for ensuring that all necessary safety rules are observed in the lab during build season. The Co-DoLOS will automatically be appointed Safety Captain at the competition and will be responsible for carrying out all duties therein.
-  department: Engineering
+  department: Mechanical Engineering
 - name: Jaco X.
   position: Director of Design
   image: https://stuypulse.nyc3.cdn.digitaloceanspaces.com/site/img/leadership/JacoX.jpg
   description: The Director of Design is responsible for the upkeep of the CAD model of the robot and all elements thereof with the aid of a CAD team. This CAD team is to be instructed in the use of CAD programs and led by the Director of Design.
-  department: Engineering
+  department: Mechanical Engineering
 - name: Amelia N.
   position: Director of Machining
   image: https://stuypulse.nyc3.cdn.digitaloceanspaces.com/site/img/leadership/AmeliaN.jpg
   description: The Primary Machinist is responsible for the maintaining the mill, lathe, and their parts. He/she must also make sure that there will be at least two members of the team that will be able to use the mill in the upcoming year, including the Primary Machinist. If there are fewer than two such members, the Primary Machinist is responsible for training new members.
-  department: Engineering
+  department: Mechanical Engineering
 - name: Esther L.
   position: Co-Assistant Director of Machining
   image: https://stuypulse.nyc3.cdn.digitaloceanspaces.com/site/img/leadership/EstherL.jpg
   description: The Assistant Machinist is to be familiar with all aspects of machining and be ready to assume the jobs of Director of Machining if necessary.
-  department: Engineering
+  department: Mechanical Engineering
 - name: Tracy Y.
   position: Co-Assistant Director of Machining
   image: https://stuypulse.nyc3.cdn.digitaloceanspaces.com/site/img/leadership/TracyY.jpg
   description: The Assistant Machinist is to be familiar with all aspects of machining and be ready to assume the jobs of Director of Machining if necessary.
-  department: Engineering
+  department: Mechanical Engineering
 - name: Zhi Han Y.
   position: Director of Field Construction
   image: https://stuypulse.nyc3.cdn.digitaloceanspaces.com/site/img/leadership/ZhiHan.jpg
   description: It is the job of the Director of Field Construction to construct the field of the released game with acceptable accuracy. For each function that the robot has to perform, it is this person’s responsibility to ensure that at least one set of the field elements involved in that task is procured and produced. However, the DoFC will also be responsible for all other fields, including FLL, FTC, and FRC fields. They are responsible for the upkeep of the shipping/robot crates and building new robot carts.
-  department: Engineering
+  department: Mechanical Engineering
 - name: Vinson C.
   position: Director of Procurement
   image: https://stuypulse.nyc3.cdn.digitaloceanspaces.com/site/img/leadership/VincentC.jpg
   description: The Director of Procurement is responsible for overseeing and actualizing the procurement of goods necessary for the team’s operation. The DoP is similarly responsible for identifying adequate substitutes when a necessary resource cannot be obtained from the traditional supplier for a reasonable cost. All procurement requests must be approved by a faculty advisor. The DoP is also required to maintain a detailed, uptodate account of the team’s expenditures, available on request.
-  department: Engineering
+  department: Mechanical Engineering
 - name: Kara Y.
   position: Director of Finance
   image: https://stuypulse.nyc3.cdn.digitaloceanspaces.com/site/img/leadership/KaraY.jpg