I wrote and merged PipeCD’s plugin contribution guide to make plugin development approachable for new contributors.
The guide explains how plugins fit into PipeCD core, the lifecycle/contracts contributors need to follow, and practical setup/testing patterns for building plugins safely.
I also aligned this with the broader docs structure updates in docs-dev and docs-v1.0.x so plugin docs match the rest of the contribution path.
This work came from issue #6124 and shipped after maintainer review rounds.
Links: PR #6398 • Issue #6124