docs: build with eleventy instead of jekyll #9146
Draft
+1,652
−301
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.
TODO
Note
If building the site with this branch after using
npm run dev-site-with-docker, generated files indocs/_site/may belong toroot. To fix this:Benefits
Changes
Eleventy is mostly compatible with Jekyll, so there are minimal changes to the site.
The main changes are:
collections.xinstead ofsite.xitem.data.xinstead ofitem.xpage.titleto globaltitlepostscollection means thatpostnow becomespost.datavsglobal, depending on how the template is used