dify-docs-guides
User Guide Rules
Not an entry point — run under dify-docs-write; this pack's rules and procedures implement its stages for user-guide pages.
Scoping rules (S1)
Match each target page to its reader persona (see Reader Personas below). use-dify pages exist as two product copies — en/cloud/use-dify/ and en/self-host/use-dify/ — with no shared pages and no cross-audience navigation. When the page exists in both, scope both: shared-content improvements land in both copies in the same pass; audience-specific blocks (plan gating, env-var callouts, Enterprise tips) stay per-copy. Exception — work on a release/<version> branch edits only the self-host copy, still in all three languages; what it excludes is the cloud copy, which follows Cloud's own release lane and is re-derived from the self-host diff when Cloud ships that version.
S2 discovery — environment variables
Check for feature-related environment variables. In the Dify codebase, run:
grep -rn "<FEATURE_KEYWORD>" docker/.env.example docker/envs/ api/configs/
Use the feature's name as it would appear in a variable (e.g. COLLABORATION); try 2–3 keyword variants before concluding. No matches → the feature has no env-var surface; skip the env-var guidance below. Matches → record each variable as mandatory or optional plus its default, and queue the dify-docs-env-vars pack's procedure in the S4 scope report, to update en/self-host/deploy/configuration/environments.mdx in the same session — that reference is the single source of truth for variable semantics.