z0 - zerops.yaml vs import.yaml, Zerops CA

[tikinang]

What Type of Change is this?

• New Page
• Minor Fix
• Minor Improvements
• Major Improvement

Description (required)

• Clarify zerops.yaml vs Import YAML distinction — added a new YamlConfigsNote Admonition component explaining the two YAML files serve different roles (zerops.yaml = application
  deployment, Import YAML = Infrastructure-as-Code manifest). Embedded it on the import reference, zcli commands, and pipeline pages.
• Rename "Import file" → "Import YAML" consistently across homepage, pipeline, and zcli docs, and tighten descriptions.
• Document JSON Schema editor support — added new sections to both references/import.mdx and zerops-yaml/specification.mdx covering the published JSON Schemas, SchemaStore auto-detection
  (file-name patterns), supported editors (VS Code, JetBrains, yaml-language-server), and manual modeline attachment.
• Fix core mind-map SVGs: SQlite -> VictoriaLogs
• Minor: fix http:// → https:// LinkedIn link in README.
• Adds a Zerops CA reference page documenting how to download (https://app.zerops.io/ca) and trust the CA when connecting to Zerops-signed TLS endpoints from outside, plus the in-container
  path /etc/zerops-zembed/ca.crt and confirmation that the CA is pre-trusted in every Zerops container.
• Cross-links the new page from PostgreSQL connect.mdx (pgBouncer 6432) and Valkey overview.mdx (TLS 6380/7001), and adds a sidebar entry under Networking.