Inspiration

Our inspiration for this site was the past and first hackathon that Kyle and Nandini did, HS I/O 2022. We did OSINT research on one of the members of the judges. It was a bad idea in terms of ethics, but our project was unique and educational. It was teamwork and the tech we used that made our project stand out. It was the impactfulness and function. What is more impactful than demonstrating that kids can find enough information to stage a social engineering attack on someone they’ve never met? As a result, we built this site to be a continuation of our hackathon ideals: usefulness, creativeness, and uniqueness. Our specific website mission was also related to our pasts. Our experiences as students always mean time is short and schools never seem to offer enough. We wanted to enable schools to provide a resource that shows students what they can do in school during school time, for our sakes, and others.

What it does

Our website is nothing fancy. It has no machine learning, no object detection, no buzzwords. It serves a purpose, and that is to provide interesting projects that anyone can try, from anywhere. We have included something for everyone and it is scalable to include numerous projects in the future. Simply said, WoGO helps schools by handpicking a unique assortment of things that inspire people to learn. An idea that many have tried to do before, but that we have done simple and right. A website that works fast and well on phones, that doesn’t reinvent the wheel, that simply brings the best resources that already exist together, and has a killer distribution method. Our wish is that you see the experiences we have found and put together and think, “My school doesn’t have many or any people who know stuff like this, I’ll post up the flier for the website so that my peers can find out.”

How we built it

Our website was built using Hugo, which is a static site generator. We collaborated via Google Docs using markdown. Kyle copied the markdown into Hugo and ran it locally on his Windows computer and Hugo gave us amazing static assets to host on Github Pages. We also must provide gratitude to the developer of the theme we used, Hugo-Winston, because without it our website would have looked nowhere as good.

Challenges we ran into

We ran into many technical challenges. Firstly, finding a Hugo theme that would work with our idea was rough. We do not know how to program in Go to make our own theme or CSS so that was the first.

Second, we had a lot of issues with syntax. It was my first time really working with .toml/.yml files. Things like embedding repl.it was an issue. It was our first experiences making a quality looking website in general.

Third, we struggled with all the new things in general: Git, Github, Windows CMD, Hugo, devpost, collaboration with multiple people, and organization. However, we still ended up making a great website despite the hurdles, because we kept sight of the bigger picture and moved on.

Accomplishments that we're proud of

We are proud of creating a site that personifies what simple tech and a strong mission can be. Our site has a purpose, it can be distributed, and it can help inspire many people to learn new things. It’s not magic. It’s a tried and true style of website, except ours is reliable, fast, simple, and above all else useful. Compared to other sites that have the same kind of information, ours accomplishes our mission.

Kyle is also proud of his progress in using Hugo. He had been for weeks floundering around trying to make his personal site, but because of the hackathon has managed to gain a lot of experience on using it.

What we learned

We all learned so much from this project. We all were able to get intros to things like Python, CTF, Google Dorking, and more. All of us had different levels of experience in different topics, and it was so cool to see everyone help and learn from one another. Additionally, we got to experience unfamiliar software. Software such as GitHub, Excel, Hugo, and even Devpost all had their own little quirks, and while it was a challenge to navigate all of them, we became stronger because of it. The best problems are the ones you solve for yourself and we accomplished that. We also learned the value of organization, planning, cooperation and the tools that enable it. One thing we learned that will apply to future hackathons we need to plan a way for all members of the team to contribute to the technical portion of the site.

What's next for WoGO

Admittedly, what we have now only scratches the surface of computer science. There are so many more topics to explore, and we’d like to build on the existing topics we have right now. In the future, we hope to add more Python and Java projects, add more advanced tutorials in Excel and CTF, and explore more features in pixlr and Hugo. We also would like to improve the functionality of the website. Adding things like a search bar, an ability to ask and answer questions, or even more technically advanced components provided they serve a purpose. If we could find a way to make machine learning useful to our site, we would. Next time, we will.

This is a beginner hackathon project.

Built With

Share this project:

Updates