Allow running builds against a custom local guidelines folder #4182
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
✅ Deploy Preview for wcag2 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
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.
These changes are part 1 of 2 to enable preview builds against the
WCAG-2.1branch. This part applies to themainbranch; see #4183 for part 2, which applies toWCAG-2.1.This adds logic to
getPrinciplesandgetTermsMapcode flows to allow explicitly specifying a localguidelines/index.htmlpath when building for a specific version, to be used in place of requesting the latest published recommendation for the specifiedWCAG_VERSION. This allows us to directly reuse the build process from themainbranch for generating preview builds againstWCAG-2.1, rather than needing to copy the entire Eleventy build process to that branch and keep it in sync.I have verified that this does not cause any changes to existing builds without the new variable, with
WCAG_VERSIONset to22,21, or unset.