Bug 1465977 - Integrate DS Console appendix to procedures in guide
Integrate DS Console appendix to procedures in guide
Status: CLOSED CURRENTRELEASE
Product: Red Hat Directory Server
Classification: Red Hat
Component: Doc-administration-guide (Show other bugs)
10.1
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Marc Muehlfeld
Viktor Ashirov
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-06-28 11:15 EDT by Marc Muehlfeld
Modified: 2017-08-24 07:06 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-08-24 07:06:04 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Marc Muehlfeld 2017-06-28 11:15:47 EDT
Document URL: 
https://access.redhat.com/documentation/en-us/red_hat_directory_server/10/html/administration_guide/app.console


Section Number and Name: 
Appendix G. Using the Console


Describe the issue: 
A lot of the content in this section is duplicative in the Admin Guide. For example, there are two almost equal sections about how to create a new DS instance using the console.


Suggestions for improvement: 
* Remove the duplicate content from the appendix
* Check if we can move the remaining content to other parts of the guide. We want the guide to be more focused on user stories. For example, if we describe how to do something on the command line, we can additionally describe the GUI procedure in this area to. So we don't split one user story into a section in a chapter and in an appenxi.
Comment 1 Marc Muehlfeld 2017-08-24 07:06:04 EDT
I checked the appendix. Meanwhile several parts have been moved while I implemented other BZs. I rechecked today the appendix. At the moment I don't see anything else that makes sense to move out of this appendix.

Note You need to log in before you can comment on or make changes to this bug.