Polyglot

Polyglot 1.14 - Più lingue, correzioni ai redirect, aggiornamenti dalla community

2026-08-21T00:00:00-06:00

Jekyll-Polyglot 1.14.0 è stato rilasciato! Questa versione estende il supporto alle lingue regionali, corregge casi limite nei redirect e aggiunge una nuova opzione di compatibilità con i plugin Jekyll che non supportano il parallelismo.

supporto per zh-TW e pt-PT

PR #316: Il sito web di Polyglot ora supporta il cinese tradizionale (zh-TW) e il portoghese europeo (pt-PT) come lingue del sito. Il sito di documentazione di Polyglot ora offre pagine tradotte per entrambe, accanto alle traduzioni esistenti zh-CN e pt-BR. Come sempre, queste traduzioni sono state realizzate con l’aiuto dell’IA; correzioni e miglioramenti sono benvenuti!

correzioni ai prefissi duplicati di redirect_from

PR #317: Correzioni al modo in cui Polyglot gestisce il frontmatter redirect_from con il plugin jekyll-redirect-from. I redirect definiti dall’utente ora vengono preservati invece di essere sovrascritti, correttamente limitati alla lingua corrispondente, e i redirect già dotati di prefisso di lingua non ricevono più un doppio prefisso — così un redirect come /fr/old-page non diventerà /fr/fr/old-page.

serial_default_lang per i plugin che non supportano il parallelismo

PR #310: @rathboma ha contribuito con la nuova opzione serial_default_lang. Quando parallel_localization è abilitato, Polyglot crea un processo per lingua tramite fork, il che può causare race condition con plugin come jekyll-assets che inizializzano cache condivise al primo utilizzo. Impostare serial_default_lang: true fa sì che Polyglot costruisca prima la lingua predefinita nel processo padre, prima di creare gli altri processi: in questo modo tali plugin si inizializzano esattamente una volta e i processi delle lingue ereditano lo stato già pronto. Se le build parallele di Polyglot sono mai entrate in conflitto con un altro plugin Jekyll, questa opzione può aiutare a evitare conflitti.

aggiornamenti delle dipendenze ruby

Questa versione mantiene inoltre aggiornate le dipendenze ruby.

Polyglot 1.13 - new liquid vars, SEO and redirect improvements

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

Jekyll-Polyglot 1.13.0 has been released! This release is made possible thanks to support and many contributions from @rathboma and Beekeeper Studio.

better hreflang generation

PR #282: @rathboma merged improvements to hreflang tag generation, adding a fallback option for unconfigured languages. This improves SEO and correctness of the generated headers on multilingual sites.

warnings on mismatched language codes

PR #287: @rathboma added build-time warnings when a post’s lang: value does not match any configured site language. Language matching is now case-insensitive, so EN and en are treated the same.
PR #290: @rathboma filtering now properly excludes posts written in languages that are not in the languages: config, preventing unconfigured content from leaking into builds.

localize Netlify _redirects

PR #285: @rathboma added a new localize_redirects option. When enabled, Polyglot automatically generates language-prefixed copies of the Netlify _redirects rules, so a redirect like /github also works for /fr/github, /de/github, and so on. See the SEO recipes page for setup details.

new liquid variables for translation status

PR #305: Two new liquid variables — page.missing_languages and page.available_languages — let your templates see which languages a page has been translated into, and which are still missing. Useful for building richer language switchers and sidebars.

new language translations

PR #303: The Polyglot documentation site now has Ukrainian (uk) and Hindi (hi) translations, with help from AI-assisted translation. Corrections are welcome!
PR #297: @manabu-nakamura contributed corrections to the Japanese (ja) site translations. Thank you!

AI development tooling support

PR #298: Polyglot now ships with first-class engineering support for GitHub Copilot, Claude Code, and the shared AGENTS.md convention. AI is part of the workflow now, and contributions made with these tools are welcome.
Additional CI quality checks were added, including htmlproofer and rubocop adjustments.

The documentation site sidebar now flags pages that do not yet have a translation in the active language, making gaps easier to spot for readers and contributors.

Thank you to @rathboma and everyone who contributed to this release!

Polyglot 1.12 - miglioramenti dei reindirizzamenti e contributi della community

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

Jekyll-Polyglot 1.12.0 è stato rilasciato! Questa versione si concentra sul miglioramento della gestione dei reindirizzamenti e include diversi contributi della community.

miglioramenti dei reindirizzamenti

Questa versione include importanti miglioramenti su come funzionano i reindirizzamenti con Polyglot:

PR #275: Preservazione dei tag di ancoraggio nei reindirizzamenti - grazie a una soluzione di @GruberMarkus, gli URL di reindirizzamento ora preservano correttamente i tag di ancoraggio, garantendo che gli utenti arrivino esattamente dove intendevano.
PR #293: Supporto reindirizzamento sottolingue per il plugin jekyll-redirect-from - suggerito da @rathboma, Polyglot ora delimita correttamente il frontmatter redirect_from attraverso le sottolingue, prevenendo reindirizzamenti duplicati e garantendo un routing corretto per le pagine in lingue non predefinite.

rilevare pagine di fallback con page.rendered_lang

PR #283: Nuova variabile page.rendered_lang - contribuita da @rathboma, questa nuova variabile liquid ti permette di rilevare quando una pagina viene renderizzata come fallback. Quando page.rendered_lang != site.active_lang, sai che il contenuto della pagina non è ancora stato tradotto.

La pagina /about è stata aggiornata con istruzioni su come utilizzare al meglio questa variabile liquid di convenienza page.rendered_lang.

nuovo supporto linguistico

PR #280: Il supporto per italiano e turco è stato aggiunto al sito di documentazione di Polyglot, espandendo la nostra portata multilingue.

contributi della community

Diversi membri della community hanno contribuito miglioramenti al progetto:

PR #277: Definizioni di rich text della sidebar aggiornate, migliorando la presentazione multilingue del sito.
PR #288: Stringhe di rich text giapponesi contribuite da @manabu-nakamura, migliorando l’esperienza della lingua giapponese.

Un ringraziamento speciale a @PanderMusubi per la demo jekyll-minimal-mistakes-polyglot, che mostra come integrare Polyglot con il popolare tema Minimal Mistakes.

Grazie a tutti i contributori che hanno reso possibile questa versione!

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.