Content Gate

opencx content gate validates your local content files and compares them against the remote to detect drift. It combines local validation (content check) with a remote diff in a single command.

#Usage

opencx content gate

Requires authentication via OPENCX_API_KEY.

#How It Differs from Check

content check validates file structure, frontmatter, and naming conventions locally. content gate does the same validation, then fetches the remote state and compares it to detect any differences.

#Exit Codes

#JSON Output

Use --json for machine-readable output.

opencx content gate --json

Output schema:

{
  "valid": true,
  "synced": true,
  "check": {
    "valid": true,
    "errors": [],
    "stats": {
      "categories": 3,
      "articles": 12
    }
  },
  "diff": {
    "hasChanges": false
  }
}

When validation fails, synced is false and diff is null:

{
  "valid": false,
  "synced": false,
  "check": {
    "valid": false,
    "errors": [
      { "file": "docs/getting-started/intro.md", "message": "Missing required field: title" }
    ]
  },
  "diff": null
}

#When to Use Gate vs Check

• Use content check during local development for quick feedback.
• Use content gate in CI pipelines to ensure content is both valid and in sync before deploying.
• Use content check in pull request workflows where you only need validation without remote comparison.