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:, запобігаючи проникненню неналаштованого вмісту до збірок.

локалізація _redirects для Netlify

PR #285: @rathboma додав нову опцію localize_redirects. Коли її увімкнено, Polyglot автоматично генерує копії правил Netlify _redirects з мовним префіксом, тож перенаправлення на кшталт /github також працює для /fr/github, /de/github і так далі. Деталі налаштування дивіться на сторінці SEO-рецептів.

нові змінні liquid для статусу перекладу

PR #305: Дві нові змінні liquid — page.missing_languages та page.available_languages — дозволяють вашим шаблонам бачити, на які мови сторінка вже перекладена, а яких ще бракує. Корисно для побудови багатших перемикачів мови та бічних панелей.

нові мовні переклади

PR #303: Сайт документації Polyglot тепер має переклади українською (uk) та гінді (hi), створені за допомогою перекладу на основі ШІ. Виправлення вітаються!
PR #297: @manabu-nakamura вніс виправлення до японських (ja) перекладів сайту. Дякуємо!

підтримка інструментів розробки на основі ШІ

PR #298: Polyglot тепер постачається з першокласною інженерною підтримкою GitHub Copilot, Claude Code та спільної конвенції AGENTS.md. ШІ тепер є частиною робочого процесу, і внески, зроблені з цими інструментами, вітаються.
Було додано додаткові перевірки якості CI, зокрема правки htmlproofer та rubocop.

бічна панель показує відсутні переклади

Бічна панель сайту документації тепер позначає сторінки, які ще не мають перекладу активною мовою, роблячи прогалини помітнішими для читачів та контриб’юторів.

Дякуємо @rathboma та всім, хто долучився до цього релізу!

Polyglot 1.12 - redirect improvements and community contributions

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

Jekyll-Polyglot 1.12.0 has been released! This release focuses on improving redirect handling and includes several community contributions.

redirect improvements

This release includes important improvements to how redirects work with Polyglot:

PR #275: Anchor tag preservation in redirects - thanks to a solution from @GruberMarkus, redirect URLs now properly preserve anchor tags, ensuring users land exactly where they intended.
PR #293: Sublanguage redirect support for the jekyll-redirect-from plugin - suggested by @rathboma, Polyglot now correctly scopes redirect_from frontmatter across sublanguages, preventing duplicate redirects and ensuring proper routing for non-default language pages.

detect fallback pages with page.rendered_lang

PR #283: New page.rendered_lang variable - contributed by @rathboma, this new liquid variable lets you detect when a page is being rendered as a fallback. When page.rendered_lang != site.active_lang, you know the page content hasn’t been translated yet.

The /about page has been updated with instructions on how to best use this page.rendered_lang convenience liquid variable.

new language support

PR #280: Italian and Turkish language support has been added to the Polyglot documentation site, expanding our multilingual reach.

community contributions

Several community members contributed improvements to the project:

PR #277: Updated sidebar rich text definitions, improving the site’s multilingual presentation.
PR #288: Japanese rich text strings contributed by @manabu-nakamura, enhancing the Japanese language experience.

A special thanks to @PanderMusubi for the jekyll-minimal-mistakes-polyglot demo, showing how to integrate Polyglot with the popular Minimal Mistakes theme.

Thank you to all contributors who made this release possible!

Polyglot 1.11 - miscellaneous fixes release

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

Jekyll Polyglot 1.11.0 has been released. It has fixes for tricky bugs that have been challenging to solve until recently. This release is possible thanks to fellow contributors and users like you.

fixed conflicts with jekyll themes

Other jekyll themes such as miminal-mistakes or chirpy use glob patterns in exclude: configurations which would previously conflict with polyglot processing websites with url relativization. @mattions contributed a fix to regex.escape these values before being applied to the relativization regexes.

This adjustment should help with using polyglot out-of-the-box with other common jekyll themes.

other miscellaneous fixes

support for japanese and arabic

The polyglot website now has translated support versions in arabic and japanese. These site translations were made with the help of AI ; if anything is mistranslated please contribute better corrections!

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!

Polyglot

Polyglot 1.13 - нові змінні liquid, покращення SEO та перенаправлень

покращена генерація hreflang

попередження про невідповідні мовні коди

локалізація _redirects для Netlify

нові змінні liquid для статусу перекладу

нові мовні переклади

підтримка інструментів розробки на основі ШІ

бічна панель показує відсутні переклади

Polyglot 1.12 - redirect improvements and community contributions

redirect improvements

detect fallback pages with page.rendered_lang

new language support

community contributions

Polyglot 1.11 - miscellaneous fixes release

fixed conflicts with jekyll themes

other miscellaneous fixes

support for japanese and arabic

Polyglot 1.10 - i18n_headers improvements

i18n_headers improvements

vibe-coded contributions

community contributions

ruby >= 3.1 required

Polyglot 1.9.0 - Instructional Improvements

Community provided instructional improvements

Polyglot 1.8.1 - Community Bug Fixes Release

Community provided bugfixes

Polyglot 1.8.0 - Community Contributions Release

language specific permalinks

sitemap generation & i18n SEO

jekyll :polyglot :post_write hook

localized variables and portuguese translation.

Localized variables

Sharing a layout between pages

Sharing a layout between pages with localized data

Defining which variable to use in the frontmatter

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

use page_id frontmatter to associate pages with different permalinks

redirects for unique permalinks

Other bug fixes

Polyglot 1.6.0 and Simplified Chinese language support

Fix for relativization of frozen strings

Fix for site navigation not being translated

Support for Chinese Language

use `page_id` frontmatter to associate pages with different permalinks