🎆 Hacktoberfest 2020

[bajtos]

Greetings 👋 to all Hacktoberfest 2020 participants! Let's have some fun hacking and improving the framework together 🥳

You can learn more about our motivations in the announcement blog post.

Focus areas

We are primarily looking for quick wins with long term impact: small enhancements improving your day-to-day experience while using LoopBack.

As you may know, we have introduced a new documentation system in June to better organize the content and make it easier to find the information you need (see New Documentation Structure and Alignment Along Abstraction Levels). The reorganization is still in progress and we would love to get some help. In particular, extracting recipes from "Concepts" explanations into proper "How-to guides" is an easy way how to quickly score valuable pull requests. See the GitHub issue loopback-next#5783 for the list of docs pages to rework.

Having said that, all improvements are welcome!

How to participate

Joining the effort is simple. Just pick any problem that is itching you and send a pull request to fix it. You can also choose one of LoopBack's issues labelled as Hacktoberfest or good first issue if you need inspiration.

Make sure to familiarize yourself with Hacktoberfest's Participation rules and Quality standards; and also LoopBack's Contributing guide.

Are you new to open source? No problem, we have you covered! Check out Hacktoberfest's Beginners guides and LoopBack's guide on submitting a pull request to LoopBack 4.

If you are contributing your first documentation improvement, then read Documentation guide for LoopBack 4 developers please. Consider previewing loopback-next docs only for a faster feedback loop. Finally, please refer to Contributing to LoopBack documentation for a more advanced information on our Jekyll-based documentation infrastructure.

[bajtos]

Big thanks to everyone who participated in this year's Hacktoberfest ❤️