-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathteam.html
More file actions
190 lines (163 loc) · 6.07 KB
/
team.html
File metadata and controls
190 lines (163 loc) · 6.07 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8" />
<title>Slugbotics | SOMARS – Team</title>
<link rel="stylesheet" href="style.css" />
</head>
<body>
<!-- Navbar -->
<header class="navbar">
<div class="nav-container">
<div class="nav-logo">
<span class="slug-icon">🚁</span>
<span class="nav-title">Slugbotics | SOMARS</span>
</div>
<nav class="nav-links">
<a href="index.html">Home</a>
<div class="nav-item has-dropdown">
<a href="team.html" class="nav-link-with-dropdown active">Team</a>
<div class="dropdown">
<a href="mechanical.html">Mechanical</a>
<a href="embedded.html">Embedded Systems</a>
<a href="perception.html">Perception</a>
<a href="simulations.html">Simulations</a>
</div>
</div>
<a href="sponsors.html">Sponsors</a>
<a href="index.html#contact">Contact</a>
</nav>
<button class="nav-toggle" id="navToggle">☰</button>
</div>
</header>
<!-- Page Header -->
<header class="page-header">
<div class="page-header-inner">
<h1>Team</h1>
<p>Meet the people building SOMARS — one subteam at a time.</p>
</div>
</header>
<!-- Why subteams -->
<section id="why-subteams" class="section">
<h2>Why Subteams?</h2>
<p>
Autonomous drones are complex systems that span mechanical engineering,
electronics, real-time software, computer vision, and simulation.
No single person can master all of it — subteams let members specialize
while still collaborating toward a single flying vehicle.
</p>
<p>
Each subteam owns a core area of the drone, working in parallel so
progress can happen quickly across the whole stack. Members get focused
experience in the domain they care about most.
</p>
</section>
<!-- Subteam strips -->
<section id="subteams" class="subteam-strips">
<a href="mechanical.html" class="subteam-strip strip-mechanical">
<div class="subteam-strip-bg">⚙️</div>
<div class="subteam-strip-content">
<span class="strip-icon">⚙️</span>
<span>Mechanical</span>
</div>
</a>
<a href="embedded.html" class="subteam-strip strip-embedded">
<div class="subteam-strip-bg">🔌</div>
<div class="subteam-strip-content">
<span class="strip-icon">🔌</span>
<span>Embedded Systems</span>
</div>
</a>
<a href="perception.html" class="subteam-strip strip-perception">
<div class="subteam-strip-bg">👁️</div>
<div class="subteam-strip-content">
<span class="strip-icon">👁️</span>
<span>Perception</span>
</div>
</a>
<a href="simulations.html" class="subteam-strip strip-simulations">
<div class="subteam-strip-bg">🌐</div>
<div class="subteam-strip-content">
<span class="strip-icon">🌐</span>
<span>Simulations</span>
</div>
</a>
</section>
<!-- Q & A -->
<section id="qa" class="section">
<h2>Q & A</h2>
<div class="qa-list">
<div class="qa-item">
<h3>Do I have to pick just one subteam?</h3>
<p>
Not necessarily. Many members focus on one subteam at first to build
depth, then branch into other areas once they're comfortable. We
encourage specialization early and cross-pollination later.
</p>
</div>
<div class="qa-item">
<h3>Can I switch subteams?</h3>
<p>
Yes — talk with the subteam leads and we'll help you transition
without disrupting ongoing work. People switch when their interests
evolve or they want a new challenge.
</p>
</div>
<div class="qa-item">
<h3>How experienced do I need to be?</h3>
<p>
No prior drone or robotics experience is required. We'll point you
toward learning resources and pair you with more experienced members.
Curiosity and consistency matter far more than what you already know.
</p>
</div>
<div class="qa-item">
<h3>What majors are welcome?</h3>
<p>
All majors! We need mechanical engineers, computer scientists,
electrical engineers, and anyone who's excited about autonomous
systems. If you're not sure where you fit, come to a meeting and
we'll figure it out together.
</p>
</div>
</div>
</section>
<!-- How to join -->
<section id="join" class="section alt">
<h2>How Do I Join?</h2>
<p>Getting involved is straightforward — here's the usual flow:</p>
<div class="qa-list" style="margin-top:1.25rem;">
<div class="qa-item">
<h3>1. Complete the SlugWorks Canvas & join our Discord</h3>
<p>
Most of our work happens in SlugWorks (BE-49). Complete the safety
training Canvas module and do a walkthrough to gain workspace access.
Join our Discord to stay up to date on meetings and announcements.
</p>
<span class="placeholder-note">TO BE FINISHED LATER — add Canvas and Discord links</span>
</div>
<div class="qa-item">
<h3>2. Visit a few subteam meetings</h3>
<p>
Check out subteam meeting times listed on each subteam page. If the
times don't work for your schedule, reach out to the leads — we
reschedule at the start of every quarter to fit everyone.
</p>
</div>
<div class="qa-item">
<h3>3. Commit to a subteam</h3>
<p>
Once you've explored, pick a primary subteam and start taking on
tasks — CAD modeling, firmware, vision code, simulation scripts,
whatever fits that group's current needs.
</p>
</div>
</div>
<p class="card-meta" style="margin-top:1rem;">
Not sure where to start? Ask any subteam lead or message us through the
contact info on the <a href="index.html#contact" style="color:#7ed957;">home page</a>.
</p>
</section>
<script src="script.js"></script>
</body>
</html>