You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Create a Textile plugin for a popular developer or designer tool
Prize Bounty
1500 DAI first place.
Challenge Description
Professional tools are abundant, and many have ecosystems with 1000s and sometimes 1,000,000s. A simple way to bootstrap your business, onboard new people to Web3, IPFS, and Filecoin, is to go to where the people work.
We want you to plan and build a plugin or add-on to a professional tool for developers or designers throughout the hackathon. Some example tools include Figma, VSCode, Chromium Dev Tools, Sketch, Hubspot, and Wordpress. Many of those tools have vibrant ecosystems of successful businesses building plugins. In particular, we want your solution to leverage the Textile Hub to help users leverage IPFS or Filecoin in a way that solves a real problem, simplifies a complicated workflow, or delivers measurable value. Ideally, your solution solves something for you!
Submission Requirements
Eligible projects must use the Textile Hub APIs to provide access to IPFS and/or Filecoin via a plugin or add-on to an existing tool. Tools include those listed above and others (ask if unsure about the target tool/platform you wish to develop for). The final add-on doesn't necessarily need to be available in a public marketplace or listing, but a video demo should demonstrate the solution working against the production tool. Relevant portions of your code will also need to be made available.
Judging Criteria
Judges will select the winner based on functionality, design, and potential. We will judge functionality and design based on the submitted demo or video showing the tool in action. We will judge potential based on a written submission that describes the target market, the expected demand for the solution, and any plans for reaching an audience with the tool.
Winner Announcement Date
All submissions must be received no later than 11:59 PM EDT on Oct 15th, 2020, to be considered.
The text was updated successfully, but these errors were encountered:
Create a Textile plugin for a popular developer or designer tool
Prize Bounty
1500 DAI first place.
Challenge Description
Professional tools are abundant, and many have ecosystems with 1000s and sometimes 1,000,000s. A simple way to bootstrap your business, onboard new people to Web3, IPFS, and Filecoin, is to go to where the people work.
We want you to plan and build a plugin or add-on to a professional tool for developers or designers throughout the hackathon. Some example tools include Figma, VSCode, Chromium Dev Tools, Sketch, Hubspot, and Wordpress. Many of those tools have vibrant ecosystems of successful businesses building plugins. In particular, we want your solution to leverage the Textile Hub to help users leverage IPFS or Filecoin in a way that solves a real problem, simplifies a complicated workflow, or delivers measurable value. Ideally, your solution solves something for you!
Submission Requirements
Eligible projects must use the Textile Hub APIs to provide access to IPFS and/or Filecoin via a plugin or add-on to an existing tool. Tools include those listed above and others (ask if unsure about the target tool/platform you wish to develop for). The final add-on doesn't necessarily need to be available in a public marketplace or listing, but a video demo should demonstrate the solution working against the production tool. Relevant portions of your code will also need to be made available.
Judging Criteria
Judges will select the winner based on functionality, design, and potential. We will judge functionality and design based on the submitted demo or video showing the tool in action. We will judge potential based on a written submission that describes the target market, the expected demand for the solution, and any plans for reaching an audience with the tool.
Winner Announcement Date
All submissions must be received no later than 11:59 PM EDT on Oct 15th, 2020, to be considered.
The text was updated successfully, but these errors were encountered: