docs: introduce PipeCD community contributor ladder and automated generation (#6548)

docs/content/en/docs-dev/contribution-guidelines/contributor-ladder.md

@@ -0,0 +1,99 @@
+---
+title: "Contributor Ladder"
+linkTitle: "Contributor Ladder"
+weight: 5
+description: >
+  Community contributor tiers, roles, responsibilities, and progression guidelines for PipeCD.
+---
+
+The **PipeCD Contributor Ladder** outlines how community members can engage with the project, advance through contributor tiers, and take on greater responsibility within the PipeCD ecosystem.
+
+Every contribution makes a difference to PipeCD — whether fixing bugs, adding new features, improving documentation, assisting users in Slack, triaging issues, or enhancing test coverage.
+
+> **Note:** PR counts listed for each tier are minimums. Maintainers retain final judgment on tier progression and GitHub organization membership, based on overall contribution quality and community engagement.
+
+---
+
+## Ladder Tiers
+
+| Tier | Merged PRs (minimum) | Description |
+| :--- | :---: | :--- |
+| 🌱 **Newcomer** | 1 | First-time contributors who have had their first pull request merged. |
+| 🛠️ **Contributor** | 2–4 | Community members actively and regularly contributing to the project. |
+| 🚀 **Core Contributor** | 5+ | Established contributors with a sustained track record, eligible to apply for `pipe-cd` GitHub organization membership. |
+
+---
+
+## Role Details & Responsibilities
+
+### 🌱 Newcomer
+
+**Newcomers** are individuals who have taken their first step into contributing to PipeCD by getting their first pull request merged.
+
+- **Requirements:**
+  - 1 merged pull request to any repository under the [`pipe-cd`](https://github.com/pipe-cd) organization.
+  - Agreement to uphold the CNCF and PipeCD [Code of Conduct](https://github.com/pipe-cd/pipecd/blob/master/CODE_OF_CONDUCT.md).
+- **Responsibilities:**
+  - Adhere to the contribution guidelines, [DCO sign-off](https://github.com/pipe-cd/pipecd/blob/master/CONTRIBUTING.md), and PR submission templates.
+- **Recognition:**
+  - Listed on the PipeCD contributors roster as a recognized community member.
+
+---
+
+### 🛠️ Contributor
+
+**Contributors** are community members who demonstrate continued active involvement across the PipeCD codebase, documentation, or tooling.
+
+- **Requirements:**
+  - 2 to 4 merged pull requests to [`pipe-cd/pipecd`](https://github.com/pipe-cd/pipecd) or associated subprojects.
+  - Familiarity with the project's architecture, test suite, and development workflow.
+- **Responsibilities:**
+  - Submit well-tested pull requests that follow project code style and design patterns.
+  - Participate in issue discussions and help clarify bugs or feature requests.
+- **Recognition:**
+  - GitHub issues can be directly assigned to you upon request, so you can officially take ownership of work items.
+  - Peer acknowledgment within the community for sustained contributions.
+
+---
+
+### 🚀 Core Contributor
+
+**Core Contributors** are established community members who have consistently delivered high-impact contributions and demonstrated dedication to the project's health and roadmap.
+
+- **Requirements:**
+  - At least 5 merged pull requests to repositories in the `pipe-cd` organization.
+  - Attended at least one [PipeCD Community Meeting](https://zoom-lfx.platform.linuxfoundation.org/meeting/96831504919?password=2f60b8ec-5896-40c8-aa1d-d551ab339d00).
+  - Demonstrated understanding of PipeCD's core design and contribution workflows.
+- **Responsibilities:**
+  - Author and review substantial features, bug fixes, or architecture documentation.
+  - Help guide and mentor newcomers and contributors in Slack and PR reviews.
+  - Actively participate in project discussions and roadmap planning.
+- **Recognition:**
+  - Eligible to apply for `pipe-cd` GitHub organization membership (see below). Membership is granted at maintainer discretion and is not guaranteed solely based on PR count.
+
+---
+
+## GitHub Organization Membership
+
+Once a contributor reaches the **Core Contributor** tier, they are encouraged to apply for membership in the `pipe-cd` GitHub organization. Membership is helpful if you want to contribute over a long period or take responsibility for a feature.
+
+### Minimum Requirements (per [CONTRIBUTING.md](https://github.com/pipe-cd/pipecd/blob/master/CONTRIBUTING.md#join-our-team-on-github)):
+1. At least **5 merged PRs** in repositories under the `pipe-cd` organization.
+2. Attendance at at least one [PipeCD Community Meeting](https://zoom-lfx.platform.linuxfoundation.org/meeting/96831504919?password=2f60b8ec-5896-40c8-aa1d-d551ab339d00).
+
+> **Note:** These are minimum requirements. Maintainers will use their judgment to evaluate overall engagement, contribution quality, and community participation before granting membership.
+
+### How to Apply:
+- Attend a community meeting and introduce yourself, **or**
+- Reach out in the `#pipecd` channel on [CNCF Slack](https://slack.cncf.io/).
+
+---
+
+## Getting Started
+
+Ready to climb the ladder? Here are great ways to begin:
+
+- Explore beginner-friendly issues labeled [**good first issue**](https://github.com/pipe-cd/pipecd/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22).
+- Read the [Documentation Contribution Guide](../contributing-documentation/) to contribute to our guides and tutorials.
+- Review the [Contributing Guide](../contributing/) for details on local environment setup, testing, and DCO sign-offs.
+- Join the `#pipecd` channel on [CNCF Slack](https://slack.cncf.io/) and introduce yourself!