I created the blog contribution guide for PipeCD so community members have a clear path to propose and publish technical posts.
This work covered content expectations, frontmatter/format rules, and the submission/review flow.
I also aligned the docs structure across docs-dev and docs-v1.0.x, including the section rename to keep contribution docs consistent.
Part of the broader contributor-docs effort in issue #6124, and merged after maintainer review.
Links: PR #6396 • Issue #6124