Open
Conversation
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.
Description
In PR #1332 the site was moved from Eleventy to Zola. This broke some syntax highlighting, leading to the following build warnings:
This PR changes the language aliases to ones that are common to both site builders (see here and here).
Afterwards we are left with:
I think this was using the
httphighlight language with Eleventry and there doesn't seem to be an equivalent with Zola.Corresponding issue: n/a
Testing
Visual inspection with Zola to verify they make a difference and checking errors went away in terminal.
Checklist
masterfor website changes,devforsource changes)
approved via an issue
npm run test) and verified that it succeeded