Development resources at your finger tips
Build with the coolest Web3 projects
Recurring funding for Open Source
Learn about Web3 & earn rewards
Show appreciation for each other
Meet fellow developers, designers, futurists and more. Collaborate and BUIDL awesome projects together.
Discover great web3 organizations, work on meaningful projects and build relationships with like minded people. Browse Tribes
Meet the top hunters and contributors from our community.
In partnership with Protocol Labs, we’re excited to welcome builders from everywhere to APOLLO, your mission control to engage with the builder…
We’re excited to publically announce that Matic Network is partnering with Gitcoin to launch the Build-n-Earn Program – assisting dApps t…
Gitcoin is GDPR complaint. Learn more in
Gitcoin's Terms & Conditions.
Check out the Issue Explorer
Looking to fund some work? You can submit a new Funded Issue here.
### User Story
[comment]: # (As a , I want to so that .)
As a user I want to have a list of keywords to match with bounties, jobs, users to be able to have better search.
### Why Is this Needed
[comment]: # (Describe the problem and why this task is needed. Provide description of the current state, what you would like to happen, and what actually happen)
Right now how matching works by string, the keywords autocomplete suggestion doesn't look for a database of keywords, just suggest the ones in github.
That make our search/match less effective
Having a dictionary of keywords will avoid duplications, better search by keywords.
[comment]: # (Feature or Bug? i.e Type: Bug)
### Current Behavior
[comment]: # (Describe what actually happened.)
Is just a comma string related with the current bounty not shared with the others bounties or products.
### Expected Behavior
[comment]: # (Describe what you expected to happen.)
Have a search of keywords already in the database when you create a bounty, if doesn't exist in the DB you can add new ones.
### Definition of Done
[comment]: # (Any other information that would be useful, bullets are helpful.)
### Data Requirements
[comment]: # (How will we measure the success of this feature? What kind of tracking is needed for this feature (clicks, impressions, flag)?)
### Additional Information
[comment]: # (Any other information that would be useful, content, screenshots, etc.)