mirror of
https://github.com/web3privacy/docs
synced 2024-10-15 18:46:26 +02:00
Create hackathon-use-cases-generator.md
This commit is contained in:
parent
bff8e9fda5
commit
531bbad426
1 changed files with 57 additions and 0 deletions
57
src/content/docs/projects/hackathon-use-cases-generator.md
Normal file
57
src/content/docs/projects/hackathon-use-cases-generator.md
Normal file
|
@ -0,0 +1,57 @@
|
||||||
|
---
|
||||||
|
title: Hackathon use-cases generator
|
||||||
|
---
|
||||||
|
|
||||||
|
**Problem**: usually hackers don't know what to build or develop not applicable to life solutions. Leading to poor post-hackathon product, project liveliness ratio.
|
||||||
|
|
||||||
|
**Solution**: create a tool helping hackers generate use-cases around privacy. Powered by real product necessity & hundreds of previously created demos.
|
||||||
|
|
||||||
|
1 click away from the privacy use-case.
|
||||||
|
|
||||||
|
**Project components**:
|
||||||
|
- use cases DB with Git repos: hundreds of hackathon projects around privacy built through the years
|
||||||
|
- Expert recommendations: up to date key privacy protocols & teams product nevessity
|
||||||
|
- Generator mechanism based on filters from specific chains, domains to complexity
|
||||||
|
- community recommended use-cases in the future versions
|
||||||
|
|
||||||
|
**Bonus**:
|
||||||
|
- generator will help not just hackers, but grant managers & researchers
|
||||||
|
- match use-cases with funding
|
||||||
|
- empower devrel efficiency
|
||||||
|
- bring a second life to unsupported code base
|
||||||
|
- increase both diversity & efficiency of the new privacy demos
|
||||||
|
- faster convert non-privacy devs into the market
|
||||||
|
- standard format for use-cases x privacy (snapshot)
|
||||||
|
|
||||||
|
**User flow (future)**
|
||||||
|
- dev launches the website
|
||||||
|
- choose filters (chain, domain, lang...) or go random
|
||||||
|
- site generates use-cases with useful links (hackathons, git repos)
|
||||||
|
- dev do DYOR & build use-case
|
||||||
|
|
||||||
|
_Team needed_
|
||||||
|
- curator facilitating the project
|
||||||
|
- researcher collecting hackathon use-cases & demos - filling the DB
|
||||||
|
- researcher applying the first simple filters (chain, domain) + how use-case will look after search
|
||||||
|
- front-end prototyping MVP
|
||||||
|
|
||||||
|
Hackathon demos repo: https://github.com/web3privacy/web3privacy/blob/main/Market%20overview/Ethereum%20Ecosystem/Hackathon%20projects.md
|
||||||
|
|
||||||
|
_Propose as an idea_
|
||||||
|
|
||||||
|
1. Think how to make MVP for privacy use-case generator
|
||||||
|
2. That could use yaml + machine readable data
|
||||||
|
|
||||||
|
a) Explorer examples:
|
||||||
|
- data repo https://github.com/web3privacy/explorer-data
|
||||||
|
- project https://github.com/web3privacy/explorer-data/tree/main/src/projects
|
||||||
|
|
||||||
|
b) Jobs SQL example: http://jobs.web3privacy.info
|
||||||
|
|
||||||
|
3. Basic MVP will be
|
||||||
|
|
||||||
|
|
||||||
|
a) simple filter like: category (gaming, wallet, auth, dao...) + ecosystem (Ethereum, Secret Network etc)
|
||||||
|
b) filtered out use-case snapshot (super simple for MVP: name, description, category, github icon+link, web icon + link)
|
||||||
|
|
||||||
|
_Some inspiration can be found here_: http://explorer.web3privacy.info
|
Loading…
Reference in a new issue