If you’ve followed me for a while, you know that I'm a firm believer that everyone has a place in open source, even if you're not technical or lack knowledge in programming.
Recently, I made no-code contributions to the Mautic project, and in this blog post, I want to share this experience with you.
The Big Picture of Open Source Contributions
Open source projects need all kinds of support. Sure, developers are super important, but there are also plenty of people who pitch in without ever touching any code, and they make a big difference, too.
Think of these roles and their contributions:
Designers: Creating mockups for website designs, improving user experience (UX) flows, and designing promotional graphics.
Testers: Running manual tests of the software and providing feedback on functionality.
Marketers & Communicators: Promoting the project, managing social media accounts, and writing informative blog posts.
Translators: Providing localized language using dedicated translation platforms.
Event Organizers: Planning meetups and contributor sprints.
PR Reviewers & Content Editors: Reviewing incoming PRs, checking grammar, and improving clarity on documentation or blog posts before they are published.
Can you imagine a project without those amazing no-code contributors? They tremendously help a project get recognized, keep things running smoothly, and make everything user-friendly for everyone. Plus, they help bring the whole community together, and that’s what open source is all about—awesome projects with solid community and collaborators!
The good news is that since last year, Hacktoberfest has started to encourage no-code contributions. But there’s still a bit of a problem. The official Hacktoberfest count is based on the total number of merged Pull Requests (PRs). This makes it tough for organizations to give credit for the amazing contributions that happen outside of coding and make sure they count for Hacktoberfest. That's why, although many people have the willingness and skills to contribute in various ways, they tend to focus on finding issues that allow them to create PRs just to get counted for Hacktoberfest.
My First Video Tutorial
I've done some no-code contributions before, but this year I tried something totally new. I created my very first video tutorials for Mautic documentation projects.
These were no-code contributions, and they quickly filled an important gap for our community.
It started during a Hacktoberfest contributor onboarding call at Mautic Community. We didn't have enough time to fully explain one of the essential steps for new contributors, which is to set up a local environment to work with our documentation projects. A few folks were also confused about what a PR actually is and how to create one.
Because of this, we planned to host another live session for these new contributors. The problem was that finding a time that works for everyone has been tough since we're all volunteers juggling different schedules and time zones. Also, if people missed the session or the recording failed, we would have to hold a new session, which would use up more of everyone's time.
That’s when my project manager suggested a great alternative: creating a video tutorial for the local environment setup instead! This way, contributors can check out the video whenever they want. I jumped right in and said I’d make the video.
What people didn't know was that this was a huge challenge for me. 😅
I'm a non-native English speaker and an introvert. Talking in public or in front of a camera is my kryptonite. I'm always anxious about recording my voice and screen. But, as people say, you can only grow when you get out of your comfort zone. Most of all, my top priority is to ensure that the onboarding process is smooth for new contributors. So, I pushed myself.
The Video Making Process
To prepare for Hacktoberfest, I created new contributing guidelines for the repository.
My initial plan was to create a single video: a walkthrough of the contributing guidelines for setting up the local environment. I figured this would be a great way to ensure the guidelines were clear and easy to navigate. If anything seemed unclear during my presentation in the video, I could update the written instructions later. It's also a good reminder for new contributors to read these guidelines before working with the repository, since they have all the info they need. That’s why I didn’t write out a script and just went with the flow.
After about five hours of retakes, editing, and re-recording, I finally finished a complete and clear 11-minute tutorial! It was rewarding to put together a solid, lasting resource for Mautic.
However, since I knew there was also ongoing confusion about creating PRs, I took the initiative to make a second video after finishing the first one. I made another video that walks through the entire process of creating a PR for no-code contributions at Mautic, using my own video tutorial contribution as an example.
The best part of all? These efforts are counted towards Hacktoberfest! 🎉
Mautic's Commitment to Full Inclusion
Since last year, Mautic has taken the initiative to bridge the gap for low- and no-code contributions so they can be recognized alongside code contributions. Mautic believes that all types of contributions should be celebrated and actively supported.
If you're curious about how Mautic recognizes high-value no-code contributions, check out this blog post, "Giving non-code contributions the recognition they deserve".
It explains how Mautic acknowledges these contributions and makes sure they’re counted for Hacktoberfest. It's definitely worth a read if you want to see how your no-code efforts can really make a difference!
Also, feel free to look at Mautic’s low- and no-code project board to find low- and no-code tasks if you’re interested in contributing.
Final Words
My experience proved the value of non-code contributions (again); now it's your turn to experience it too. Every single skill you have is valuable in open source. Now, let’s act on that knowledge.
If you’re a beginner or a non-programmer looking to contribute to open source but lack the confidence, you need to hear this: Open source isn’t just welcoming, it’s actively waiting for you! Find a project you love and ask, "How can my skills in writing, design, testing, or marketing help right now?"
If a project lacks a clear process for accepting no-code contributions, suggest one! Talk to the maintainers. Explain politely that incorporating non-code contributions not only feels nice but also builds a healthier and more diverse community. Feel free to share this post and suggest they check out the Mautic approach as a simple starting point.
Your next contribution is waiting. Together, let's elevate open source in a way code never could.
