There are many ways to contribute to the Yearn ecosystem and equally many ways to write this guide. Whether you're a writer, developer, translator, strategist, or a creative; there's room for you!
We invite writers—technical and non-technical—to review Yearn's documentation, browse through open issues in the docs repository, write blog posts, write how-to guides, and serve any other need you see in the community. Here's some places to start:
[ Insert your own blog here ]
If you're a translator, your help is also needed on the resources above! Hop into the #translations channel on Discord to get started.
We invite developers to look for bugs in Yearn's code, create tools, create interfaces, help strategists bring their ideas to life, and fill any gaps you see fit. Here's some resources to get started:
If you build it, they will come. If you fix it, we will owe you.
We invite designers, animators, artists, and more to share your skills with the Yearn ecosystem! If you're interested in creating graphics that describe Yearn's systems, creating video explainers, fixing Yearn's UI/UX, or any other combination of things—hop into the #ui-ux channel or #media-resources channels on Discord!
The Yearn community has quite a few places to find your bearings, make connections, and discover where help is needed most. Don't hesitate to reach out to someone if you're having trouble getting started.