Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -14,9 +14,13 @@
.Procedure
. In the {ProjectWebUI}, ensure the context is set to the organization you want to use.
. Navigate to *Content* > *Subscriptions*.
. Click *Manage Manifest*.
. In the *Manage Manifest* window, click *Choose File*.
. Navigate to the location that contains the Red{nbsp}Hat subscription manifest file, then click *Open*.
. If no manifest is imported, click *Import a Manifest*.
To import a manifest when one is already present, open the actions menu and click *Manage manifest*.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
To import a manifest when one is already present, open the actions menu and click *Manage manifest*.
. Click *Import a Manifest*.

I think there is a bit of a problem here as the next step only applies for users who are following the Manage Manifest method.
I am wondering if we can keep this procedure only for users who are uploading a new manifest i.e. the empty state action, and update the procedure in proc_updating-and-refreshing-red-hat-subscription-manifests.adoc.
This module is rendered only for the Managing Content guide and I believe this information only belongs in that guide, and not in the Installation guides.

Comment on lines +17 to +18

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

another issue: If line 17 starts with "If ...", then users might not continue to read line 18. So IMO line 18 should also be a step. Maybe use two if statements:

Suggested change
. If no manifest is imported, click *Import a Manifest*.
To import a manifest when one is already present, open the actions menu and click *Manage manifest*.
. Import your manifest:
* If no manifest is imported, click *Import a Manifest*.
* If you already have a manifest imported to {Project}, open the actions menu and click *Manage manifest*.

Maybe it also makes sense to move line 19 under the second unordered list item.

. In the *Manage Manifest* window, on the *Manifest* tab, next to *Import new manifest*, click *Upload*.
You can also drag the manifest `.zip` file onto *Drag here* or *Upload a zip file*.
. Select the Red{nbsp}Hat subscription manifest `.zip` file.

The import starts when you select the `.zip` file.

Check warning on line 23 in guides/common/modules/proc_importing-a-red-hat-subscription-manifest-by-using-web-ui.adoc

View workflow job for this annotation

GitHub Actions / lint DITA

[vale] reported by reviewdog 🐶 Content other than a single list cannot be mapped to DITA steps. Raw Output: {"message":"Content other than a single list cannot be mapped to DITA steps.","location":{"path":"guides/common/modules/proc_importing-a-red-hat-subscription-manifest-by-using-web-ui.adoc","range":{"start":{"line":23,"column":1},"end":{"line":23,"column":51}}},"severity":"WARNING","code":{"value":"AsciiDocDITA.TaskStep","url":"https://github.com/jhradilek/asciidoctor-dita-vale/blob/main/README.md#warnings"}}
Comment on lines +22 to +23

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The import starts when you select the `.zip` file.

This seems redundant.


ifdef::content-management[]
.Next steps
Expand Down
Loading