DOC Update templates section #198
Merged
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
Closed
GuySartorelli
force-pushed
the
pulls/5.0/templates-section
branch
8 times, most recently
from
542005e
to
d2afd1a
Compare
GuySartorelli
force-pushed
the
pulls/5.0/templates-section
branch
from
d2afd1a
to
18cc1b4
Compare
emteknetnz
approved these changes
Apr 16, 2023
|
Need to rebase |
|
Rebased |
GuySartorelli
force-pushed
the
pulls/5.0/templates-section
branch
from
18cc1b4
to
2ea7db3
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.
A (relatively quick) sweep over the templates section of the docs to update any false or outdated information.
Note: This should be reviewed after #188
Scope
The primary purpose of this PR is to ensure that:
In many cases I may have also augmented the existing documentation to make it clearer or to add information I felt was missing.
There may also be cases where I have updated code examples or written documentation to better reflect best practices - but that is not the main purpose of this PR. If there are areas where I have not updated examples or docs to reflect best practices (but those examples work and the docs are factually correct) then they are out of scope for this PR.
Formatting that I haven't explicitly touched is definitely out of scope.
Issue