-
Notifications
You must be signed in to change notification settings - Fork 0
/
hack-club-jams-first-big-project.html
99 lines (90 loc) · 7.55 KB
/
hack-club-jams-first-big-project.html
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
<!DOCTYPE html>
<html>
<head>
<title>Hack Club Journeys - Thomas</title>
<meta name="title" content="Hack Club Journeys - Thomas" />
<meta name="description" content="Thomas's wild journeys with Hack Club" />
<meta property="og:type" content="website" />
<meta property="og:title" content="Hack Club Journeys - Thomas" />
<meta property="og:description" content="Thomas's wild journeys with Hack Club" />
<meta property="og:image" content="https://cloud-regpmmq7q-hack-club-bot.vercel.app/0journey-cover.png" />
<meta property="twitter:card" content="summary_large_image" />
<meta property="twitter:title" content="Hack Club Journeys - Thomas" />
<meta property="twitter:description" content="Thomas's wild journeys with Hack Club" />
<meta property="twitter:image" content="https://cloud-regpmmq7q-hack-club-bot.vercel.app/0journey-cover.png" />
<link rel="apple-touch-icon" sizes="57x57" href="/hc-journey/apple-icon-57x57.png">
<link rel="apple-touch-icon" sizes="60x60" href="/hc-journey/apple-icon-60x60.png">
<link rel="apple-touch-icon" sizes="72x72" href="/hc-journey/apple-icon-72x72.png">
<link rel="apple-touch-icon" sizes="76x76" href="/hc-journey/apple-icon-76x76.png">
<link rel="apple-touch-icon" sizes="114x114" href="/hc-journey/apple-icon-114x114.png">
<link rel="apple-touch-icon" sizes="120x120" href="/hc-journey/apple-icon-120x120.png">
<link rel="apple-touch-icon" sizes="144x144" href="/hc-journey/apple-icon-144x144.png">
<link rel="apple-touch-icon" sizes="152x152" href="/hc-journey/apple-icon-152x152.png">
<link rel="apple-touch-icon" sizes="180x180" href="/hc-journey/apple-icon-180x180.png">
<link rel="icon" type="image/png" sizes="192x192" href="/hc-journey/android-icon-192x192.png">
<link rel="icon" type="image/png" sizes="32x32" href="/hc-journey/favicon-32x32.png">
<link rel="icon" type="image/png" sizes="96x96" href="/hc-journey/favicon-96x96.png">
<link rel="icon" type="image/png" sizes="16x16" href="/hc-journey/favicon-16x16.png">
<link rel="manifest" href="/hc-journey/manifest.json">
<meta name="msapplication-TileColor" content="#ffffff">
<meta name="msapplication-TileImage" content="/hc-journey/ms-icon-144x144.png">
<meta name="theme-color" content="#ffffff">
<link rel="stylesheet" type="text/css" href="styles.css">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
</head>
<body style="display: flex; justify-content: center;">
<div style="max-width: 720px;">
<a href="./index.html">
<div class="header">
<h1>Journeys @</h1>
<img style="height: 78px" src="./assets/hc-logo.png"/>
<h1 id="date">(2023-2024)</h1>
</div>
</a>
<p><a href="./index.html">Home</a> / <a href="">Hack-Club-Jams-First-Big-Project</a></p>
<p>
JAMS! I started with a question of: "How can we make workshops awesome?"
<br/>
<img style="width: 100%" src="./assets/figmaJam.png"/>
<br/>
When I was in High School, I never used the workshops that Hack Club provided. I found it more work to go through each one and create slides around them than to just make my own.
<br/>
<br/>
I also think that making your own club meeting content makes you a better leader because you understand the content like the back of your hand & it is authentic to you & your club.
<br/>
<br/>
When I thought about what made great club meetings, the core thing for me was that it met the following conditions
<ul>
<li>Every end project from the workshop was unique, leaving the attendee feeling ownership over what they made</li>
<li>Workshops could be done solely in the browser (no need to download anything or to use a device other than a chromebook)</li>
<li>Workshops needed to stem from some genunie curiosity or aspirational project that the creator wanted to make</li>
</ul>
I also recognized the problem with each workshop being totally standalone: there is no concept of progression because each week you're hopping from one thing to another.
<br/>
<br/>
My solution to this problem were "batch jams" where a Jam could have multiple parts where each part is done in a club meeting. There are some problems with this concept (like for example it is difficult to account for members that join/leave mid-way through the Club). Regardless of the issues with batches, I still wanted to provide them as an option for clubs.
<br/>
<br/>
I also thought the word "workshop" felt a bit corporate and that it seemed like a class where I wanted it to feel like a bunch of friends getting together making something fun: "jamming out a project" (this was the rationale behind calling it Hack Club Jams).
<br/>
<img style="width:280px" src="./assets/jams.png"/>
<br/>
I started with the design (see above image) & then I made <a href="https://jams.hackclub.com/batch/webOS">WebOS</a> which was the first batch Jam! The concept behind the Jam was inspired a goal I had of making my own operating system when I was 7 or 8 years old and did not know how to code. I realized I could try making a web operating system in just pure vanilla javascript. I started breaking it down in my notebook as to how I would do this, I made a prototype, and then I turned it into slides (same process I did with my Hack Club).
<br/>
<br/>
I was working with Christina at the time and I was shocked when she was willing to give the project funds to host a bounty and pay Hack Clubbers to make content for the Jams site. This was the first time that a project I was working on had received funding.
<br/>
<br/>
I worked for weeks with every person participating in the bounty to help make their Jam fit that criteria that I mentioned (web compatible, hackable with different end results, and from a place of genuine curiosity). Mid-way through I remember looking through the Jams and Zach asking me what I thought of the content so far. I said: "honestly, right now it is really bad. I am going to figure out a way to turn this around. I am going to figure out a way to make them great."
<br/>
<br/>
Here I learned a lesson which is to always wait to pay a person doing a contract job until you are satisfied with the product that they promised to deliver. I worked with every person to help them frame their Jam as something that teenagers could fill a room with and something that they would enjoy leading a meeting about. Deciding to not give up but to rather take control of the situation and turn it around to make the content better was a key lesson for me and something I am proud of.
<br/>
<br/>
I think a lot of people at Hack Club (HQ & the community) question whether it was a good idea for us to break away from our <a href="https://workshops.hackclub.com/">workshops.hackclub.com</a> site to make <a href="https://jams.hackclub.com/">jams.hackclub.com</a>. That's up to each individual to decide. I personally am for it.
<br/>
<br/>
<p><a href="./pizza-grant-first-partnership.html">Pizza Grant - first partnership →</a></p>
</p>
</body>
</html>