PipeCD

Over time, the plugin-arch pipecd (https://pipecd.dev/blog/2024/11/28/overview-of-the-plan-for-pluginnable-pipecd/) (some docs we call pipecdv1) has reached the final stages before release. Although most of the features of v0 are retained when moving to v1, some of the documentation and usage need to be updated to match v1. Expected Outcome: 1. Refine pipecd documentation, ensure v0 and v1 coexist in parallel without causing confusion 2. Prepare documentation for pipecd v1 3. Support prepare developer guideline for making pipecd plugins (https://github.com/pipe-cd/community-plugins/)

<p>PipeCD v1 introduced a plugin-based architecture enabling deployments on any platform. While the technical capabilities have evolved significantly, resources for building plugins are currently only available in Japanese. This project focuses on translating and expanding the existing [PipeCD Plugin Development Book](<a href="https://zenn.dev/warashi/books/try-and-learn-pipecd-plugin" rel="noopener noreferrer" target="_blank">https://zenn.dev/warashi/books/try-and-learn-pipecd-plugin</a>) into English and hosting it within PipeCD's docs, making plugin development accessible to the global contributor community.</p><p><br></p><p>As part of the project, [examples of pipedv1 will also be created](<a href="https://github.com/pipe-cd/pipecd/issues/6266" rel="noopener noreferrer" target="_blank">https://github.com/pipe-cd/pipecd/issues/6266</a>) practical, real-world deployment patterns built around PipeCD's new plugin architecture to help adopters get started.</p><p><br></p><p>Alongside this, the mentee will improve documentation experience for contributors and adopters, produce technical content (blogs, articles and walkthrough videos) tied to the book chapters, and grow community awareness through talks and outreach.</p><p><br></p><p>Expected Outcome: </p><p><br></p><p>English Plugin Development Book published within PipeCD docs, v1 examples completed, improved contributor and adopter onboarding experience, better docs usability and content discoverability, walkthrough videos (2–4) and blog posts tied to book chapters, and measurable community and social media growth.</p>

In the latest evolution of PipeCD, the plugin architecture for piped has been established (ref: PipeCD plugin-arch blog)(https://pipecd.dev/blog/2024/11/28/overview-of-the-plan-for-pluginnable-pipecd/) , paving the way for community-developed plugins. Previously, PipeCD already supported deploying applications using Terraform, with the Terraform plugin being developed by the maintainer team to ensure continued support for existing users. Meanwhile, OpenTofu has emerged within the Cloud Native landscape as a drop-in alternative to Terraform. To align with this development, we aim to extend PipeCD’s support to enable the deployment of OpenTofu applications, just as we have done for Terraform. Expected Outcome: 1. OpenTofu plugin for PipeCD 2. Possible update plugin SDK while develop the OpenTofu plugin 3. Possible update docs how to develop PipeCD plugin 4. Blog about how to develop a PipeCD plugin on https://pipecd.dev/blog/

The release of PipeCD v1 introduced a plugin-based architecture that enables deployments on any platform. This is a significant evolution in the project's capabilities, but community awareness and adoption haven't kept pace with the technical progress. This project focuses on growing PipeCD's community through consistent content creation across developer platforms, producing technical content around the v1 release, improving documentation for users and contributors, and engaging with the community through demos and discussions. The mentee will work closely with maintainers to translate PipeCD's technical strengths into accessible content that drives adoption and contributions. - Expected Outcome: Established social media presence for PipeCD across key developer platforms, along with technical content covering v1 features, plugin development, and real-world deployment patterns. Demo content including video walkthroughs and livestreams that make the project easier to adopt. Improved contributor documentation and onboarding materials, with active community engagement through GitHub Discussions and other channels. At least one CNCF talk or meetup presentation delivered.

PipeCD v1 - the new version based on a plugin architecture (ref: [PipeCD plugin-arch overview blog](https://pipecd.dev/blog/2024/11/28/overview-of-the-plan-for-pluginnable-pipecd/)), has released an alpha version, and we are rapidly adding features supported in v0. With a better architecture, support for multi-cluster Kubernetes deployments is a natural extension. This project will focus on developing the Piped v1 plugin to support multi-cluster Kubernetes deployments. - Expected Outcome: - Multi-cluster Kubernetes plugin for PipeCD - Possible update plugin SDK while develop the plugin - Possible update docs how to develop PipeCD plugin - Blog about how to develop a PipeCD plugin on [https://pipecd.dev/blog/](https://pipecd.dev/blog/)