> For the complete documentation index, see [llms.txt](https://wiki.superteam.com.br/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.superteam.com.br/en/resources/non-developer-contributors.md).

# Non-Developer Contributors

You do not need to write code to contribute to the Solana ecosystem -- or to earn from it. Superteam Brazil explicitly welcomes designers, content creators, marketers, community managers, and capital allocators (see [Membership](/en/about/membership.md)), and the community's own earning platform lists design, content, and business bounties right alongside development work. This page collects the resources that matter for non-technical contributors: where paid work lives, the official design assets, how content gets distributed, how to join a hackathon team without shipping code, and the community roles that lead to membership.

***

## Earning Opportunities

### Superteam Earn -- Content, Design & Business Bounties

<https://superteam.fun/earn/s/superteambr>

The Superteam Brazil Earn page is the same platform developers use for bounties, but it is filterable by category -- Content, Design, and Dev each have their own tab. Ecosystem teams post paid work like writing threads and articles, producing videos, designing visual identities and decks, and business development tasks, and the platform handles payment, escrow, and dispute resolution.

This is the most reliable entry point for a non-developer: completing visible, paid work is exactly the kind of contribution that [Membership](/en/about/membership.md) describes as the path to an official member invite. Start with smaller bounties to build a track record before applying to larger project engagements.

***

## Design

### Solana Brand Assets & Media Kit

<https://solana.com/branding>

The official Solana brand page: logotype, logomark, and wordmark in PNG and SVG, the brand colors (Solana purple `#9945FF` and green `#14F195`), usage guidelines (clearspace, what not to do with the logo), a downloadable folder with all marketing assets, and the full Solana Foundation brand guidelines.

If you design anything Solana-adjacent -- event banners, pitch decks, dApp landing pages, social graphics for a bounty -- start here. Ecosystem teams and hackathon judges notice when brand usage is correct, and design bounties on Earn frequently require official assets rather than recreations.

***

## Content Creation

Content is one of the most consistently sponsored non-dev skills in the ecosystem. The formats that ecosystem teams pay for through Earn bounties are concrete and repeatable: explainer threads on X, video tutorials and walkthroughs, event recaps, and translations -- Portuguese-language Solana content is scarce relative to demand, which is an advantage for Brazilian creators.

### Superteam Brazil YouTube

<https://www.youtube.com/@SuperteamBrazil>

Superteam Brazil's YouTube channel is where community workshops, bootcamp sessions, and live events are published. For creators, it works in two directions: it is a reference library for the kind of content the community produces, and it is a distribution channel -- creators who collaborate with the community on tutorials or event coverage reach an existing audience instead of starting from zero. Pair it with [@SuperteamBR on X](https://x.com/SuperteamBR), which amplifies builder and creator work in Portuguese and English.

***

## Hackathons Without Writing Code

Hackathon teams need more than engineers. The [hackathon FAQ](/en/hackathon/faq.md) is direct about this: solo submissions are allowed, but diverse teams -- devs plus marketers, designers, and product people -- are recommended, and winners average 3+ members. Look at what judges actually score in [Tips for Generating Good Ideas](/en/hackathon/tips-and-ideas.md): business viability, founder-market fit, and presentation quality are three of the four criteria, and none of them are code.

As a non-technical team member, you own the parts that decide close calls: the pitch deck, the demo video, the go-to-market narrative, and user research that proves founder-market fit. Team formation happens in the [Superteam Brazil Discord](https://discord.gg/superteambrasil) -- introduce yourself with the skills you bring and what you have shipped (even non-crypto work counts).

***

## Community Roles

Beyond bounties and hackathons, there are ongoing roles that the community depends on -- and they are the contribution path [Membership](/en/about/membership.md) describes: contribute, get recognized, get invited.

* **Event organizing** -- Superteam Brazil runs a steady calendar of meetups, bootcamps, and conference activations across Brazilian cities (see [luma.com/superteambrasil](https://luma.com/superteambrasil)). Local organizers who can handle logistics, partnerships, and promotion are always needed.
* **Translation** -- this wiki itself is trilingual (English, Portuguese, Spanish), and keeping documentation, guides, and announcements synchronized across languages is recurring, visible work.
* **Community moderation** -- the [Discord](https://discord.gg/superteambrasil) has channels organized by topic (development, design, content, business); moderators and channel leads keep discussions useful and help newcomers find their footing.

***

## Related Pages

* [Community & Hackathons](/en/resources/community-and-hackathons.md) -- all community channels, events, and earning platforms in detail
* [Membership](/en/about/membership.md) -- the full path from contributor to member
* [Hackathon section](/en/hackathon/hackathon.md) -- the complete hackathon guide, including the Brazil local track


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://wiki.superteam.com.br/en/resources/non-developer-contributors.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
