Comply with DITA - Mng content - CVs

guides/common/assembly_managing-content-views.adoc

@@ -8,25 +8,41 @@ include::modules/ref_best-practices-for-content-views.adoc[leveloffset=+1]
 
 include::modules/ref_best-practices-for-patching-content-hosts.adoc[leveloffset=+1]
 
-include::modules/proc_creating-a-content-view.adoc[leveloffset=+1]
+include::modules/proc_creating-a-content-view-by-using-web-ui.adoc[leveloffset=+1]
 
-include::modules/proc_copying-a-content-view.adoc[leveloffset=+1]
+include::modules/proc_creating-a-content-view-by-using-cli.adoc[leveloffset=+1]
+
+include::modules/proc_copying-a-content-view-by-using-web-ui.adoc[leveloffset=+1]
+
+include::modules/proc_copying-a-content-view-by-using-cli.adoc[leveloffset=+1]
 
 include::modules/proc_synchronizing-a-content-view-to-a-smart-proxy-server.adoc[leveloffset=+1]
 
-include::modules/proc_viewing-module-streams.adoc[leveloffset=+1]
+include::modules/proc_viewing-module-streams-by-using-web-ui.adoc[leveloffset=+1]
+
+include::modules/proc_viewing-module-streams-by-using-cli.adoc[leveloffset=+1]
+
+include::modules/proc_promoting-a-content-view-by-using-web-ui.adoc[leveloffset=+1]
 
-include::modules/proc_promoting-a-content-view.adoc[leveloffset=+1]
+include::modules/proc_promoting-a-content-view-by-using-cli.adoc[leveloffset=+1]
+
+include::modules/proc_promoting-a-content-view-to-all-environments-in-an-organization.adoc[leveloffset=+1]
 
 include::modules/con_rolling-content-views.adoc[leveloffset=+1]
 
-include::modules/proc_creating-a-rolling-content-view.adoc[leveloffset=+1]
+include::modules/proc_creating-a-rolling-content-view-by-using-web-ui.adoc[leveloffset=+1]
+
+include::modules/proc_creating-a-rolling-content-view-by-using-cli.adoc[leveloffset=+1]
 
-include::modules/proc_assigning-a-rolling-content-view-to-lifecycle-environments.adoc[leveloffset=+1]
+include::modules/proc_assigning-a-rolling-content-view-to-lifecycle-environments-by-using-web-ui.adoc[leveloffset=+1]
+
+include::modules/proc_assigning-a-rolling-content-view-to-lifecycle-environments-by-using-cli.adoc[leveloffset=+1]
 
 include::modules/con_composite-content-views-overview.adoc[leveloffset=+1]
 
-include::modules/proc_creating-a-composite-content-view.adoc[leveloffset=+1]
+include::modules/proc_creating-a-composite-content-view-by-using-web-ui.adoc[leveloffset=+1]
+
+include::modules/proc_creating-a-composite-content-view-by-using-cli.adoc[leveloffset=+1]
 
 include::modules/con_content-filter-overview.adoc[leveloffset=+1]
 

guides/common/modules/con_clearing-the-search-filter.adoc

@@ -3,6 +3,7 @@
 [id="Clearing_the_Search_Filter_{context}"]
 = Clearing the search filter
 
+[role="_abstract"]
 If you search for specific content types by using keywords in the *Search* text box and the search returns no results, click *Clear search* to clear all the search queries and reset the *Search* text box.
 
 If you use a filter to search for specific repositories in the *Type* text box and the search returns no results, click *Clear filters* to clear all active filters and reset the *Type* text box.

guides/common/modules/con_composite-content-views-overview.adoc

@@ -3,12 +3,15 @@
 [id="Composite_Content_Views_Overview_{context}"]
 = Composite content views overview
 
+[role="_abstract"]
 A composite content view combines the content from several content views.
 For example, you might have separate content views to manage an operating system and an application individually.
 You can use a composite content view to merge the contents of both content views into a new repository.
 The repositories for the original content views still exist but a new repository also exists for the combined content.
 
-If you want to develop an application that supports different database servers.
+.Application that supports different database servers
+====
+You want to develop an application that supports different database servers.
 The _example_application_ appears as:
 
 |===
@@ -47,11 +50,12 @@ Example composite content view for a MariaDB:
 | MariaDB (Database)
 | {client-os} (Operating System)
 |===
+====
 
 Each content view is then managed and published separately.
 When you create a version of the application, you publish a new version of the composite content views.
 You can also select the *Auto Publish* option when creating a composite content view, and then the composite content view is automatically republished when a content view it includes is republished.
 
-.Repository restrictions
+Repository restrictions::
 Docker repositories cannot be included more than once in a composite content view.
 For example, if you attempt to include two content views that contain the same docker repository in a composite content view, {ProjectServer} reports an error.

guides/common/modules/con_content-access-strategies.adoc

@@ -44,7 +44,7 @@ For more information about multiple content view environments, see xref:managing
 
 Composite content views::
 You can use composite content views to combine and give hosts access to the content from multiple content views.
-For more information about composite content views, see xref:Creating_a_Composite_Content_View_{context}[].
+For more information about composite content views, see xref:creating-a-composite-content-view-by-using-web-ui[].
 
 Architecture and operating system version restrictions::
 In custom products, you can set restrictions on the architecture and operating system versions for `{client-content-type}` repositories on which the product will be available.

guides/common/modules/con_content-filter-examples.adoc

@@ -3,6 +3,7 @@
 [id="Content_Filter_Examples_{context}"]
 = Content filter examples
 
+[role="_abstract"]
 Use any of the following examples with the procedure that follows to build custom content filters.
 
 [NOTE]
@@ -11,7 +12,8 @@ Filters can significantly increase the time to publish a content view.
 For example, if a content view publish task completes in a few minutes without filters, it can take 30 minutes after adding an exclude or include errata filter.
 ====
 
-.Example 1
+.Include a package group
+====
 Create a repository with the base {client-os} packages.
 This filter requires a {client-os} repository added to the content view.
 
@@ -20,8 +22,10 @@ This filter requires a {client-os} repository added to the content view.
   * *Inclusion Type:* Include
   * *Content Type:* Package Group
   * *Filter:* Select only the *Base* package group
+====
 
-.Example 2
+.Exclude errata
+====
 Create a repository that excludes all errata, except for security updates, after a certain date.
 This is useful if you want to perform system updates on a regular basis with the exception of critical security updates, which must be applied immediately.
 This filter requires a {client-os} repository added to the content view.
@@ -34,8 +38,10 @@ This filter requires a {client-os} repository added to the content view.
 Set the *Date Type* to *Updated On*.
 Set the *Start Date* to the date you want to restrict errata.
 Leave the *End Date* blank to ensure any new non-security errata is filtered.
+====
 
-.Example 3
+.Exclude errata and include a package group
+====
 A combination of Example 1 and Example 2 where you only require the operating system packages and want to exclude recent bug fix and enhancement errata.
 This requires two filters attached to the same content view.
 The content view processes the Include filter first, then the Exclude filter.
@@ -54,9 +60,11 @@ The content view processes the Include filter first, then the Exclude filter.
 Set the *Date Type* to *Updated On*.
 Set the *Start Date* to the date you want to restrict errata.
 Leave the *End Date* blank to ensure any new non-security errata is filtered.
+====
 
 ifdef::client-content-dnf[]
-.Example 4
+.Include a module stream
+====
 Filter a specific module stream in a content view.
 
 *Filter 1:*
@@ -72,8 +80,10 @@ Filter a specific module stream in a content view.
 * *Filter:* Add a rule to filter any non-modular packages that you want to exclude from the content view.
 If you do not filter the packages, the content view filter includes all non-modular packages associated with the module stream *ant*.
 Add a rule to exclude all `*` packages, or specify the package names that you want to exclude.
+====
 endif::[]
 
 ifndef::orcharhino[]
-For another example of how content filters work, see the following article: https://access.redhat.com/solutions/1564953["How do content filters work in Satellite 6"].
+.Additional resources
+* https://access.redhat.com/solutions/1564953["How do content filters work in Satellite 6"]
 endif::[]

guides/common/modules/con_content-filter-overview.adoc

@@ -3,6 +3,7 @@
 [id="Content_Filter_Overview_{context}"]
 = Content filter overview
 
+[role="_abstract"]
 ifdef::satellite[]
 Content views also use filters to include or restrict certain Yum content.
 endif::[]
@@ -11,8 +12,9 @@ Content views also use filters to include or restrict certain Deb and Yum conten
 endif::[]
 Without these filters, a content view includes everything from the selected repositories.
 
+Filter types::
 There are two types of content filters:
-
++
 .Filter types
 [cols="1,3"]
 |===
@@ -25,14 +27,13 @@ Use this filter when you want to use most of a particular content repository whi
 The filter uses all content in the repository except for the content you select.
 |===
 
-.Include and Exclude filter combinations
+Include and Exclude filter combinations::
 If using a combination of Include and Exclude filters, publishing a content view triggers the include filters first, then the exclude filters.
 In this situation, select which content to include, then which content to exclude from the inclusive subset.
 
-.Content types
-
+Content types::
 You can filter content based on the following content types:
-
++
 .Content types
 [cols="2,3"]
 |===

guides/common/modules/con_content-promotion-across-the-application-lifecycle.adoc

@@ -70,4 +70,4 @@ After a successful review, promote the package to the _Production_ environment:
 ====
 
 .Additional resources
-* xref:Promoting_a_Content_View_{context}[]
+* xref:promoting-a-content-view-by-using-web-ui[]

guides/common/modules/con_content-views-in-project.adoc

@@ -3,6 +3,7 @@
 [id="Content-Views-in-{ProjectNameID}_{context}"]
 = Content views in {ProjectName}
 
+[role="_abstract"]
 A content view is a deliberately curated subset of content that your hosts can access.
 By creating a content view, you can define the software versions used by a particular environment or {SmartProxyServer}.
 
@@ -17,11 +18,11 @@ For example, you can use one content view for content for managing an operating
 By creating a composite content view that combines both content views, you create a new repository that merges the repositories from each of the content views.
 However, the repositories for the content views still exist and you can keep managing them separately as well.
 
-.Default Organization View
+Default Organization View::
 A _Default Organization View_ is an application-controlled content view for all content that is synchronized to {Project}.
 You can register a host to the _Library_ environment on {Project} to consume the _Default Organization View_ without configuring content views and lifecycle environments.
-
 ifndef::satellite[]
++
 You can access unprotected repositories in the _Default Organization View_ content view.
 The URL consists of your {SmartProxy} FQDN, `/pulp/content/`, your organization label, `/Library/custom/`, your product label, `/`, your repository label, and a trailing `/`, for example, `\https://{foreman-example-com}/pulp/content/Example/Library/custom/{client-content-product-label}/{client-content-repository-label}/`.
 ifdef::content-management[]
@@ -40,7 +41,7 @@ endif::[]
 endif::[]
 endif::[]
 
-.Promoting a content view across environments
+Promoting a content view across environments::
 When you promote a content view from one environment to the next environment in the application lifecycle, {Project} updates the repository and publishes the packages.
 
 .Promoting a package from _Development_ to _Testing_
@@ -80,5 +81,5 @@ endif::[]
 ifeval::["{context}" == "planning"]
 [role="_additional-resources"]
 .Additional resources
-* For more information, see {ContentManagementDocURL}Managing_Content_Views_content-management[Managing content views] in _{ContentManagementDocTitle}_.
+* {ContentManagementDocURL}Managing_Content_Views_content-management[Managing content views in _{ContentManagementDocTitle}_]
 endif::[]

guides/common/modules/con_managing-content-views.adoc

@@ -3,6 +3,7 @@
 [id="Managing_Content_Views_{context}"]
 = Managing content views
 
+[role="_abstract"]
 {ProjectName} uses content views to allow your hosts access to a deliberately curated subset of content.
 To do this, you must define which repositories to use and then apply certain filters to the content.
 
@@ -16,7 +17,7 @@ For more information, see xref:Content_Filter_Examples_{context}[].
 For more information, see xref:Resolving_Package_Dependencies_{context}[].
 . Publish the content view.
 . Optional: Promote the content view to another environment.
-For more information, see xref:Promoting_a_Content_View_{context}[].
+For more information, see xref:promoting-a-content-view-by-using-web-ui[].
 . Attach the content host to the content view.
 
 ifdef::client-content-dnf[]
@@ -28,4 +29,4 @@ endif::[]
 
 Hosts can only be associated with a single content view.
 To associate a host with multiple content views, create a composite content view.
-For more information, see xref:Creating_a_Composite_Content_View_{context}[].
+For more information, see xref:creating-a-composite-content-view-by-using-web-ui[].

guides/common/modules/con_resolving-package-dependencies.adoc

@@ -3,6 +3,7 @@
 [id="Resolving_Package_Dependencies_{context}"]
 = Resolving package dependencies
 
+[role="_abstract"]
 {Project} can add dependencies of packages in a content view to the dependent repository when publishing the content view.
 To configure this, you can enable _dependency solving_.
 

guides/common/modules/con_rolling-content-views.adoc

@@ -3,6 +3,7 @@
 [id="rolling-content-views"]
 = Rolling content views
 
+[role="_abstract"]
 A rolling content view is a curated subset of content that your hosts can access.
 It is a subset of the Library environment and contains the latest synchronized content from one or multiple repositories.
 You can use a rolling content view to provide a continuous stream of synchronized content to hosts.

guides/common/modules/con_standardizing-content-view-empty-states.adoc

@@ -3,6 +3,7 @@
 [id="Standardizing_Content_View_Empty_States_{context}"]
 = Standardizing content view empty states
 
+[role="_abstract"]
 If there are no filters listed for a content view, click *Create filter*.
 A modal opens to show you the next steps to create a filter.
 Follow these steps to add a new filter to create new content types.

guides/common/modules/proc_assigning-a-rolling-content-view-to-lifecycle-environments.adoc → guides/common/modules/proc_assigning-a-rolling-content-view-to-lifecycle-environments-by-using-cli.adoc

@@ -1,26 +1,17 @@
 :_mod-docs-content-type: PROCEDURE
 
-[id="assigning-a-rolling-content-view-to-lifecycle-environments"]
-= Assigning a rolling content view to lifecycle environments
+[id="assigning-a-rolling-content-view-to-lifecycle-environments-by-using-cli"]
+= Assigning a rolling content view to lifecycle environments by using Hammer CLI
 
-You can assign your rolling content view to lifecycle environments to limit Library content synchronized to {SmartProxyServers}.
+[role="_abstract"]
+You can assign your rolling content view to lifecycle environments to limit Library content synchronized to {SmartProxyServers} by using Hammer CLI.
 
 To consume rolling content views, you must assign them to one or more lifecycle environments.
 By doing so, you expose a subset of Library content to those lifecycle environments.
 {Team} does not recommend assigning a rolling content view to the Library environment itself because it creates duplicate content within Library.
 By using environments other than Library, you can synchronize your rolling content views from {ProjectServer} to any {SmartProxyServers} that are configured to consume the relevant lifecycle environments without the need to synchronize all of Library to {SmartProxyServers}.
 
-To use the CLI instead of the {ProjectWebUI}, see the xref:cli-assigning-a-rolling-content-view-to-lifecycle-environments[].
-
 .Procedure
-. In the {ProjectWebUI}, navigate to *Content* > *Lifecycle* > *Content Views*.
-. Select your rolling content view.
-. Select the *Details* tab.
-. In the *Lifecycle Environments* field, assign your rolling content view to your lifecycle environments.
-. Click *Save Environments* to submit your changes to {Project}.
-
-[id="cli-assigning-a-rolling-content-view-to-lifecycle-environments"]
-.CLI procedure
 . List all content views:
 +
 [options="nowrap" subs="+quotes"]

guides/common/modules/proc_assigning-a-rolling-content-view-to-lifecycle-environments-by-using-web-ui.adoc

@@ -0,0 +1,23 @@
+:_mod-docs-content-type: PROCEDURE
+
+[id="assigning-a-rolling-content-view-to-lifecycle-environments-by-using-web-ui"]
+= Assigning a rolling content view to lifecycle environments by using {ProjectWebUI}
+
+[role="_abstract"]
+You can assign your rolling content view to lifecycle environments to limit Library content synchronized to {SmartProxyServers} by using {ProjectWebUI}.
+
+To consume rolling content views, you must assign them to one or more lifecycle environments.
+By doing so, you expose a subset of Library content to those lifecycle environments.
+{Team} does not recommend assigning a rolling content view to the Library environment itself because it creates duplicate content within Library.
+By using environments other than Library, you can synchronize your rolling content views from {ProjectServer} to any {SmartProxyServers} that are configured to consume the relevant lifecycle environments without the need to synchronize all of Library to {SmartProxyServers}.
+
+.Procedure
+. In the {ProjectWebUI}, navigate to *Content* > *Lifecycle* > *Content Views*.
+. Select your rolling content view.
+. Select the *Details* tab.
+. In the *Lifecycle Environments* field, assign your rolling content view to your lifecycle environments.
+. Click *Save Environments* to submit your changes to {Project}.
+
+.Next steps
+* Synchronize lifecycle environments to {SmartProxyServers}.
+For more information, see {AdministeringDocURL}Synchronizing_Content_from_{project-context}_Server_to_{smart-proxy-context-titlecase}_Servers_admin[Synchronizing content from {ProjectServer} to {SmartProxyServers}] in _{AdministeringDocTitle}_.

guides/common/modules/proc_comparing-content-view-versions.adoc

@@ -3,6 +3,7 @@
 [id="Comparing_Content_View_Versions_{context}"]
 = Comparing content view versions
 
+[role="_abstract"]
 Use this procedure to compare content view version functionality for {Project}.
 
 .Procedure

guides/common/modules/proc_copying-a-content-view-by-using-cli.adoc

@@ -0,0 +1,24 @@
+:_mod-docs-content-type: PROCEDURE
+
+[id="copying-a-content-view-by-using-cli"]
+= Copying a content view by using Hammer CLI
+
+[role="_abstract"]
+You can copy an existing content view into a new content view by using Hammer CLI.
+
+[NOTE]
+====
+A copied content view does not have the same history as the original content view.
+Version 1 of the copied content view begins at the last version of the original content view.
+As a result, you cannot promote an older version of a content view from the copied content view.
+====
+
+.Procedure
+* Copy the content view by using Hammer:
++
+[options="nowrap", subs="+quotes,attributes"]
+----
+$ hammer content-view copy \
+--name _My_original_CV_name_ \
+--new-name _My_new_CV_name_
+----