Repository navigation
merged 3.18 and 3.19 - #16
Closed
andreadavanzo wants to merge 1 commit into
Closed
andreadavanzo wants to merge 1 commit into
andreadavanzo wants to merge 1 commit into
Conversation
…Use Plaintext Formats When Appropriate" into "3.18 Include Expected And Beneficial Files"
Member
|
Discussed in Slack & Chat to merge the guidelines manually to deploy across all supplements. |
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 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.
I merged 3.18 "Include Files That Are Automatically Expected" and 3.19 "Use Plaintext Formats When Appropriate" in one point "3.18 Include Expected And Beneficial Files".These are the reasons:- robots.txt was mentioned in both sections, so merging the two avoids repetition.
I believe that merging the two sections, the explanation becomes more comprehensive. It effectively combines the expected files (like favicon.ico, robots.txt, etc.) and the beneficial files (like ads.txt, carbon.txt, etc.) into one unified guideline, making it easier for web developers to understand the full scope of important files they should include on their websites.
The two criteria now are extended to any new web standards or specifications.
The Additional Content sections have been merged as well.