Polyglot

Polyglot 1.13 - 新しいLiquid変数、SEOとリダイレクトの改善

2026-05-13T00:00:00-06:00

Jekyll-Polyglot 1.13.0がリリースされました！このリリースは、@rathbomaとBeekeeper Studioのサポートと多くの貢献によって実現しました。

hreflang生成の改善

PR #282：@rathbomaがhreflangタグ生成の改善をマージし、未設定の言語に対するフォールバックオプションを追加しました。これにより、多言語サイトで生成されるヘッダーのSEOと正確性が向上します。

言語コードの不一致に対する警告

PR #287：@rathbomaは、投稿のlang:値が設定されたサイト言語のいずれにも一致しない場合に、ビルド時に警告を出すようにしました。言語の照合は大文字小文字を区別しなくなったため、ENとenは同じものとして扱われます。
PR #290：@rathbomaフィルタリングがlanguages:設定に含まれていない言語で書かれた投稿を適切に除外するようになり、未設定のコンテンツがビルドに混入することを防ぎます。

Netlifyの_redirectsをローカライズ

PR #285：@rathbomaが新しいlocalize_redirectsオプションを追加しました。有効にすると、PolyglotはNetlifyの_redirectsルールの言語プレフィックス付きコピーを自動的に生成するため、/githubのようなリダイレクトは/fr/github、/de/githubなどでも動作します。設定の詳細についてはSEOレシピページをご覧ください。

翻訳ステータス用の新しいLiquid変数

PR #305：2つの新しいLiquid変数 — page.missing_languagesとpage.available_languages — により、ページがどの言語に翻訳されているか、またどの言語がまだ翻訳されていないかをテンプレートで確認できます。より充実した言語スイッチャーやサイドバーの構築に役立ちます。

新しい言語翻訳

PR #303：Polyglotドキュメントサイトに、AI支援翻訳の助けを借りてウクライナ語（uk）とヒンディー語（hi）の翻訳が追加されました。修正は歓迎します！
PR #297：@manabu-nakamuraが日本語（ja）サイト翻訳の修正に貢献してくださいました。ありがとうございます！

AI開発ツールのサポート

PR #298：PolyglotはGitHub Copilot、Claude Code、および共有のAGENTS.md規約に対する一流のエンジニアリングサポートを備えるようになりました。AIは今やワークフローの一部であり、これらのツールを使用した貢献を歓迎します。
htmlproofer、rubocopの調整を含む、CI品質チェックも追加されました。

サイドバーが未翻訳ページを表示

ドキュメントサイトのサイドバーは、アクティブな言語でまだ翻訳されていないページにフラグを立てるようになり、読者や貢献者にとってギャップが見つけやすくなりました。

このリリースに貢献してくださった@rathbomaとすべての方々に感謝します！

Polyglot 1.12 - リダイレクト改善とコミュニティ貢献

2026-01-31T00:00:00-07:00

Jekyll-Polyglot 1.12.0がリリースされました！このリリースはリダイレクト処理の改善に焦点を当てており、複数のコミュニティ貢献を含んでいます。

リダイレクト改善

このリリースには、Polyglotでリダイレクトがどのように機能するかについての重要な改善が含まれています：

PR #275：リダイレクトでのアンカータグの保持 - @GruberMarkusのソリューションのおかげで、リダイレクトURLがアンカータグを正しく保持するようになり、ユーザーが意図した場所に正確に到達できるようになりました。
PR #293：jekyll-redirect-fromプラグインのサブ言語リダイレクトサポート - @rathbomaの提案により、Polyglotはサブ言語間でredirect_fromフロントマターを正しくスコープするようになり、重複リダイレクトを防ぎ、デフォルト以外の言語ページの適切なルーティングを保証します。

page.rendered_langでフォールバックページを検出

PR #283：新しいpage.rendered_lang変数 - @rathbomaによる貢献で、この新しいliquid変数を使用すると、ページがフォールバックとしてレンダリングされているときに検出できます。page.rendered_lang != site.active_langの場合、ページコンテンツがまだ翻訳されていないことがわかります。

/aboutページは、このpage.rendered_lang便利なliquid変数の使用方法についての説明で更新されました。

新しい言語サポート

PR #280：イタリア語とトルコ語のサポートがPolyglotドキュメントサイトに追加され、多言語対応が拡大しました。

コミュニティ貢献

複数のコミュニティメンバーがプロジェクトに改善を貢献しました：

PR #277：サイドバーのリッチテキスト定義が更新され、サイトの多言語プレゼンテーションが改善されました。
PR #288：@manabu-nakamuraによる日本語リッチテキスト文字列の貢献で、日本語体験が向上しました。

人気のMinimal MistakesテーマとPolyglotを統合する方法を示すjekyll-minimal-mistakes-polyglotデモを提供してくれた@PanderMusubiに特別な感謝を。

このリリースを可能にしてくれたすべての貢献者に感謝します！

Polyglot 1.11 - その他の修正リリース

2025-09-20T00:00:00-06:00

Jekyll Polyglot 1.11.0がリリースされました。最近まで解決が困難だった複雑なバグの修正が含まれています。このリリースは、あなたのような貢献者やユーザーのおかげで実現しました。

jekyllテーマとの競合を修正

minimal-mistakesやchirpyなどの他のjekyllテーマは、exclude:設定でglobパターンを使用しており、以前はURL相対化を使用するウェブサイトのpolyglot処理と競合していました。@mattionsが、これらの値を相対化正規表現に適用する前にregex.escapeする修正を貢献しました。

この調整により、他の一般的なjekyllテーマとpolyglotをすぐに使用できるようになるはずです。

その他の様々な修正

日本語とアラビア語のサポート

polyglotウェブサイトには、アラビア語と日本語で翻訳されたサポート版があります。これらのサイト翻訳はAIの助けを借りて作成されました。何か誤訳があれば、より良い修正を貢献してください！

Polyglot 1.10 - i18n_headers improvements

2025-07-07T00:00:00-06:00

Jekyll-Polyglot 1.10 is now available. It has vast improvements and changes to the i18n_headers liquid plugin for SEO improvements, and minor adjustments for parallel build idempotency. Community Contributions and Vibe Coding helped with a large portion of these release features, testing and blog post.

This version of polyglot now requires ruby >= 3.1 , which may break in build systems.

i18n_headers improvements

the i18n_headers plugin now has extended capabilities as part of this release:

it will add <link rel="canonical" ...> for each page language, so indexing is unique across sites.
it will add <link rel="alternate" hreflang="x-default" ...> to point to default language version of a site, when no matching language is requested by the browser.
it will correctly define <link rel="alternate" hreflang="..." > for pages and posts in collections with custom permalinks.
the default url will now include the site.baseUrl if defined

this additionally fixes a bug noticed that caused absolute url relativization to mangle these tags unintentionally.

vibe-coded contributions

Using certain vibe coding tools have helped find, measure and verify bug fixes and features for this release. This is a new approach for software development, and it created advanced ruby tests against jekyll plugin code running against many built site languages.

The tests written with vibe coding helped ensure the code coverage remained high, and complex features could be added with confidence. Ensuring the test automation was in place ensured tricky features could be built correctly.

Additionally vibe coding tools helped translate this blog post into many languages.

community contributions

Jekyll-Polyglot has been supported by humans. Human language documentation is contributed by humans who want to see this plugin documented in their native tongue. Humans contributing bug fixes and documentation are what have helped this plugin reach thousands of downloads a release. AI assisted programming, in my hands or yours, will shape the software we use, and in the many languages we write and speak.

ruby >= 3.1 required

Ongoing security updates to jekyll-polyglot build-time dependencies required a major version upgrade to ruby 3.1 . This may affect build systems that build their docs with jekyll-polyglot. But now is a good time to upgrade to the latest ruby major by now. Speak up if these changes cause complications with jekyll builds.

Polyglot 1.9.0 - Instructional Improvements

2025-01-18T00:00:00-07:00

Jekyll-Polyglot 1.9.0 has been released, which has minor dependency updates, and instructional improvements for getting the most from your multi-language website.

Community provided instructional improvements

Thank you to aturret for helping to maintain the existing zh-CN site pages. 谢谢！

george-gca improved the optional derive_lang_from_path configuration to better identify document language from the path inference. Tests were added for his helpful feature improvement PR. This improvement helps infer the language of posts and pages missing lang frontmatter, from any part of the document filepath.

Github user yunseo-kim submitted a instructions to improve sitemap generation . To help with SEO, a website should have only one root sitemap.xml , and not have duplicates for each sub-language site. Be sure to add the sitemap.xml to the exclude_from_localization configuration.

Polyglot 1.8.1 - Community Bug Fixes Release

2024-08-18T00:00:00-06:00

Jekyll-Polyglot 1.8.1 has been released, which has a few feature improvements and recognizes community found bugs and provided fixes.

Community provided bugfixes

hacketiwack provided a stricter check for setting a doc permalink, preventing downstream problems with empty frontmatter fields.

Github user blackpill submitted a one character bugfix for the i18n headers tag when rendering the default language link alternative href.

Polyglot 1.8.0 - Community Contributions Release

2024-03-17T00:00:00-06:00

Get excited for Jekyll-Polyglot 1.8.0, which has a few feature improvements and recognizes community documentation and contributions!

language specific permalinks

One new feature is to give pages language specific permalinks and to retain their association to other relative pages. This new feature is again improved by antoniovazquezblanco, who is a gentleman and a scholar.

sitemap generation & i18n SEO

This release also recognizes the quality sitemap.xml and robots.txt solution provided by jerturowetz. This website now demonstrates and captures more SEO power by using these to be crawlable as a static jekyll website by search providers. See the example website files here.

jekyll :polyglot :post_write hook

Github user obfusk contributed a tiny PR a few years back:

With polyglot :site, :post_write like these run for each child processes:

Jekyll::Hooks.register :site, :post_write do |site|
  ...
end

This release adds a custom :post_write hook that runs exactly once, after all languages been processed (whether or not parallel_localization is used):

Jekyll::Hooks.register :polyglot, :post_write do |site|
  # do something amazing here!
end

This feature is helpful for complex jekyll static sites that make additional use of jekyll hook plugins.

She also contributed a fix for additional logging when language subprocesses crash. Thanks for this contribution!

localized variables and portuguese translation.

george-gca is a talented and awesome guy, contributing an entire blogpost on how best to localize rich text from site data. He also provided a site brazilian translation.

Localized variables

2024-02-29T00:00:00-07:00

Polyglot allows you to have different pages for different languages in your Jekyll site. For example, one could have a page about.md in English and another about.md in Spanish with completely different layouts. But if you want to have the same layout for both pages, you can use localized variables. This is a way to have different data for different languages in your Jekyll site, but using the same layout for all languages.

As an example I will use a template site created with Polyglot.

In that site they have an about page for every language, in their case english in _pages/en-us/about.md and brazilian portuguese in _pages/pt-br/about.md. In both pages we can see that they have the same keys in the frontmatter, but some with different values. Both files point to the same layout, about, and this layout uses the values in the frontmatter to render the page.

For example, the subtitle key in the english page has the value subtitle: <a href='#'>Affiliations</a>. Address. Contacts. Moto. Etc. and in the brazilian portuguese page it has subtitle: <a href='#'>Afiliações</a>. Endereço. Contatos. Lema. Etc.. To use this information in the layout, it is used like this:

{{ page.subtitle }}

The same goes for the content below the frontmatter in both files, which is simply used in the layout like this:

{{ content }}

Polyglot will automatically render the page with the correct values for the current language.

For the subtitle of the page they used key: value pairs in the frontmatter, but sometimes we want to use these same pairs in different parts of the site. For example, if we want to use the same subtitle in the about.md and in another page, we would have to repeat the same pair in the frontmatter of both pages. This is not ideal because if we want to change the subtitle we would have to change it in two places. This is where localized data comes in. You can create a file like _data/:lang/strings.yml, one for each language, and Polyglot will bring those keys under site.data[:lang].strings.

For example, in the template site there are two files, _data/en-us/strings.yml and _data/pt-br/strings.yml. In the first file they have:

latest_posts: latest posts

And in the second file they have:

latest_posts: últimas postagens

This way, they can use the latest_posts key in the layout like this:

{{ site.data[site.active_lang].strings.latest_posts }}

Which will correctly get the value for the latest_posts variable defined in the file _data/:lang/strings.yml for the current language.

Defining which variable to use in the frontmatter

Now if you want to define this variable in the frontmatter of the page, this gets a little bit trickier. One possible solution is to check if the value of the variable has a . in it, and if it does use the value in the file _data/:lang/strings.yml. This is how you would do it:

{% if frontmatter_var contains '.' %}
  {% assign first_part = frontmatter_var | split: '.' | first %}
  {% assign last_part = frontmatter_var | split: '.' | last %}
  {% capture result %}{{ site.data[site.active_lang].strings[first_part][last_part] }}{% endcapture %}
{% endif %}

{{ result }}

This will work, for example, if frontmatter_var = blog.title.

Now, if you need to check if the localization string (in this case blog.title) actually exists in the file _data/:lang/strings.yml before using it, you’ll have to create a plugin to check if the variable exists in the file _data/:lang/strings.yml and if it does, use it, otherwise fallback to any value you want. I will not go into detail on how to do this, but I will show you how to use it. You can see the code for the plugin here.

{% if frontmatter_var contains '.' %}
  {% capture contains_localization %}{% localization_exists {{ frontmatter_var }} %}{% endcapture %}
  {% if contains_localization == 'true' %}
    {% assign first_part = frontmatter_var | split: '.' | first %}
    {% assign last_part = frontmatter_var | split: '.' | last %}
    {% capture result %}{{ site.data[site.active_lang].strings[first_part][last_part] }}{% endcapture %}
  {% else %}
    {% capture result %}fallback value{% endcapture %}
  {% endif %}
{% endif %}

{{ result }}

Polyglot 1.7.0 and page_id front-matter for different permalinks by language

2023-10-29T00:00:00-06:00

I’m excited to announce Jekyll-Polyglot 1.7.0, which has a new feature to give pages language specific permalinks and to retain their association to other relative pages.

This new feature is provided by antoniovazquezblanco, who is a gentleman and a scholar.

use `page_id` frontmatter to associate pages with different permalinks

Polyglot associates pages by matching their permalinks or filenames. However some site translations may instead desire pages with unique permalinks.

Polyglot already coordinates multiple copes of the same document across different languages. So keying off of a different property like page_id is no different than keying off of the permalink.

Using a page_id to coordinate similar pages with different permalinks ensures that custom permalinks can still be seen on language specific sites.

redirects for unique permalinks

The challenge with unique permalinks comes with relativizing those urls. Polyglot avoids this problem entirely by suggesting consistent permalinks.

To help with this, polyglot sets redirect_from hidden frontmatter on these pages, listing the unique permalinks of corresponding pages.

When using the jekyll-redirect-from plugin, that frontmatter will be picked up, and intelligent redirects made to the page’s custom permalink.

To see this in action, visit this page with a long permalink in different languages.

Other bug fixes

This release should have a fix for #151 and #184, preventing crashes on startup when calling other jekyll commands.

Polyglot 1.6.0 and Simplified Chinese language support

2023-06-08T00:00:00-06:00

The Polyglot website has been updated with support for Chinese!

This is made possible by aturret, who contributed numerous bugfixes to the plugin, the website, and an entirely new site translation.

Additionally, jekyll-polyglot 1.6.0 is now available from rubygems.

Fix for relativization of frozen strings

Polyglot used String::gsub! which mutates a .frozen? string. This has now been fixed to duplicate the cloned string before modifying it.

A typo in the html on the site layout prevented the previous page navigation from being translated correctly.

Support for Chinese Language

With a big 谢谢 of support and appreciation to aturret, polyglot.untra.io now supports a zh-CN Simplified Chinese translation!