Update deploy workflow to use Eleventy build process #3955
Merged
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.
This replaces the existing files under
.github
(bothworkflows
andscripts
) with a new workflow using the Eleventy build process.conformance-challenges
,guidelines
, andrequirements
directories is retainedguidelines
techniques
,understanding
, andworking-examples
are now generated by the Eleventy build processThis has positive side effects over what's currently seen on https://w3c.github.io/wcag/techniques/ and https://w3c.github.io/wcag/understanding/:
Note that this intentionally does not clean out old files under
techniques
,understanding
, andworking-examples
(as mentioned in #3952 and seen rolled back in the 2nd commit in this PR). There are future plans to bring back obsolete techniques pages with some indication of their obsolescence; performing this cleanup now would lead to a lot of files being deleted now, only to be recreated later.Previews: