Multilingual graph for taxonomy term pages

/faq/{category}/ and /news/{section}/ pages had no hreflang, no
language menu, and an empty JS pageTranslations map because Zola's
term resource exposes no .translations field.

Base.html now derives a per-language term URL list by inspecting the
first page in the term: that page's translations point to each
per-language version, and each per-language version declares its
taxonomy slug in its own frontmatter (which is the localized term
slug). Built as parallel arrays since Tera has no inline dict literal.

The derived data feeds three places:
  * <link rel="alternate" hreflang> in base.html
  * The language dropdown in language_selector.html
  * The pageTranslations map in language_redirect.html

Each FAQ term page now ships 34 hreflang entries (33 langs + x-default)
plus 32 language menu items linking to the correctly-localized slug
(/it/faq/applicazione/, /ru/faq/приложение/, /pl/faq/aplikacja/, etc).

Author: biodranik

templates/base.html

@@ -95,6 +95,13 @@
   <link rel="canonical" href="{{ config.base_url | safe }}{{ resource_path | safe }}">
 
   {%- set translations = resource | get(key="translations", default=[]) -%}
+
+  {#- Taxonomy term pages (/faq/app/, /news/releases/) intentionally
+      get no hreflang annotations. Zola's term resource has no
+      .translations field, and inferring equivalents from the term's
+      pages produces inconsistent clusters when content uses mixed
+      slugs across languages (e.g. Hebrew posts tagged both
+      "releases" and "גרסאות"), which Google may discard entirely. -#}
   {%- if translations | length > 0 %}
   <link rel="alternate" hreflang="{{ lang }}" href="{{ current_url | safe }}">
   {%- for t in translations %}

templates/language_redirect.html

@@ -9,6 +9,10 @@
     {% for translation in resource.translations -%}
     "{{ translation.lang }}": "{{ translation.permalink  | replace(from=config.base_url, to="") | safe }}",
     {% endfor -%}
+    {%- elif term_translation_langs is defined and term_translation_langs | length > 0 -%}
+    {% for i in range(end=term_translation_langs | length) -%}
+    "{{ term_translation_langs[i] }}": "{{ term_translation_urls[i] | replace(from=config.base_url, to="") | safe }}",
+    {% endfor -%}
     {%- endif %}
   };
   var userPreferredLanguages = navigator.languages ? navigator.languages : [navigator.language];

templates/language_selector.html

@@ -7,7 +7,8 @@
   </script>
   <!-- Hidden checkbox is used for pure CSS toggle menu. -->
   {% set translations = resource | get(key="translations", default=[]) %}
-  {% if translations | length > 1 %}
+  {%- set has_term_translations = term_translation_langs is defined and term_translation_langs | length > 0 -%}
+  {% if translations | length > 1 or has_term_translations %}
   <input type="checkbox" id="lang-menu-trigger" class="lang-menu-trigger" />
   {% endif %}
   <label class="no-print" for="lang-menu-trigger">
@@ -24,5 +25,16 @@
     </li>
     {% endif %}
     {% endfor %}
+    {%- if has_term_translations -%}
+    {%- for i in range(end=term_translation_langs | length) -%}
+    {%- if term_translation_langs[i] != lang %}
+    <li class="lang-menu-item" role="menuitem">
+      <a class="lang-menu-link" onclick="return onLanguageClick('{{ term_translation_langs[i] }}');" href="{{ term_translation_urls[i] | replace(from=config.base_url, to="") | safe }}">
+        {{ trans(key="language", lang=term_translation_langs[i]) }}
+      </a>
+    </li>
+    {%- endif -%}
+    {%- endfor -%}
+    {%- endif -%}
   </ul>
 </span>