From 33e61c9b5fd38b6b598295faff2bdc5c8eb5a60b Mon Sep 17 00:00:00 2001
From: RuchaYeole <160214265+RuchaYeole@users.noreply.github.com>
Date: Fri, 16 Jan 2026 18:26:41 +0530
Subject: [PATCH] Update best-practices.md

Added a short beginner-friendly explanation to help new contributors
understand the responsibilities of open source maintainers.
---
 _articles/best-practices.md | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/_articles/best-practices.md b/_articles/best-practices.md
index aac362fa281..967000bf9ee 100644
--- a/_articles/best-practices.md
+++ b/_articles/best-practices.md
@@ -15,6 +15,13 @@ related:
 If you maintain an open source project that a lot of people use, you may have noticed you're coding less and responding to issues more.
 
 In the early stages of a project, you're experimenting with new ideas and making decisions based on what you want. As your project increases in popularity, you'll find yourself working with your users and contributors more.
+> **Note for beginners:**  
+> A maintainer is not just someone who writes code.  
+> Maintainers also review issues, respond to contributors, manage releases,
+> and make decisions about the direction of the project.
+>
+> As a project grows, these responsibilities often take more time than coding itself.
+
 
 Maintaining a project requires more than code. These tasks are often unexpected, but they're just as important to a growing project. We've gathered a few ways to make your life easier, from documenting processes to leveraging your community.