Editorial Policy
Engineers rely on our guides to configure real systems, so accuracy comes before everything else. This policy describes how we create, review and maintain content.
1. Sources
Technical statements are based on primary sources: the official Argo Workflows documentation, release notes and upgrading guides, the project’s source code and examples, and the Kubernetes documentation. When we describe other tools — such as Apache Airflow or Tekton — we rely on their official documentation. We do not present community opinion as fact.
2. Working examples
YAML and command examples are written to run on a standard installation with public images. Before publication, examples are checked for syntax and structure, and the editorial process includes running them against a recent Argo Workflows release. Where behaviour differs between versions, we say so explicitly.
3. Version awareness
Argo Workflows evolves quickly. Each guide states the release line it targets and highlights changes such as fields removed in version 4.0. When a new release changes recommended practice, we update affected guides and their “Updated” date.
4. Independence and neutrality
We are not affiliated with the Argo Project or any vendor. Comparisons describe each tool on its own terms, explain trade-offs and avoid declaring universal winners. We do not accept payment to change technical conclusions.
5. Review and updates
- Every guide is reviewed for technical accuracy and clarity before publication.
- Guides are re-checked periodically and after major Argo Workflows releases.
- Tool rules — such as validator and checker checks — are updated when the specification changes.
6. Corrections
If you find an error, please contact us with the page and section. We investigate every report, correct confirmed errors promptly and update the page date for material changes.
7. Use of automation
We may use software tools, including AI-assisted drafting and editing, during content production. All published material is reviewed by a human editor for accuracy, and the editorial team is responsible for everything we publish.