Verify documentation
First off there’s a lot of documentation, and it’s not always easy to keep it updated or know if we covered all the details you need to know to follow them. We would love your help to verify the documentation. That is, to follow the docs to the letter and see if you’re successful or missing anything.
If you find some of the documentation lacking then we reward 2 actions: a report of where you got stuck, or, even better, a pull request to help everyone get “unstuck” (also see the section around “low-code / no-code contributions later on in this blog post).
Find detailed instructions on how to contribute to the docs directly in the documentation site. Here, we have outlined the steps involved with testing and checking the articles against our style guide. In the same article, you can also learn much more about the rules we’re checking the docs against.
Tip: The best way to start helping with identifying where “rules are broken”, we recommend that you install a tool called Vale on your local machine and use that along with an extension to Visual Studio code to run checks on a fork of the UmbracoDocs repository.
Tip tip: your PR will definitely get prioritized when it's changing less than about 5 files at a time, which makes it nice and easy to scan and merge the changes. So we recommend working in small chunks, also to give everyone the opportunity to dive in. It’s no fun if just one person corrects all of the Vale errors in one go, sharing is caring. 💙
Packages
For the third year in a row, packages are back on the menu - and yes, they also count as a contribution to Umbraco!
Here are some specific details on this:
- Only contributions made to open-source Umbraco packages added to the Hacktoberfest Package repo list counts
- Follow the contribution guidelines provided by the package creator
- Look for the “help wanted” label on the issue tracker associated with the package you want to help out with
- Read much more about how this works, and guidelines on adding your own package repo to the list on the Umbraco Packages Hacktoberfest homepage.
Please note: Package contributions eligibility for swag differ slightly from those used for all contributions. Read more on the Packages Hacktoberfest guidelines to learn more about how a contribution is marked as “swag-eligible”.
Creating a brand-new package
Publishing a brand new package to the Umbraco Marketplace will also count towards both DigitalOcean’s and Umbraco’s Hacktoberfest contributions ⭐🤩
Packages for Umbraco 14, also known as Bellissima, are eligible by default, even if the equivalent package already exists for Umbraco 12.
Check out Lee Kelleher’s list of potential new package ideas!
Low-code / no-code contributions
Back, by popular demand, we will also be rewarding contributions that are either low-code and more importantly: no-code!
Eligible contributions according to the Hacktoberfest guidelines include:
- Verifying documentation
- Copy editing
- User experience testing
- Talks or presentations
- Blog posts
- Podcasts
- Case studies
- Organizing Hacktoberfest events
We have set up a special GitHub repository for you to record your contributions that are NOT a pull request.
In order to record your journey of verifying documentation (i.e. related blog post(s) in October, events organized), please edit the README.md file and add your activity at the end in the recommended format and submit that as a pull request. We’ll take it from there!
New! Sponsor an Umbraco-related GitHub repository
To appreciate people who maintain open-source projects for the Umbraco ecosystem, an easy way to help contribute is to give them some money! We’d suggest you have a look at your favorite packages and see if their repo/maintainer is accepting sponsorship.
We suggest you scroll through the list of topics on GitHub, filtered by Umbraco, and see if your favorite packages/authors are open to sponsorship. Look for the heart icon.