Community guides
Scope and review expectations for user-contributed documentation.
Community documentation should be reproducible, platform-specific where necessary, and aligned with the current Core ownership boundaries. State the target repository, platform, required permissions, and version assumptions. Prefer linking to Core or script source for unstable implementation details instead of copying large function lists into a guide.
Do not present local fork URLs, credentials, unreviewed shell snippets, or a Proxmox-only command as universal guidance. Include verification and recovery steps for destructive operations, and identify whether a problem belongs to the application script, Core backend, or the upstream host platform.
Open documentation changes in the repository that owns the information: Core for shared engine behaviour, Incus for Incus-specific host material, and the relevant script repository for application documentation.