I created the blog contribution guide for PipeCD so community members have a clear path to propose and publish technical posts.
The guide covers what kind of content is expected, the frontmatter and format rules, and how submission and review work.
I also made the docs structure match across docs-dev and docs-v1.0.x, including a section rename to keep the contribution docs consistent.
This was part of the wider contributor-docs effort in issue #6124, and it merged after maintainer review.
Links: PR #6396 • Issue #6124