describe in the share the workload heading

Author: tapaswenipathak

_articles/best-practices.md

@@ -174,6 +174,8 @@ You don't have to do everything yourself. Your project's community exists for a
 
 If you're looking for others to pitch in, start by asking around.
 
+One way to gain new contributors is to explicitly [label issues that are simple enough for beginners to tackle](https://help.github.com/en/articles/helping-new-contributors-find-your-project-with-labels). GitHub will then surface these issues in various places on the platform, increasing their visibility.
+
 When you see new contributors making repeated contributions, recognize their work by offering more responsibility. Document how others can grow into leadership roles if they wish.
 
 Encouraging others to [share ownership of the project](../building-community/#share-ownership-of-your-project) can greatly reduce your own workload, as @lmccart discovered on her project, [p5.js](https://github.com/processing/p5.js).
@@ -194,6 +196,7 @@ If other people are enthusiastic about its direction, give them commit access or
 
 > I wrote a wiki page describing what I wanted and why I wanted it. For some reason it came as a surprise to me that the maintainers started moving the project in that direction! Did it happen exactly how I'd do it? Not always. But it still brought the project closer to what I wrote down.
 
+
 ### Let others build the solutions they need
 
 If a potential contributor has a different opinion on what your project should do, you may want to gently encourage them to work on their own fork.