Comply with DITA - Mng content (#4520)

Author: Lennonka

guides/common/assembly_content-access-control-for-hosts.adoc

@@ -0,0 +1,9 @@
+:_mod-docs-content-type: ASSEMBLY
+
+include::modules/con_content-access-control-for-hosts.adoc[]
+
+include::modules/con_content-access-strategies.adoc[leveloffset=+1]
+
+include::modules/con_conditions-for-content-availability.adoc[leveloffset=+1]
+
+include::modules/con_activation-keys-and-content-access.adoc[leveloffset=+1]

guides/common/assembly_restricting-hosts-access-to-content.adoc

@@ -0,0 +1,19 @@
+:_mod-docs-content-type: CONCEPT
+
+[id="activation-keys-and-content-access"]
+= Activation keys and content access
+
+[role="_abstract"]
+Activation keys simplify the workflow for some of the content access strategies.
+
+You can use activation keys to perform the following actions:
+
+* Assign hosts to content view environments.
+* Add content overrides to hosts.
+* Set system purpose attributes on hosts, including a release version.
+
+Activation keys only affect hosts during registration.
+If a host is already registered, you can change the content access individually for each host or through content host bulk actions.
+
+.Additional resources
+* xref:Managing_Activation_Keys_{context}[]

guides/common/modules/con_activation-keys-and-content-access.adoc

@@ -0,0 +1,21 @@
+:_mod-docs-content-type: CONCEPT
+
+[id="conditions-for-content-availability"]
+= Conditions for content availability
+
+[role="_abstract"]
+A host can access a package or repository only when all of the following conditions are true.
+
+* The repository is included in the content view environments of the host.
+* The content view of the host has been published after the repository was added to it.
+* The repository has not been filtered out by a content view filter.
+* The repository is enabled by default or overridden to *Enabled* by using a content override.
+* The repository has no architecture or operating system version restrictions or it has architecture or operating system version restrictions that match the host.
+ifndef::orcharhino[]
+* For certain Red{nbsp}Hat repositories either no release version is set or the release version matches that of the host.
+endif::[]
+ifdef::orcharhino[]
+ifdef::red_hat_enterprise_linux[]
+* For certain Red{nbsp}Hat repositories either no release version is set or the release version matches that of the host.
+endif::[]
+endif::[]

guides/common/modules/con_conditions-for-content-availability.adoc

@@ -0,0 +1,9 @@
+:_mod-docs-content-type: CONCEPT
+
+[id="content-access-control-for-hosts"]
+= Content access control for {Project} hosts
+
+[role="_abstract"]
+{Project} provides a robust set of strategies for controlling what content is accessible to your hosts.
+You can restrict content access by using core mechanisms, such as content views, lifecycle environments, and content overrides.
+You can use activation keys to apply these content access controls during host registration.

guides/common/modules/con_content-access-control-for-hosts.adoc

@@ -1,11 +1,12 @@
 :_mod-docs-content-type: CONCEPT
 
-[id="Restricting_Hosts_Access_to_Content_{context}"]
-= Restricting hosts' access to content
+[id="content-access-strategies"]
+= Content access strategies
 
-{Project} offers multiple options for restricting host access to content.
+[role="_abstract"]
 To give hosts access to a specific subset of the content managed by {Project}, you can use the following strategies.
-{Team} recommends to consider implementing the strategies in the order listed here:
+
+{Team} recommends considering implementing the strategies in the order as listed here:
 
 Content views and lifecycle environments::
 Use content views and lifecycle environments, incorporating content view filters as needed.
@@ -63,43 +64,14 @@ Release version::
 Certain Red{nbsp}Hat repositories, such as the {RHEL} dot release repositories, include a *Release version* in their repository metadata.
 The release version is then compared with the release version specified in the *System purpose* properties of the host.
 Access to content may be limited or restricted based on this comparison.
-For more information about setting system purpose attributes, see {ManagingHostsDocURL}Creating_a_Host_managing-hosts[Creating a Host in {ProjectName}] in _{ManagingHostsDocTitle}_.
+For more information about setting system purpose attributes, see {ManagingHostsDocURL}editing-the-system-purpose-of-a-host-by-using-web-ui[Editing the system purpose of a host] in _{ManagingHostsDocTitle}_.
 endif::[]
 ifdef::orcharhino[]
 ifdef::red_hat_enterprise_linux[]
 Release version::
 Certain Red{nbsp}Hat repositories, such as the {RHEL} dot release repositories, include a *Release version* in their repository metadata.
 The release version is then compared with the release version specified in the *System purpose* properties of the host.
 Access to content may be limited or restricted based on this comparison.
-For more information about setting system purpose attributes, see {ManagingHostsDocURL}Creating_a_Host_managing-hosts[Creating a Host in {ProjectName}] in _{ManagingHostsDocTitle}_.
-endif::[]
-endif::[]
-
-.Incorporating all strategies
-A particular package or repository is available to a host only if all of the following are true:
-
-* The repository is included in the content view environments of the host.
-* The host's content view has been published after the repository was added to it.
-* The repository has not been filtered out by a content view filter.
-* The repository is enabled by default or overridden to *Enabled* by using a content override.
-* The repository has no architecture or operating system version restrictions or it has architecture or operating system version restrictions that match the host.
-ifndef::orcharhino[]
-* For certain Red{nbsp}Hat repositories either no release version is set or the release version matches that of the host.
-endif::[]
-ifdef::orcharhino[]
-ifdef::red_hat_enterprise_linux[]
-* For certain Red{nbsp}Hat repositories either no release version is set or the release version matches that of the host.
+For more information about setting system purpose attributes, see {ManagingHostsDocURL}editing-the-system-purpose-of-a-host-by-using-web-ui[Editing the system purpose of a host] in _{ManagingHostsDocTitle}_.
 endif::[]
 endif::[]
-
-.Using activation keys
-Using activation keys can simplify the workflow for some of these strategies.
-You can use activation keys to perform the following actions:
-
-* Assign hosts to content view environments.
-* Add content overrides to hosts.
-* Set system purpose attributes on hosts, including release version.
-
-Activation keys only affect hosts during registration.
-If a host is already registered, the above attributes can be changed individually for each host or through content host bulk actions.
-For more information, see {ContentManagementDocURL}Managing_Activation_Keys_content-management[Managing Activation Keys] in _{ContentManagementDocTitle}_.

…restricting-hosts-access-to-content.adoc …dules/con_content-access-strategies.adocguides/common/modules/con_restricting-hosts-access-to-content.adoc renamed to guides/common/modules/con_content-access-strategies.adoc guides/common/modules/con_restricting-hosts-access-to-content.adoc renamed to guides/common/modules/con_content-access-strategies.adoc

@@ -38,7 +38,7 @@ include::common/assembly_managing-alternate-content-sources.adoc[leveloffset=+1]
 
 include::common/assembly_importing-content.adoc[leveloffset=+1]
 
-include::common/assembly_restricting-hosts-access-to-content.adoc[leveloffset=+1]
+include::common/assembly_content-access-control-for-hosts.adoc[leveloffset=+1]
 
 include::common/assembly_managing-application-lifecycles.adoc[leveloffset=+1]