├── static ├── cover.png ├── prize-deno-pocket-tee.png ├── prize-deno-kv-floppy-disk.png └── prize-deno-kv-sticker-set.png ├── .github └── ISSUE_TEMPLATE │ └── project-submission.md └── README.md /static/cover.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/denoland/deno-kv-hackathon/main/static/cover.png -------------------------------------------------------------------------------- /static/prize-deno-pocket-tee.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/denoland/deno-kv-hackathon/main/static/prize-deno-pocket-tee.png -------------------------------------------------------------------------------- /static/prize-deno-kv-floppy-disk.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/denoland/deno-kv-hackathon/main/static/prize-deno-kv-floppy-disk.png -------------------------------------------------------------------------------- /static/prize-deno-kv-sticker-set.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/denoland/deno-kv-hackathon/main/static/prize-deno-kv-sticker-set.png -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/project-submission.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Project Submission 3 | about: Your team's hackathon submission details. 4 | title: "[Project or Team Name]" 5 | labels: '' 6 | assignees: '' 7 | 8 | --- 9 | 10 | ## Team or Project Name 11 | ... 12 | 13 | ## Team Members 14 | ... 15 | 16 | ## Screenshots of your Project 17 | ... 18 | 19 | ## Link to demo on Deno Deploy 20 | ... 21 | 22 | ## Link to project's public GitHub repo 23 | ... 24 | 25 | ## Any final comments you'd like to add? -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | ![Deno Hackathon](https://github.com/denoland/deno-kv-hackathon/blob/main/static/cover.png) 2 | 3 | # Deno KV Hackathon 4 | 5 | Welcome to the Deno KV Hackathon! 6 | 7 | For more information, check out the 8 | [announcement blog post](https://deno.com/blog/deno-kv-hackathon). 9 | 10 | The hackathon will run from **Monday, June 12th, 10am PT to Thursday, June 15th, 11 | 12pm PT**. 12 | 13 | [Submit your project here](https://github.com/denoland/deno-kv-hackathon/issues/new?assignees=&labels=&projects=&template=project-submission.md&title=%5BProject+or+Team+Name%5D). 14 | 15 | ## Categories and Prizes 16 | 17 | We'll evaluate projects in these five categories: 18 | 19 | - Overall best 20 | - Ryan's favorite 21 | - Most fun 22 | - Most technically impressive 23 | - Fan favorite (community vote — you get to decide!) 24 | 25 | And all winning teams will receive... 26 | 27 | **Our new Deno KV sticker set:** 28 | 29 | ![Deno KV sticker set](https://github.com/denoland/deno-kv-hackathon/blob/main/static/prize-deno-kv-sticker-set.png) 30 | 31 | **A Deno pocket tee:** 32 | 33 | ![A Deno pocket tee](https://github.com/denoland/deno-kv-hackathon/blob/main/static/prize-deno-pocket-tee.png) 34 | 35 | **A Deno KV floppy disk USB drive (16GB):** 36 | 37 | ![A Deno KV floppy disk](https://github.com/denoland/deno-kv-hackathon/blob/main/static/prize-deno-kv-floppy-disk.png) 38 | 39 | ## Submission Rules 40 | 41 | To be eligible for judging, you must submit your project 42 | [here](https://github.com/denoland/deno-kv-hackathon/issues/new?assignees=&labels=&projects=&template=project-submission.md&title=%5BProject+or+Team+Name%5D) 43 | by Thursday 12pm Pacific Time and adhere to the following rules: 44 | 45 | - Uses [Deno KV](https://deno.com/kv) and deployed on [Deno Deploy](https://deno.com/deploy) 46 | - Open sourced on GitHub 47 | - One submission per team 48 | - Team size can be 1 person to 5 people 49 | - You cannot be on multiple teams 50 | - All code must be created during the event 51 | --------------------------------------------------------------------------------