-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathrss.xml
67 lines (67 loc) · 8.75 KB
/
rss.xml
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
<?xml version="1.0"?>
<rss version="2.0">
<channel>
<title>ScribeHacks Blog</title>
<link>https://scribehacks.tech</link>
<description>ScribeHacks is a highschool hackathon happening on April 17-18, 2021 in the Bay Area.</description>
<language>en</language>
<pubDate>Fri, 24 Jul 2020 19:31:58 -0700</pubDate>
<lastBuildDate>Fri, 24 Jul 2020 19:31:58 -0700</lastBuildDate>
<item>
<guid isPermalink="true">https://scribehacks.tech/2020/Technology-and-Social-Media/</guid>
<title>Technology and Social Media</title>
<link>https://scribehacks.tech/2020/Technology-and-Social-Media/</link>
<pubDate>Fri, 24 Jul 2020 19:31:58 -0700</pubDate>
<description><![CDATA[ <html><head></head><body><h2 id="Back-to-Working-Hard"><a href="#Back-to-Working-Hard" class="headerlink" title="Back to Working Hard"></a>Back to Working Hard</h2><p>After a much needed summer break, our team has started working hard once again, and we&#x2019;ve accomplished a lot.</p>
<p>We&#x2019;ve set up our social medias! We have Twitter (@Scribe_Hacks), Instagram (@scribehacks), and a Facebook soon, so go follow us! We&#x2019;ll be using these accounts to post updates before and during the hackathon. We&#x2019;ll also be using them to give shoutouts to our sponsors and introduce the team.</p>
<p>Our tech team has also been working extremely hard on the website! They&#x2019;re trying to create the best possible user experience so that our website is easy to use, and you can get all the information you need about the hackathon in one place. Unfortunately, our old design had some issues, so they went back to the drawing board to create a new one that can run a lot smoother. We were having some issues with our scrolling getting in the way of the rest of the design. Some words weren&#x2019;t showing, while others weren&#x2019;t showing up quite where we wanted them too. Regardless, we are close to getting our new and improved website up and running and we&#x2019;re so excited to share with you!</p>
<p>They have also been working hard on the Capture the Flag event for the hackathon. The Capture the Flag challenge will consist of having multiple teams attempt challenges to try and get a string called the flag which they receive points for if the string is correct. There are going to be a lot different types of challenges, and they all share will some sort of cryptography or encryption element to them. For this challenge, we&#x2019;re planning on using Python with Flask for the Frontend and Python with SQLite for the backend (keeping track of points and teams). There are going to be so many fun and interesting challenges, and our tech team is so excited to be able to share it with you all.</p>
<script>
document.querySelectorAll('.github-emoji')
.forEach(el => {
if (!el.dataset.src) { return; }
const img = document.createElement('img');
img.style = 'display:none !important;';
img.src = el.dataset.src;
img.addEventListener('error', () => {
img.remove();
el.style.color = 'inherit';
el.style.backgroundImage = 'none';
el.style.background = 'none';
});
img.addEventListener('load', () => {
img.remove();
});
document.body.appendChild(img);
});
</script><link rel="stylesheet" href="/css/spoiler.css" type="text/css"><script src="/js/spoiler.js" type="text/javascript" async></script></body></html> ]]></description>
</item>
<item>
<guid isPermalink="true">https://scribehacks.tech/2020/Month-1-Planning-and-Making/</guid>
<title>Month 1: Planning and Making</title>
<link>https://scribehacks.tech/2020/Month-1-Planning-and-Making/</link>
<pubDate>Thu, 21 May 2020 19:34:18 -0700</pubDate>
<description><![CDATA[ <html><head></head><body><h2 id="Week-0"><a href="#Week-0" class="headerlink" title="Week 0"></a>Week 0</h2><p>This week is called Week 0 because it was when the idea was conceived and we made some progress in the hackathon before we waited like 6 months to start working on it for real. During this week, it was just the two team members, me (Kai) and Soham. We decided to start work on the hackathon after we went to another hackathon and was very disappointed in it. We were disappointed in it because we were spoiled by another hackathon, my first hackathon, Los Altos Hacks. We wanted our hackathon to be just as good, so with our tired minds after the hackathon, we quickly made a list of companies to email for sponsors, food, events, and prizes. After that day we barely worked any more on it except for a few times when we just wanted to add like another company onto it.</p>
<h2 id="How-Elon-Started-a-Hackathon"><a href="#How-Elon-Started-a-Hackathon" class="headerlink" title="How Elon Started a Hackathon"></a>How Elon Started a Hackathon</h2><p>After a long hiatus, the Coronavirus quarantine got to us and so did the Elon Musk AMA with Hack Club. Soham messaged me to say that he wanted to work more on our hackathon, so we quickly signed up for the Hack Club Slack like many others. From there it was about another week until we started to work on it. A week passes by, (yes I still count it as the same week because nothing major happened) and we get a Discord Server up and have the team join. It was fairly quick as we had only 7 people on the team at the time, including me and Soham. We then made a GitHub for the hackathon and went straight to work assigning roles for everyone. We already had an idea for each person. We tried to have about 3 people on each team with one head of the team. The first task was put out and it was to make the website, as a head of tech this also included me. I made the design in XD in a day for the front page and the teams page. I asked my team if it was good and they said that it looked good. We went straight to work making the website. The idea was to make it using plain HTML/CSS and JavaScript with a few JS libraries to help us. On the Monday I made the front page and pushed it to GitHub. Another person on tech decided to start working on the the teams page while the last person in my team was tasked was making animations and UI elements. On Tuesday I had the idea to setup a blog for the website as Hack Club has been trying to make sure that it keeps its brand as transparent as possible. We decided that it was a good idea to make a blog not only to be transparent but also track our progress. I set up the blog you see here using Hexo and the minos theme which I tweaked to make it closer to our colors. I published the blog and called it a day. The next day, Wednesday was when the My MLH integration started to happen. I made a dummy app and put a button on the website which led to a success page. This was pretty easy to set up. During this time also, the outreach team made a sign up form for people who wanted to join our team and we invited two more people to join to be educational partners. Also Soham setup a hack club bank and registered for the MLH sponsorship. Thursday is the date I am writing this blog and so far, it seems to be working well. The team seems to have milestones and dates to meet in mind and our team is working hard to meet those.</p>
<script>
document.querySelectorAll('.github-emoji')
.forEach(el => {
if (!el.dataset.src) { return; }
const img = document.createElement('img');
img.style = 'display:none !important;';
img.src = el.dataset.src;
img.addEventListener('error', () => {
img.remove();
el.style.color = 'inherit';
el.style.backgroundImage = 'none';
el.style.background = 'none';
});
img.addEventListener('load', () => {
img.remove();
});
document.body.appendChild(img);
});
</script><link rel="stylesheet" href="/css/spoiler.css" type="text/css"><script src="/js/spoiler.js" type="text/javascript" async></script></body></html> ]]></description>
</item>
</channel>
</rss>