chore(deps): update dependency jekyll-contentblocks to v2

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
jekyll-contentblocks	1.2.0 → 2.0.0

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

rustygeldmacher/jekyll-contentblocks (jekyll-contentblocks)

v2.0.0

Compare Source

A major modernization release: full Jekyll 4 support, powerful new contentblocks.<name> capabilities (repeatable blocks with front matter, and content-aware conditionals), and dropping the long-obsolete Jekyll 1.x/2.x line.

✨ New features

• Repeatable content blocks with front matter. You can now use the same block name more than once on a page and loop over the blocks individually in your layout via contentblocks.<name>. Each block can carry its own YAML front matter (exposed as data), with its Markdown rendered into content — great for lists like testimonials, team members, or cards:

  {% contentfor testimonial %}
  ---
  author: Ada Lovelace
  ---
  A **delightful** plugin.
  {% endcontentfor %}

  {% for t in contentblocks.testimonial %}
    <li>{{ t.content }} — <cite>{{ t.data.author }}</cite></li>
  {% endfor %}

  The existing {% contentblock %} / {% ifhascontent %} tags are unchanged.

• Content-aware conditionals. Every block name is now exposed as a Liquid variable, so you can branch on whether a block was filled — including in compound conditions, which ifhascontent can't express:

  {% if contentblocks.sidebar %}
    {% contentblock sidebar %}
  {% else %}
    <div>Default sidebar</div>
  {% endif %}
  
  {% if contentblocks.sidebar or page.force_sidebar %}
    ...
  {% endif %}

  This is usually cleaner than {% ifhascontent %} / {% ifnothascontent %}, which remain available (they specifically test for non-empty content, whereas contentblocks.<name> is truthy whenever the block was defined).

• Jekyll 4 support. The plugin now works across the entire Jekyll 3.0 → 4.4 range.

• Broader Ruby support — tested on Ruby 2.7 through 4.0.

💥 Breaking changes

• Jekyll < 3.0 is no longer supported. The gem now requires jekyll >= 3.0, < 5.0. Compatibility:
  • Jekyll 3.0–3.7 require Ruby 2.7 (they rely on APIs removed in Ruby 3).
  • Jekyll 3.8+ runs on Ruby 2.7 through 4.0.
• Requires Ruby 2.7.0 or newer. The gem now declares required_ruby_version >= 2.7.0, so it won't install on older Rubies (1.2.0 declared no floor).
• Blocks that begin with a --- YAML block are now parsed as front matter. If an existing contentfor block's content starts with a full ---…--- block, it's now interpreted as that block's data rather than rendered literally. (Narrow edge case, but worth flagging.)

🔧 Under the hood

• Test suite now runs the full Jekyll 3.0–4.4 matrix across Ruby 2.7 / 3.3 / 3.4 / 4.0 (40 CI cells).
• CI moved from CircleCI to GitHub Actions.
• Adopted rubyfmt (enforced as a CI gate); local toolchain pinned via mise (mise.toml).
• Removed the dead Jekyll 1.x/2.x code paths and refactored converter resolution to derive from the render context.

Thanks to @​stellarpower (#​24, repeatable blocks) and @​NikkyAI (#​21, conditionals) for the ideas behind these features.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "every weekend"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[netlify]

✅ Deploy Preview for kongdeveloper ready!

Name	Link
🔨 Latest commit	4b2c84a
🔍 Latest deploy log	https://app.netlify.com/projects/kongdeveloper/deploys/6a71b6a1e771030008c311a9
😎 Deploy Preview	https://deploy-preview-6530--kongdeveloper.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.