Skip to content

rysolv/hackathon

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

78 Commits
 
 
 
 
 
 
 
 

Repository files navigation

Past

Terrible UI #1: Worst Time/Date Selector

Upcoming

Terrible UI Hackathon #2

When: 5/20/22 @ 6:00PM EST
Challenge: Build the worst Phone Number input

Come join us May 20, 2022 to build the worst UI features you can imagine! Each month we'll select a new UI feature, and compete to make it as terrible as possible.

How to join

The hackathon is hosted on Discord (https://discord.gg/kqt8RcVggN)

  • Join the server
  • Click "Events" and mark yourself as interested

Don't have discord, no problem. Just submit a PR following the #submission instructions before the deadline and you're good to go.

Schedule

The hackathon starts Friday 5/20/22 at 6:00pm. All submissions are due Saturday 5/21/22 6:00pm.

Friday @ 6:00pm

Hop on discord, introduce yourselves, work solo or with a friend.

Next 24 hours

GET HACKING

Saturday @ 6:00pm

Submit your solution for judging.

Saturday @ 8:00pm

Join the live stream on Discord to see the winners.

Submissions

  1. Fork the repo (click the fork button)

  2. Clone down the codebase

  3. Create a new folder (i.e. coolest_project) in the /submissions/terrible_u1_2 directory.

  4. That folder should contain all the code, as well as an about.json. Feel free to copy the ./sample folder to get started.

    🗀 coolest_project
        🗀 assets
        about.json
        index.html
        script.js
        style.css
    
    {
        "name": "sample",
        "description": "Sample solution for terrible_ui hackathon",
        "link": "https://example.com (Optional if hosted)",
        "contributors": [
            {
                "name": "Tyler Maran",
                "github": "https://github.com/tylermaran"
            }
        ]
    }
    
  5. Push up your code

    • push changes to your local fork
      git add .
      git commit -m 'bestest ui ever'
      git pull
      git push
      
    • Create a pull request from your fork. You can follow these instructions.
  6. That's it!

Problems?

Best bet is to ask in the Discord. But feel free to email [email protected] as well.