Add SUMA guide and clarify subscriptions (SLL8) #36
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
changed the title
4 tasks
4 tasks
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
I've started with SLL8 because it's the cleanest to read (no big LTSS notes like SLL7, and still has CentOS unlike SLL9).
I'll adapt it for the other versions once the overall thing is approved.
The SUMA guide is basically a stub, but at this stage it doesn't make sense to duplicate whole SUMA guides in one little article so links will do just fine. The option is still there to possibly expand it in the future.
The new intro required a table. I tried to keep it as minimal as possible, and it's still much easier to read than the two itemlists I'd have needed otherwise.
PDFs:
SUMA guide:
art-suma-quickstart_en.pdf
RMT guide new intro:
art-quickstart_en.pdf
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.