WIP: Expand non-quick installation content #410
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tahliar
force-pushed
the
PED-2842-full-install-guide
branch
from
f0c2eb9
to
18d2861
Compare
tahliar
changed the title
jsc#PED-2842
jsc#PED-2842
It's no longer in the same guide, and the weirdly the xref resulted in a blank space instead of the Admin Guide's title
Oops I changed my mind
Will expand to be more detailed
For SLE 15, it just isn't viable to have a new guide. A lot of the content is already in the Admin Guide and would need to be either duplicated or linked to. Reusing content is currently not simple. For SLE 16, we can revisit having a separate guide.
tahliar
force-pushed
the
PED-2842-full-install-guide
branch
from
99fc267
to
8a95d11
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR creator: Description
Adding a full deployment guideExpanding the Admin Guide installation content so that all the options are clear. This is a long-term project and is currently a WIP.Opening a PR just for easier viewing of progress. It will need to be rebased regularly, so the commit dates in this PR do not reflect reality.
I originally kept track of the relevant product changes for each SP, but I've decided that it doesn't make sense to backport this, both because of complexity and to avoid issues with the localised content in earlier versions.
PR creator: Are there any relevant issues/feature requests?
PR creator: Which product versions do the changes apply to?
When opening a PR, check all versions of the documentation that your PR applies to.
main, no backport necessary)PR reviewer only: Have all backports been applied?
The doc team member merging your PR will take care of backporting to older documents.
When opening a PR, do not set the following check box.