Updated: Improved feature_request.yml with guidelines for pinging maintainers

- Added a new section with clear guidelines on when and when not to ping maintainers.
- Improved readability with a structured format for better comprehension.
- Applied minor Markdown adjustments for consistency and clarity.

modified: .github/ISSUE_TEMPLATE/feature_request.yml

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -8,7 +8,9 @@ body:
   - type: markdown
     attributes:
       value: |
-        ## **❗ Important: Temporary Delay in Feature Requests and Pull Request Reviews**
+        ## ❗Important Announcement
+
+        ### 🚧 Temporary Delay in Feature Requests and Pull Request Reviews
 
         **At this time, we may be slower to respond to new feature requests and review pull requests. Existing requests and PRs will remain in the backlog but may not be prioritized immediately.**
 
@@ -20,13 +22,18 @@ body:
 
         [Review Guidelines]: ../REVIEW_GUIDELINES.md
 
-        ## **❗ Important: Please Avoid Unnecessary Pinging of Maintainers**
+        ### 🚫 Please Avoid Unnecessary Pinging of Maintainers
 
         **We kindly ask users to refrain from pinging maintainers unless absolutely necessary. Pings should be reserved for critical issues or urgent matters that require immediate attention.**
 
         - **Why**: To help maintainers focus on high-priority tasks, we kindly request that unnecessary or repeated pings be minimized. This will help ensure quicker responses for matters that truly need attention.
         - **What This Means**: Non-urgent pings may be ignored or addressed later. Please assess the urgency of your request before pinging a maintainer.
 
+        #### Guidelines for Pinging
+
+        - ✅ **Appropriate**: Critical issues or urgent matters requiring immediate attention.
+        - ❌ **Not Appropriate**: Repeated or non-urgent pings, which may be ignored or addressed later.
+
   - type: textarea
     id: related-issues
     validations: