GitHub Pages now runs Jekyll 3.1
As promised, GitHub Pages has moved to the Jekyll 3.1 branch with an upgrade to Jekyll 3.1.6. Jekyll 3.1 brings significant performance improvements to GitHub Pages. By using Liquid::Drops, rather…
As promised, GitHub Pages has moved to the Jekyll 3.1 branch with an upgrade to Jekyll 3.1.6. Jekyll 3.1 brings significant performance improvements to GitHub Pages. By using Liquid::Drop
s, rather than Ruby Hash
es, Jekyll now calculates document and site metadata on demand, rather than calculating every possible value at build time.
While this should be a seamless transition for most GitHub Pages users, we recommend that all users test locally using the GitHub Pages Gem before pushing. This ensures that your site will continue to build as expected. Three things to note as you upgrade:
- All front matter defined in layouts are now accessible only via
{% raw %}{{ layout }}{% endraw %}
. In you define a variablewidth: full
in your layout’s YAML front matter, access it withlayout.width
. - The inheritance of front matter values properly merges a child layout’s front matter over its parent’s front matter. If you define a variable
color: purple
in a layout calledpost
which has a parent layout ofdefault
, and you definecolor: blue
in thedefault
layout, then{% raw %}{{ layout.color }}{% endraw %}
will bepurple
. For more on this, read the pull request that made the change. - If you are using the Jekyll Bootstrap theme, you must update the contents of
_includes/JB/setup
to use{% raw %}{{ layout.theme.name }}{% endraw %}
instead of{% raw %}{{ page.theme.name }}{% endraw %}
.
Beyond the performance improvements, Jekyll 3.1.6 includes over 100 changes, including many bug fixes, both to the rendering process and to the experience of previewing Jekyll locally.
For a full list of changes, see the Jekyll changelog and of course, if you have any questions, please get in touch with us.
Written by
Related posts
![](https://github.blog/wp-content/uploads/2023/10/Collaboration-DarkMode-2.png?resize=400%2C212)
2024 is the biggest global election year in history. What’s at stake for developers?
GitHub is considering what is at stake for our users and platform, how we can take responsible action to support free and fair elections, and how developers contribute to resilient democratic processes.
![](https://github.blog/wp-content/uploads/2023/10/AI-DarkMode-2.png?resize=400%2C212)
GitHub named a Leader in the Gartner first-ever Magic Quadrant for AI Code Assistants
This year, as part of its annual Magic Quadrant series, Gartner published a first-of-its-kind report analyzing the state of play in the AI Code Assistants market–and named GitHub a Leader.
![AI in software development 2024 survey results with colorful graphics and percentages.](https://github.blog/wp-content/uploads/2024/08/ai-survey-header.png?resize=400%2C212)
Survey: The AI wave continues to grow on software development teams
We surveyed 2,000 people on software development teams at enterprises in the U.S., Brazil, India, and Germany about the use, experience, and expectations around generative AI tools in software development.