Skip to content

Editorial Policy

How HelmForge publishes technical content.

These standards keep articles useful, verifiable, and honest about operational trade-offs.

Technical review

Articles should be grounded in working Helm, Kubernetes, or project repository behavior. Commands, paths, and configuration examples are reviewed against the current HelmForge codebase when possible.

Source selection

Posts favor primary sources such as upstream documentation, release notes, project repositories, and official specifications. When a claim depends on current behavior, the source should be linked or reproducible.

AI and editorial assistance

Automation and AI tools may assist with drafts, checks, and formatting. Maintainers remain responsible for factual review, final wording, and publication decisions.

Corrections

Material errors are corrected when discovered. Meaningful updates should preserve or add visible updated dates so readers can understand when guidance changed.

Update policy

Dates are not changed for cosmetic edits. Updated dates are reserved for meaningful technical changes, migration guidance, corrected behavior, or refreshed references.