From d298e020619534115d8f071852efa516e91808e6 Mon Sep 17 00:00:00 2001
From: Muhammad Abdullah Shahid
 <108458621+abdollahShahid@users.noreply.github.com>
Date: Mon, 4 May 2026 15:33:40 +0500
Subject: [PATCH] docs: add contribution guides overview

Signed-off-by: Muhammad Abdullah Shahid <108458621+abdollahShahid@users.noreply.github.com>
---
 .../en/docs-v1.0.x/contribution-guidelines/_index.md  | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/docs/content/en/docs-v1.0.x/contribution-guidelines/_index.md b/docs/content/en/docs-v1.0.x/contribution-guidelines/_index.md
index 595f0e2c75..95fe42a583 100755
--- a/docs/content/en/docs-v1.0.x/contribution-guidelines/_index.md
+++ b/docs/content/en/docs-v1.0.x/contribution-guidelines/_index.md
@@ -5,3 +5,14 @@ weight: 6
 description: >
   This guide is for anyone who wants to contribute to the PipeCD project. We are so excited to have you!
 ---
+
+PipeCD has several contribution guides. If you are new to the project, start by choosing the guide that matches the type of change you want to make.
+
+## Choose a contribution path
+
+- [Contribute to PipeCD](contributing-to-pipecd/) for general project contribution guidance, local development setup, pull request expectations, and community links.
+- [Contribute to PipeCD Documentation](contributing-documentation/) for documentation file locations, local preview steps, and the docs pull request process.
+- [Contribute to PipeCD plugins](contributing-plugins/) for plugin contribution guidance and plugin-specific development resources.
+- [Contribute to PipeCD Blogs](contributing-blogs/) for blog front matter, content guidance, and local preview steps.
+
+For a first contribution, keep the change small and focused. If your work relates to a tracked issue, mention it in the pull request description so reviewers have the right context.