chore(deps-dev): bump prettier from 3.5.3 to 3.6.0

Author: julien-deramond

package-lock.json

@@ -33,7 +33,7 @@
     "gemoji": "^8.1.0",
     "linkedom": "^0.18.11",
     "parse-github-url": "^1.0.3",
-    "prettier": "^3.5.3",
+    "prettier": "^3.6.0",
     "prettier-plugin-astro": "^0.14.1",
     "reading-time": "^1.5.0",
     "starlight-blog": "^0.24.0",

package.json

@@ -59,11 +59,9 @@ The foundation of a thriving open-source community is an inclusive and welcoming
 Communication is the lifeblood of an open-source community. It is essential to establish clear, accessible, and inclusive communication channels:
 
 1. **Mailing Lists** are a traditional but effective way to communicate with your community. They allow for asynchronous discussions, detailed conversations, and archiving conversations for future reference.
-
    - Create separate lists for different purposes (e.g., development, user support, announcements). Encourage clear, respectful communication and thread management.
 
 2. **Forums and Discussion Boards** provide a structured environment for ongoing discussions, categorized by topics or features.
-
    - Use platforms like [Discourse](https://www.discourse.org/) or [GitHub Discussions](https://docs.github.com/en/discussions). Ensure active moderation to maintain a positive environment and keep discussions on-topic.
 
 3. **Real-Time Communication Tools** like [Slack](https://slack.com), [Discord](https://discord.com/), IRC, or [Mattermost](https://mattermost.com/) enable quick, interactive conversations and foster a sense of community through real-time engagement.
@@ -74,11 +72,9 @@ Communication is the lifeblood of an open-source community. It is essential to e
 Making it easy for new contributors to get started with your project is crucial for community growth. Here are some strategies to streamline the onboarding process:
 
 1. **Creating Comprehensive Documentation** lowers the barrier to entry by providing clear, step-by-step guides for setting up and contributing to the project.
-
    - Include sections like a project overview, installation instructions, contribution guidelines, and FAQs. Use visual aids, such as diagrams and videos, to enhance understanding.
 
 2. **Mentorship Programs** pair newcomers with experienced contributors to accelerate learning and foster a supportive community atmosphere.
-
    - Establish a mentorship program where experienced members volunteer to guide new contributors. Define the scope of mentorship, including code reviews, answering questions, and providing feedback on contributions.
 
 3. **Starter Issues and First-Timer-Friendly Tasks** by labeling issues as "good first issue" helps new contributors find tasks that match their skill level and confidence. Folks will follow guide like our ["Finding Open-Source Projects" chapter](/guide/contributing-to-open-source-projects/finding-open-source-projects) to find projects to contribute to; you can adapt your project to follow what we suggest in that guide but from the maintainer's perspective.
@@ -91,11 +87,9 @@ Making it easy for new contributors to get started with your project is crucial
 Consistent and transparent communication is key to keeping your community informed and engaged. Here are some effective strategies:
 
 1. **Newsletters** provide a regular touchpoint with your community, summarizing recent developments, upcoming events, and important announcements.
-
    - Send out newsletters on a regular schedule (e.g., monthly or quarterly). Include sections like "Recent Highlights" "Contributor Spotlights" and "Upcoming Events"
 
 2. **Blog Posts** offer an in-depth look at new features, project milestones, and insights from the development team.
-
    - Maintain a project blog on platforms like [Medium](https://medium.com/) or your own website. Encourage contributors to write guest posts. Share posts on social media and other communication channels to maximize reach.
 
 3. **Social Media Presence** help you reach a broader audience and engage with your community in real-time.
@@ -106,11 +100,9 @@ Consistent and transparent communication is key to keeping your community inform
 Acknowledging the efforts of your contributors is vital for maintaining motivation and a sense of belonging. Here are some ways to recognize and reward contributions:
 
 1. **Acknowledging Contributions Publicly** boosts morale and shows appreciation for the efforts of your contributors.
-
    - Include contributor acknowledgments in your newsletters, blog posts, and release notes. Highlight significant contributions during community meetings or webinars.
 
 2. **Badges and Certifications** incentivize participation and recognize achievements.
-
    - Create a system of badges for various levels of contribution (e.g., "First Pull Request" "Documentation Hero" "Core Contributor").
 
 3. **Contributor Spotlights** featuring individual contributors in spotlight segments showcases their work and personal stories, fostering a sense of community.
@@ -121,11 +113,9 @@ Acknowledging the efforts of your contributors is vital for maintaining motivati
 Events provide opportunities for real-time interaction, learning, and collaboration. Here are some types of events you can organize:
 
 1. **Meetups and Hackathons** foster collaboration, idea exchange, and hands-on coding experience.
-
    - Organize regular meetups either virtually or in different locations. Host hackathons to tackle specific issues, build new features, or explore innovative ideas. Use platforms like [Meetup](https://www.meetup.com/), [Eventbrite](https://www.eventbrite.com/), or GitHub for organizing and promoting these events.
 
 2. **Webinars and Virtual Events** allow you to share knowledge, discuss updates, and engage with your community regardless of geographical constraints.
-
    - Schedule webinars on topics of interest, such as new releases, technical deep dives, or Q&A sessions with maintainers. Use tools like [Zoom](https://zoom.us/), [YouTube Live](https://www.youtube.com/live), or [Twitch](https://www.twitch.tv/) for hosting. Record and archive these sessions for later viewing.
 
 3. **Conferences and Summits** provide an immersive experience for networking, learning, and collaboration.
@@ -142,13 +132,11 @@ Check out our [Events](/resources/events) page.
 Even in the most well-intentioned communities, conflicts can arise. Handling these conflicts effectively is crucial to maintaining a positive and productive environment.
 
 1. **Identifying Common Conflicts**
-
    - **Technical Disagreements:** Differing opinions on the direction or implementation of features.
    - **Personal Clashes:** Personality conflicts between community members.
    - **Behavioral Issues:** Violations of the code of conduct or disrespectful behavior.
 
 2. **Mediation Techniques**
-
    - **Active Listening:** Ensure all parties feel heard and understood. This can de-escalate tensions and foster mutual respect.
    - **Neutral Moderation:** Involve a neutral third party to mediate the discussion. This person should be respected by all involved and have a track record of fair judgment.
    - **Focus on Solutions:** Encourage a solution-oriented mindset. Frame conflicts as problems to be solved collaboratively rather than battles to be won.
@@ -162,13 +150,11 @@ Even in the most well-intentioned communities, conflicts can arise. Handling the
 A sustainable community is one where members are engaged for the long term, and the project itself remains viable and vibrant.
 
 1. **Handling Burnout**
-
    - **Recognize Signs:** Be aware of burnout signs, such as declining participation, irritability, or disengagement.
    - **Encourage Breaks:** Promote a culture where taking breaks and time off is normalized and encouraged.
    - **Distribute Responsibilities:** Prevent over-reliance on a few individuals by distributing responsibilities across a broader group of contributors.
 
 2. **Encouraging Long-Term Contributions**
-
    - **Clear Pathways for Advancement:** Provide clear pathways for contributors to take on more significant roles, such as becoming maintainers.
    - **Mentorship:** Establish mentorship programs where experienced members support and guide newer members, fostering a sense of progression and investment in the community.
    - **Recognition and Rewards:** Continuously recognize and reward contributions, as discussed in the previous section, to maintain motivation and engagement.
@@ -185,13 +171,11 @@ A sustainable community is one where members are engaged for the long term, and
 To gauge the health and engagement of your open-source community, it's essential to track relevant metrics and Key Performance Indicators (KPIs).
 
 1. **Tracking Contributions**
-
    - **Number of Contributions:** Monitor the volume of code contributions, documentation updates, issue comments, and other forms of engagement.
    - **Diversity of Contributors:** Measure the diversity of contributors in terms of backgrounds, skill levels, and geographical locations to ensure inclusivity.
    - **Code Quality:** Assess code quality metrics such as code coverage, code churn, and the number of bugs reported and fixed.
 
 2. **Measuring Activity Levels**
-
    - **Active Contributors:** Track the number of active contributors over time to identify trends and fluctuations in community participation.
    - **Issue and Pull Request Activity:** Monitor the rate of issue creation, pull request submissions, and review turnaround times to ensure timely responses.
    - **Community Engagement:** Measure engagement on communication channels such as mailing lists, forums, and social media platforms.
@@ -206,13 +190,11 @@ To gauge the health and engagement of your open-source community, it's essential
 Establishing feedback loops allows you to collect input from your community and iterate on your processes and initiatives.
 
 1. **Regularly Collecting Feedback**
-
    - **Surveys and Polls:** Conduct periodic surveys or polls to gather feedback on specific aspects of the project, such as documentation, usability, and community engagement.
    - **User Testing:** Recruit community members to participate in user testing sessions to identify usability issues and areas for improvement.
    - **Open Discussions:** Encourage open discussions and feedback sessions during community meetings, webinars, and conferences to foster dialogue and idea exchange.
 
 2. **Implementing Changes Based on Feedback**
-
    - **Actionable Insights:** Analyze feedback collected from surveys and discussions to identify actionable insights and areas for improvement.
    - **Prioritization:** Prioritize changes and enhancements based on the feedback received, considering both the needs of the community and the project's strategic objectives.
    - **Iterative Approach:** Implement changes incrementally and iteratively, soliciting additional feedback at each stage to validate improvements and address any remaining issues.