This repository was archived by the owner on Nov 24, 2025. It is now read-only.
Added Cache Groups overview section#4154
Merged
Merged
Conversation
Contributor
|
Refer to this link for build results (access rights to CI server needed): |
mitchell852
reviewed
Dec 5, 2019
mitchell852
reviewed
Dec 5, 2019
7 tasks
rawlinp
previously requested changes
Dec 10, 2019
Contributor
|
Refer to this link for build results (access rights to CI server needed): |
section about localization method was addressed
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What does this PR (Pull Request) do?
Adds a Cache Groups subsection to the Overview section of the documentation. Also cleans up some less-than-excellent formatting and removes a slew of false deprecation notices as well as linking the new subsubsections of the CG overview all over the docs.
Which Traffic Control components are affected by this PR?
What is the best way to verify this PR?
Build and read the docs, ensure no warnings, and that all information is comprehensible, complete, and renders well in the HTML output.
No test beacuase is docs
The following criteria are ALL met by this PR