diff --git a/platform/.eslintrc.json b/.eslintrc.json similarity index 100% rename from platform/.eslintrc.json rename to .eslintrc.json diff --git a/DEPLOY23/DEPLOY23 Debrief and Notes for DEPLOY24.md b/DEPLOY23/DEPLOY23 Debrief and Notes for DEPLOY24.md deleted file mode 100644 index 5ae1c72..0000000 --- a/DEPLOY23/DEPLOY23 Debrief and Notes for DEPLOY24.md +++ /dev/null @@ -1,34 +0,0 @@ -# DEPLOY/23 Debrief & Notes for DEPLOY/24 - -## Platform - -- entirely custom DB (nothing in Notion) that accounts for registration & inviting to a team. essentially everything is automated and we just audit if/when necessary - -## Event - -- dinner at opening night was nice but food at presentations would be a huge plus. even just refreshments would be good -- have Redbull lol - -## Presentations / Workflow - -- Make it clearer to participants the presentation workflow, order of team presentations, etc. -- Be stricter on time limits - - Maybe a timer on the podium to help teams time themselves -- Make the time blocks for presenting → judges ask questions → audience asks questions clearer (e.g. 5 mins, 2 mins, 2 mins) -- Streamline the presentation handoff (walkout music) -- Use only one laptop for presentations - - Teams can either record their demos or if available live, we can pull it up on our end - -## Promotion - -- massive promo campaign - - particularly with design & engineering -- several promo bits encouraging ppl with minimal experience to attend — that's the whole point, to *get* experience -- double down on staging as an opportunity to build skills for the hackathon -- one-month extended hackathons but more like just demos & snacks (build night on steroids) - -### Judging - -- external factors — like referrals or event attendance — should not impact score. use solely judge evals OR make the point formula known (for example that # of majors are considered if we do that) -- still have some sort of incentive for referrals, as well as early registration (which is much more attainable for everyone than referrals anyway) -- less weight on presentation, more on quality of project diff --git a/DEPLOY23/README.md b/DEPLOY23/README.md deleted file mode 100644 index 6f9f35e..0000000 --- a/DEPLOY23/README.md +++ /dev/null @@ -1,36 +0,0 @@ -[![DEPLOY/23 Banner](https://raw.githubusercontent.com/compsigh/deploy/main/platform/public/banner-grid.png)](https://deploy.compsigh.so) - -# DEPLOY/23 - -Welcome to the repo for the landing page & platform for DEPLOY/23 — [compsigh](https://compsigh.so)'s first hackathon, and our biggest event of the semester. An interdisciplinary three-day event running from Friday November 17th – Sunday November 19th, bringing together the best minds in CS, design, and engineering to hack on a project for a weekend. - -One of our club's values is [Learning/Building in Public](https://www.swyx.io/learn-in-public), so in that spirit this repo is publicly available. Hopefully it can serve as inspiration for people in making their own hackathons a unique experience! 💛 - -## Stack - -- [React](https://react.dev) -- [Next.js](https://nextjs.org) -- [NextAuth.js](https://github.com/nextauthjs/next-auth) -- [Tally](https://tally.so) -- [Notion API](https://developers.notion.com) - -## Technical Breakdown - -### Registration - -The participant registration form is courtesy of Tally, a Notion-like form builder. The form is embedded in the page using an `