Skip to content

Fix Jekyll build warnings#445

Merged
ColinEberhardt merged 4 commits into
ScottLogic:gh-pagesfrom
ColinEberhardt:gh-pages
Jul 16, 2026
Merged

Fix Jekyll build warnings#445
ColinEberhardt merged 4 commits into
ScottLogic:gh-pagesfrom
ColinEberhardt:gh-pages

Conversation

@ColinEberhardt

Copy link
Copy Markdown
Contributor

Resolves a number of deprecation warnings and Liquid syntax errors that appear during bundle exec jekyll serve / bundle exec jekyll build.

These fixes were all implemented by Claude Code.

Changes

1. Add jekyll-paginate to plugins (_config.yml)
Pagination was enabled (paginate: 20) but the gem was missing from the plugins list, causing a deprecation warning on every build.

2. Fix {% post_url %} tags in 12 posts (2013–2018)
Jekyll's updated post matching requires just the date-slug filename — the old author-prefixed format ({% post_url author/date-slug %}) no longer resolves correctly. Removed the prefix from all affected cross-post links.

3. Wrap foreign template syntax in {% raw %} blocks (4 posts)
Code blocks in four posts contain template/expression syntax from other systems (CircleCI {{ .Branch }}, React JSX {{color: ...}}, Java anonymous class initialisers {{ put(...) }}, GitHub Actions ${{ ... }}). Jekyll was attempting to parse these as Liquid, generating syntax warnings. Wrapped the affected code blocks in {% raw %}...{% endraw %}.

4. Add excerpt_separator: "" to front matter of 82 old HTML posts (2008–2013)
These posts contain Liquid blocks (e.g. {% highlight %}) that span a blank line, which Jekyll mistakes for the excerpt separator and warns about. Setting excerpt_separator to an empty string per-post suppresses the warning without affecting the rendered output.

Testing

Verified locally against a full jekyll build — output is clean with no warnings or deprecations remaining. Spot-checked the following pages in a local jekyll serve:

  • Home page + pagination (/, /page2/, /page3/) — post listing renders correctly
  • /2013/06/06/scala-macros-part-2.html — cross-post links to parts 1 and 3 resolve correctly
  • /2014/08/04/introducing-agile-development-to-client-projects.html — forward link to next post works
  • /2019/03/25/how-to-integrate-end-to-end-tests-in-circleci.html — CircleCI YAML code block renders with {{ .Branch }} visible
  • /2025/08/21/making-visual-comparison-test-maintenance-easier-with-github-actions.html — GitHub Actions block renders with ${{ matrix.os }} visible
  • /2009/05/12/silverlight-cliptobounds-can-i-clip-it-yes-you-can.html — old HTML post renders correctly; excerpt in listing page looks as expected

ColinEberhardt and others added 4 commits July 15, 2026 18:17
Pagination was enabled (paginate: 20) but the jekyll-paginate gem was
missing from the plugins list, causing a deprecation warning on build.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Jekyll's new post matching requires just the date-slug filename without
the author subdirectory prefix. Removed the author/ prefix from all
{% post_url author/date-slug %} references across 12 posts (2013-2018).

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Code blocks in these posts contain template/expression syntax from
CircleCI ({{ .Branch }}), React JSX ({{color: ...}}), Java anonymous
class initialisers ({{ put(...) }}), and GitHub Actions (${{ ... }})
that Jekyll mistakenly parses as Liquid, generating syntax warnings.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
These posts contain Liquid blocks (e.g. {% highlight %}) that span a
blank line, which Jekyll mistakes for the excerpt separator and emits
a warning. Setting excerpt_separator to an empty string per-post
prevents Jekyll from attempting to split an excerpt there.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@ColinEberhardt
ColinEberhardt merged commit 6baf249 into ScottLogic:gh-pages Jul 16, 2026
1 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant