Development resources at your finger tips
Build with the coolest Web3 projects
Recurring funding for Open Source
Ethical ads to power 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.
KERNEL is an 8-week, invite-only program for top tech talent looking to build relationships, products, and companies in blockchain and Web 3. 100 tal…
Heyo Gitcoiners! With an entire city of hackers, coders and blockchain innovators relocated on our platform, the atmosphere is just buzzing with crea…
Type in [[ 2- term.length]] more characters to get results
[[ result.title ]]
[[ result.description | truncate(70) ]]
No matches found
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.
As described in #20, we are currently facing a couple issues regarding our UI kit. In short, we have two major issues:
* Our current setup is a CRA app that takes forever to load, when one wants to use/develop a component for our application.
* We have no easy way to fetch individual components, so even though we can install our UI kit, one can't easily fetch one specific component like most UI libraries can do.
In the past, we had been using bitsrc.io, but has been quite challenging for local development. We'll favor NPM for the time being, so the solution should natively assume NPM deployment.
1. Split the code for showcasing a specific component and our entire gallery. The gallery can still be a CRA application and might not need modification, but we need to setup an easy "view component" setup so someone can see only one component if so wishes. You can inspire yourself in the [Aragon UI](https://ui.aragon.org/), [x0 compositor](https://github.com/c8r/x0), [Neutrino components](https://neutrinojs.org/packages/react-components/), [Storybook](https://storybook.js.org/) or similar. Pick a light-weight library that doesn't take forever to load and can easily allow development of a component.
2. Setup the required scripts for deploying the library and add the documentation required for showcasing how the library can be:
- Installed, used and reused in many react applications
- Improved, added and redeployed.
## Expected Deliverables
1. A gallery with all the current existing components.
2. A component viewer where one can view a specific component.
3. A project setup (through lerna, builder) that allows quickly versioning per component, and the capabilities to upgrade a component as required.
4. Documentation and demos on how to use our existing components through npm and easily integrate it in any React project.
## To Submit:
1. Pull Request with changes to our gallery and components setup.
2. Any necessary refactor for our components to work easily and be integrated into any react project.
3. Documentation with tests, demos and examples for a project easily using a component, and instructions on how to add a new one to our kit.
## Additional Information:
This is a bit of a lengthy task that requires modifying the setup of an existing project. Make sure to pick the adequate technology or setup in order to move forward as the idea is anyone can:
- Preview our gallery in an easy way, with its current design
- Preview a component in an easy way, with its current design
- Develop a component in an easy way, with a better setup than we have
- Integrate a component in an easy way, with a better setup than we have
## Additional Notes
If you have any questions, please feel free to ask in the thread or ping us at our Gitter channel - https://gitter.im/Mybit-Foundation/DDF
All work completed via the MyBit Decentralised Development Fund is property of the MyBit Foundation (CHE-177.186.963) and may be used, re-used, and/or distributed, re-distributed by the MyBit Foundation for financial gain. The contributor holds no warrant nor claims for any future payments resulting from monetisation schemes originating from the MyBit Foundation or any of its affiliates. Where law permits outside of open source regulations, the contributor is not permitted to distribute any work completed via the MyBit Decentralised Development Fund (DDF) for personal gain.