Contributing to Codetopia Community is not just about writing code. Whatever your skills, there is a place for you here. This guide walks you through every way you can get involved.
NOTE
All roles in the community are voluntary and unpaid, including department leads. What you gain is experience, mentorship, and a public track record of your work.
What this can look like
Ship code. Write the thing someone will search for at 2am. Hop on a call and help someone go from stuck to shipped. Show up in Discord like you own the place. Plan the event people actually want to be at. Grab a mic and go live. Open doors nobody else could. Ask the questions that make us better. That is the vibe. Some of the ways it actually shows up:
- Build — ship code on one of our open source projects, or help keep the website and our tooling running.
- Write — docs, howtos, technical articles. Whatever helps the next person get unstuck or learn something new.
- Teach and mentor — one-on-one, a study session, breaking something hard down until it finally clicks.
- Show up — facilitate conversations on Discord, welcome the new people, keep the lights on.
- Plan and run events — meetups, workshops, community calls, online or in person.
- Go live — talk shows, panels, AMAs on X Spaces, TikTok Live, YouTube, wherever people already are.
- Build relationships — partnerships, sponsors, connecting Codetopia to other communities.
- Understand us — research, surveys, data. Help the community understand itself.
This is not the full list, just a taste. Departments cover the ongoing paths below, and there is always room for something new.
Who can contribute?
On GitHub: anyone can help. Our repos are public. If you spot a bug, a typo, a broken link, or something that no longer works the way the docs say it does, you can report it or fix it yourself. You do not need to be a member to make something better.
Beyond that, you need to be a member. Joining a department and writing for our blog are for verified members of the community. These need context that only comes from being part of what we are building. Writing new howtos is a little more open — more on that below.
Contributing on GitHub but not a member yet? Join us. You will be able to talk directly with maintainers, have your work recognized inside the community, and unlock every other way to contribute on this page. It takes a few minutes.
Quick contributions
These are things you can do today, no long-term commitment needed.
Fix something on GitHub
Spotted a typo in our docs? A broken link? A bug on the website? You can report it or fix it yourself, even if you have never contributed to a project before. Our guides walk you through it step by step.
Write something
Writing comes in two forms, and you can do either or both. They are different jobs, so here is how to tell them apart.
Howtos are practical guides and walkthroughs for getting things done in Codetopia Community. How to join, how to use Discord, how to contribute to a project, how to submit your work. If a member is stuck on something about how this community works, a howto is what unblocks them. The guide you are reading right now is one. They live in our community-howtos repo.
- Who writes them? Members, mostly. Writing a good howto means knowing what people around here actually get stuck on, and that comes from being part of the community.
- Can anyone fix one? Yes. If you spot a typo, a broken link, or a step that no longer matches what you see on screen, open a pull request. You do not need to be a member to make something better.
- How? Through GitHub, the same way as code.
- What happens next? We review it, and once it is merged it becomes part of this collection.
Technical articles are teaching. They answer "help me understand this" rather than "how do I do this." Tutorials, deep dives, lessons learned, things you figured out the hard way. People read them to learn something, not to unblock themselves in the next five minutes. They are longer, they carry your voice, and they are published on our Hashnode blog under Codetopia Community's name.
- Who writes them? Members of the Blog Writers team.
- How? Create a portal account, then request to join the Blog Writers team. Once you are approved, you can start writing.
- What should I put in my request? Link something you have written before, anywhere. A blog post, an article, a howto, anything that shows how you write.
Still not sure which one you are writing? Ask yourself who is reading it and why. If they are stuck and want it fixed, it is a howto. If they are curious and want to understand, it is an article.
Join a department/team
If you want to contribute in an ongoing way, our departments are where the real work happens. Each one is a team of members who keep a part of the community running.
NOTE
On the portal, departments are called teams. Same thing, two names.
How to join a department/team
Log in to the portal, go to Teams, and click Browse Teams to see the full, current list and pick where you fit. Open the one you want and click Request to Join. A team lead will review your request and get you started.
Not sure which one fits you? Ask in the #general channel on Discord and someone will point you in the right direction.
Not sure where you fit?
That is completely fine. Hang out, join conversations, show up to events. Contribution starts with being present. When you are ready, this page will still be here.