anchor.diff:  +
   [NOTE]
   ====
  -The `{product-name}` and `{product-version}` common attributes are not defined in the `modules/common-attributes.adoc` file. Those attributes are pulled by AsciiBinder from the distro mapping definitions in the https://github.com/openshift/openshift-docs/blob/main/_distro_map.yml[_distro_map.yml] file. See xref:product-name-and-version[Product name and version] for more information on this topic.
  +The `{product-name}` and `{product-version}` common attributes are not defined in the `_attributes/common-attributes.adoc` file. Those attributes are pulled by AsciiBinder from the distro mapping definitions in the https://github.com/openshift/openshift-docs/blob/main/_distro_map.yml[_distro_map.yml] file. See xref:product-name-and-version[Product name and version] and xref:attribute-files[attribute files] for more information on this topic.
   ====
   +
   <5> Context used for identifying headers in modules that is the same as the anchor ID. Example: cli-developer-commands.
  
positive.code: 
  [NOTE]
  ====
  Other common attribute values are defined in the `modules/common-attributes.adoc` file. Where possible, generalize references to those values by using the common attributes. For example, use `{console-redhat-com}` to refer to Red Hat OpenShift Cluster Manager.
  ====
  
  [id="conditional-content"]
  
negative.code: 
  The metadata examples contain sample placement for each file type, xref:assembly-file-metadata[assembly], xref:module-file-metadata[module], and xref:snippet-file-metadata[snippet].
  
  [id="attribute-files"]
  == Attribute files
  
  All attribute files must be placed in the `_attributes` directory. In most cases involving OpenShift Container Platform or OKD, add attributes to the `common-attributes.adoc` file instead of creating or using a separate attributes file. Before you add an attribute, review the contents of the `common-attributes.adoc` file to ensure that it is not already defined.
  
  [IMPORTANT]
  ====
  If you think that you need a separate attributes file, check with the docs team before you create it.
  ====
  
  It is acceptable to group related attributes in the `common-attributes.adoc` file under a comment, as shown in the following example:
  
  ----
  //gitops
  :gitops-title: Red Hat OpenShift GitOps
  :gitops-shortname: GitOps
  ----
  
  It is also acceptable to enclose attributes in a xref:product-name-and-version[distro-based] conditional. The following example shows how to set a different value for the `:op-system-base:` attribute for OKD:
  
  ----
  :op-system-base: RHEL
  ifdef::openshift-origin[]
  :op-system-base: Fedora
  endif::[]
  ----
  
  == Assembly/module file names
  
  Try to shorten the file name as much as possible _without_ abbreviating important terms that may cause confusion. For example, the `managing-authorization-policies.adoc` file name would be appropriate for an assembly titled "Managing Authorization Policies".
  