jekyll-theme-zer0 1.30.0 → 1.31.1

data/README.md

@@ -43,11 +43,16 @@ preview: /assets/images/wizard-on-journey.png
 hero_image: /assets/images/wizard-on-journey.png
 excerpt: "AI-native Jekyll theme for GitHub Pages — multi-agent ready (Copilot, Codex, Cursor, Claude), AI-powered install & preview images, AIEO-optimized, with Docker-first development and 43 documented features"
 ---
-
 [![pages-build-deployment](https://github.com/bamr87/zer0-mistakes/actions/workflows/pages/pages-build-deployment/badge.svg)](https://github.com/bamr87/zer0-mistakes/actions/workflows/pages/pages-build-deployment) [![Gem Version](https://badge.fury.io/rb/jekyll-theme-zer0.svg)](https://badge.fury.io/rb/jekyll-theme-zer0) [![CI](https://github.com/bamr87/zer0-mistakes/actions/workflows/ci.yml/badge.svg)](https://github.com/bamr87/zer0-mistakes/actions/workflows/ci.yml) [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT) [![Docker](https://img.shields.io/badge/docker-ready-blue.svg)](https://github.com/bamr87/zer0-mistakes/blob/main/docker-compose.yml) [![Bootstrap](https://img.shields.io/badge/Bootstrap-5.3.3-purple.svg)](https://getbootstrap.com/) [![AI-Native](https://img.shields.io/badge/AI--Native-Copilot%20%7C%20Codex%20%7C%20Cursor%20%7C%20Claude-8A2BE2)](AGENTS.md) [![AIEO](https://img.shields.io/badge/AIEO-Optimized-ff69b4)](#-aieo-optimized--built-for-ai-citation)
 
 # zer0-mistakes
 
+> AI-native, Docker-first Jekyll theme for GitHub Pages sites, built on Bootstrap 5 and published as a Ruby gem.
+
+[![CI](https://github.com/bamr87/zer0-mistakes/actions/workflows/ci.yml/badge.svg)](https://github.com/bamr87/zer0-mistakes/actions/workflows/ci.yml) [![License](https://img.shields.io/github/license/bamr87/zer0-mistakes)](LICENSE) [![Live site](https://img.shields.io/badge/live-zer0--mistakes.com-2ea44f)](https://zer0-mistakes.com/)
+
+## Overview
+
 ### A modern website theme that just works — for blogs, docs, portfolios, and more
 
 **Free • Open source • Hosted on GitHub Pages for $0/month • Works on Mac, Windows, and Linux**
@@ -58,8 +63,6 @@ If you already know Jekyll, Ruby, Docker, or AI coding agents: the same theme gr
 
 [Get Started in 5 Minutes](#-get-started-in-5-minutes) • [What You Get](#-what-you-get) • [Who It's For](#-who-its-for) • [Advanced & AI Features](#-advanced-features-for-power-users) • [Live Demo](https://zer0-mistakes.com/)
 
----
-
 ## ✨ What You Get
 
 A complete, professional website out of the box — no design or coding required to start:
@@ -963,4 +966,15 @@ And these AI partners that make zer0-mistakes truly AI-native:
 
 **v1.19.1** • [Changelog](CHANGELOG.md) • [License](LICENSE) • [Contributing](CONTRIBUTING.md) • [AI Agent Guide](AGENTS.md)
 
+## Changelog
+
+Notable changes are recorded in [CHANGELOG.md](CHANGELOG.md). Tagged versions are on the [releases page](https://github.com/bamr87/zer0-mistakes/releases).
+
+## License
+
+Released under the [MIT License](LICENSE).
+
+---
 
+<!-- bamr87-portfolio-footer -->
+Part of the [bamr87 portfolio](https://github.com/bamr87) — browse every project on [Amr's GitHub profile](https://github.com/bamr87).

data/_data/backlog.yml

@@ -866,7 +866,7 @@ tasks:
 
   - id: T-033
     title: "Retire legacy test_installation.sh after equivalence audit against the installer harness"
-    status: open
+    status: done
     priority: P2
     area: tests
     risk: standard
@@ -880,6 +880,10 @@ tasks:
       uncovered into test_install_*.sh, then delete the legacy suite and remove the
       `installation` routing from test_runner.sh, ci.yml, and nightly-extended.yml.
       Until then it runs nightly and on install-path PRs only (2026-07 CI tiering).
+      Done 2026-10-02: the suite is deleted, its scenarios live in
+      test_install_legacy_flags.sh (marked "Ported from retired
+      test_installation.sh"), test_runner.sh routes no `installation` suite, and
+      the CI/nightly suite lists no longer name it.
     acceptance:
       - "Every test_installation.sh scenario is mapped to a harness equivalent or ported."
       - "test_installation.sh deleted; test_runner.sh no longer routes an `installation` suite."
@@ -887,7 +891,7 @@ tasks:
       - "Nightly extended run green after removal."
     links: { issue: null, pr: null, roadmap: null }
     created: 2026-07-06
-    updated: 2026-07-06
+    updated: 2026-10-02
   - id: T-034
     title: "Remove the dead preview_image_generator.rb Jekyll plugin and its test surface"
     status: done
@@ -999,7 +1003,7 @@ tasks:
 
   - id: T-037
     title: "Navbar width recovery: two clean label tiers, merged chevron, centered grid, no subtitle"
-    status: open
+    status: done
     priority: P2
     area: feat
     risk: standard
@@ -1018,13 +1022,32 @@ tasks:
       the navbar subtitle (_includes/core/branding.html — home hero only).
       Clarify the three toggles: labeled "Menu" text button below lg, gear moves
       into the unified drawer on mobile so only two toggles coexist.
+      Done 2026-09-23: collapsed the three container-query tiers to two (icon+label
+      >=51rem, icon-only below — the old 41-50.99rem bare-label tier and its
+      text-overflow: ellipsis safety net are gone), merged the dropdown chevron
+      into the parent link's hover row, gave the desktop grid's side tracks a
+      shared floor (--zer0-navbar-side-min), moved site.subtitle to the home hero,
+      and labeled the mobile menu toggle "Menu" (with aria-label mirroring the
+      visible text for WCAG 2.5.3). `grid-template-columns: 1fr auto 1fr` as
+      literally proposed breaks the container queries (track 2 must stay a
+      definite 1fr for `.bd-navbar-nav-viewport`'s `width: 100%` to resolve) —
+      used a shared side-track minimum instead; documented in-source. A prior
+      attempt (#454) reached the same design but was closed as stale — its author
+      had no Docker/Jekyll to run the Playwright suite or regenerate evidence.
+      This finishes it against a real local build (bundle + jekyll build +
+      Playwright), and additionally caught and fixed a collision the earlier
+      attempt's tooling couldn't check: the new visible "Menu" text reused the
+      already-defined `ui.menu_label` ("Toggle menu"), which would have shipped
+      wrong text — added a dedicated `ui.nav_menu_toggle_label` key instead.
+      49/49 Playwright checks pass (37 existing navbar.spec.js + 12 new
+      navbar-tiers.spec.js).
     acceptance:
       - "At 1024px and 1280px with 5 nav items every label is fully visible or the whole row is icon-only — no ellipses anywhere."
       - "Dropdown chevron shares the parent row's hover zone; no dead zone between link and chevron."
       - "Navbar carries logo + title only; subtitle appears on the home hero."
       - "regression test added"
       - "before/after evidence committed"
-    links: { issue: null, pr: null, roadmap: null }
+    links: { issue: 405, pr: 495, roadmap: null }
     created: 2026-08-18
     updated: 2026-08-18
 
@@ -1292,7 +1315,7 @@ tasks:
 
   - id: T-046
     title: "Retire the now-dead gotoBeforeScrollSpy fixture and cover the mobile offcanvas TOC spy"
-    status: open
+    status: done
     priority: P3
     area: tests
     risk: low
@@ -1354,13 +1377,13 @@ tasks:
 
   - id: T-048
     title: "Site-level theme_color re-pins --zer0-color-primary over the active skin"
-    status: open
+    status: done
     priority: P2
     area: feat
     risk: low
     effort: S
     source: issue
-    summary: "Discovered while making Mermaid diagrams follow the skin (ZER0-013 rework): the skin mixin (_sass/theme/_skins.scss) writes both --bs-primary and --zer0-color-primary under [data-theme-skin], but _includes/core/tokens-inline.html emits `:root { --zer0-color-primary: <theme_color.main> }` AFTER main.css, and :root ties [data-theme-skin] on specificity, so the later inline rule wins. Result on this site: buttons/links follow the skin (#6fa8dc on air, #8338ec on neon) while every custom component that reads --zer0-color-primary (callouts, code-block accent border, focus rings) stays on the config #007bff regardless of skin. Mermaid works around it by reading --bs-primary first; the token layer should agree with itself instead."
+    summary: "Done 2026-10-02 (#459): the skin wins. tokens-inline.html emits theme_color main/blue/purple only when no palette skin is active, the precedence is documented in docs/ui/design-tokens.md, and appearance.spec.js asserts it. Discovered while making Mermaid diagrams follow the skin (ZER0-013 rework): the skin mixin (_sass/theme/_skins.scss) writes both --bs-primary and --zer0-color-primary under [data-theme-skin], but _includes/core/tokens-inline.html emits `:root { --zer0-color-primary: <theme_color.main> }` AFTER main.css, and :root ties [data-theme-skin] on specificity, so the later inline rule wins. Result on this site: buttons/links follow the skin (#6fa8dc on air, #8338ec on neon) while every custom component that reads --zer0-color-primary (callouts, code-block accent border, focus rings) stays on the config #007bff regardless of skin. Mermaid works around it by reading --bs-primary first; the token layer should agree with itself instead."
     acceptance:
       - "With theme_color.main set, switching skin changes --zer0-color-primary as well as --bs-primary (probe getComputedStyle on <html>)."
       - "Decide and document the precedence: skin over site theme_color (recommended) or the reverse — one rule, applied to every --zer0-color-* the mixin sets."
@@ -1368,11 +1391,11 @@ tasks:
       - "before/after evidence committed"
     links: { issue: null, pr: null, roadmap: null }
     created: 2026-09-05
-    updated: 2026-09-05
+    updated: 2026-10-02
 
   - id: T-049
     title: "test_core.sh: Liquid nested-tag check and gem-content check can never fail"
-    status: open
+    status: done
     priority: P3
     area: tests
     risk: low
@@ -1389,7 +1412,7 @@ tasks:
 
   - id: T-050
     title: "Visual Snapshots tier: LiveReload reloads the page mid-test because npm ci lands after Jekyll starts watching"
-    status: open
+    status: done
     priority: P2
     area: tests
     risk: low

data/_data/consumers.yml

@@ -47,6 +47,25 @@
 #   gem_unconstrained   `gem 'jekyll-theme-zer0'` with no version — resolves
 #                       whatever RubyGems has at `bundle update` time; tracked
 #                       only (like resolved_lockfile), never reports drift
+#
+# ------------------------------------------------------------------------------
+# Stack fields (optional; informational — scripts/bin/propagate ignores them)
+# ------------------------------------------------------------------------------
+#   How far each consumer is aligned with the zer0 stack (one theme, one image
+#   engine, one CMS — templates/consumer/README.md § The zer0 stack). A dated
+#   snapshot of each consumer's default branch, not a live reading: refresh it
+#   from `zer0-cms doctor <checkout>` (bamr87/zer0-CMS), never from memory.
+#
+#   stack:
+#     checked             date the default branch was read
+#     image_gem           Gemfile requires zer0-image-generator
+#     preview_images      _config.yml has a preview_images: block
+#     vendored_generator  copies of the image engine the gem replaces
+#                         (_plugins/preview_*.rb forks, scripts/lib/
+#                         preview_generator.py, scripts/generate-preview-images.sh);
+#                         a deliberate local generator is NOT listed
+#     zer0_json           a zer0.json (zer0-CMS project file) is committed
+#     doctor              .github/workflows/zer0-doctor.yml caller is committed
 # ==============================================================================
 
 version: 1
@@ -77,6 +96,16 @@ consumers:
       hook, enabled by `user_overrides: true`, not a shadow — and no fix
       numbered #338 could be substantiated in that repo. Keep this field
       derived from audit-consumer output, not hand-maintained estimates.
+    stack:
+      checked: "2026-09-14"
+      image_gem: true
+      preview_images: true
+      vendored_generator:
+        - _plugins/preview_image_generator.rb
+        - _plugins/preview_generator.rb
+        - scripts/lib/preview_generator.py
+      zer0_json: false
+      doctor: false
     pins:
       - file: _config.yml
         kind: remote_theme
@@ -90,6 +119,14 @@ consumers:
     risk: >-
       Unpinned, same exposure as it-journey. Small override surface (2 includes).
       Recommend pinning and joining the fan-out.
+    stack:
+      checked: "2026-09-14"
+      image_gem: true
+      preview_images: true
+      vendored_generator:
+        - scripts/generate-preview-images.sh
+      zer0_json: false
+      doctor: false
     pins:
       - file: _config.yml
         kind: remote_theme
@@ -106,6 +143,15 @@ consumers:
       Gemfile.azure + _config.azure.yml, and local dev mounts a path gem. A bump
       must move the remote_theme tag and the gem constraint together or the two
       production stacks render different theme versions.
+    stack:
+      checked: "2026-09-14"
+      image_gem: false
+      preview_images: true
+      vendored_generator:
+        - _plugins/preview_image_generator.rb
+        - scripts/generate-preview-images.sh
+      zer0_json: true
+      doctor: false
     pins:
       - file: _config.yml
         kind: remote_theme
@@ -139,6 +185,15 @@ consumers:
       render different theme versions with nothing here to notice. Recommend
       pinning remote_theme and constraining Gemfile.azure together and joining
       the fan-out.
+    stack:
+      checked: "2026-09-14"
+      image_gem: false
+      preview_images: true
+      vendored_generator:
+        - _plugins/preview_image_generator.rb
+        - scripts/generate-preview-images.sh
+      zer0_json: true
+      doctor: false
     pins:
       - file: _config.yml
         kind: remote_theme
@@ -165,6 +220,14 @@ consumers:
       so one bump here re-rolls the whole org (12 sites). The hub's own
       _config.yml and hub.yml must move together — they are read by different
       code paths and drift silently otherwise.
+    stack:
+      checked: "2026-09-14"
+      image_gem: true
+      preview_images: true
+      vendored_generator:
+        - scripts/generate-preview-images.sh
+      zer0_json: false
+      doctor: false
     pins:
       - file: _config.yml
         kind: remote_theme
@@ -189,6 +252,14 @@ consumers:
       Unpinned, and an org hub: a theme break here reaches every auto-discovered
       member site at once. Recommend pinning both files together and joining
       the fan-out (dispatch: true) like year-of-ai.
+    stack:
+      checked: "2026-09-14"
+      image_gem: true
+      preview_images: true
+      vendored_generator:
+        - scripts/generate-preview-images.sh
+      zer0_json: false
+      doctor: false
     pins:
       - file: _config.yml
         kind: remote_theme
@@ -220,6 +291,13 @@ consumers:
       Gemfile.lock resolved 1.25.0 while the Gemfile constraint (~> 1.25)
       already permitted 1.28.0 — stale purely because nothing was nudging it.
       Keeps two deliberate include forks, declared in its .theme-overrides.yml.
+    stack:
+      checked: "2026-09-14"
+      image_gem: true
+      preview_images: true
+      vendored_generator: []
+      zer0_json: false
+      doctor: false
     pins:
       - file: Gemfile
         kind: gem_constraint
@@ -246,6 +324,13 @@ consumers:
       Unpinned, and with no local preview path a contributor cannot see a theme
       break before pushing. Keeps three deliberate overrides, declared in its
       .theme-overrides.yml.
+    stack:
+      checked: "2026-09-14"
+      image_gem: false
+      preview_images: false
+      vendored_generator: []
+      zer0_json: false
+      doctor: false
     pins:
       - file: _config.yml
         kind: remote_theme
@@ -264,6 +349,13 @@ consumers:
     risk: >-
       Unpinned, and its only build runs on push to main (jekyll-gh-pages.yml),
       so a break ships before anyone sees it.
+    stack:
+      checked: "2026-09-14"
+      image_gem: false
+      preview_images: false
+      vendored_generator: []
+      zer0_json: false
+      doctor: false
     pins:
       - file: _config.yml
         kind: remote_theme
@@ -289,6 +381,13 @@ consumers:
       "unreachable" rather than reading its pin — drift reporting needs a token
       here even though it is read-only. CI already supplies one; a bare local
       run will not.
+    stack:
+      checked: "2026-09-14"
+      image_gem: false
+      preview_images: false
+      vendored_generator: []
+      zer0_json: false
+      doctor: false
     pins:
       - file: _config.yml
         kind: remote_theme

data/_data/features.yml

@@ -2196,7 +2196,7 @@ features:
       docs: "docs/systems/multilingual-translation.md"
     features:
       - "One large full-translation job (workflow_dispatch) plus bounded incremental runs when English content changes"
-      - "Manifest-driven SHA change detection, pruning of deleted sources, and generated /fr<en-url> permalinks (GitHub Pages safe-mode friendly)"
+      - "Manifest-driven SHA change detection, pruning of deleted sources, and generated /fr/... permalinks mirroring the English URLs (GitHub Pages safe-mode friendly)"
       - "Markdown-safe segment translation: code, Liquid, wiki-links and URLs masked as placeholders and validated"
       - "Navbar language toggle with availability states, hreflang alternates, per-page html lang, machine-translation notice"
 

data/_data/i18n/fr.yml

@@ -4,18 +4,18 @@
 # scripts/translate.rb from _data/ui-text.yml (en). Regenerate via
 # the Translate workflow or: ruby scripts/translate.rb --langs fr
 # ================================================================
-skip_links: Liens d'accès rapide
-skip_primary_nav: Aller à la navigation principale
-skip_content: Aller au contenu
-skip_main_content: Aller au contenu principal
-skip_footer: Aller au pied de page
+skip_links: Liens d'évitement
+skip_primary_nav: Passer à la navigation principale
+skip_content: Passer au contenu
+skip_main_content: Passer au contenu principal
+skip_footer: Passer au pied de page
 page: Page
 pagination_previous: Précédent
 pagination_next: Suivant
 breadcrumb_home_label: Accueil
 breadcrumb_separator: "/"
-menu_label: Basculer le menu
-search_label: Basculer la recherche
+menu_label: Afficher/masquer le menu
+search_label: Afficher/masquer la recherche
 toc_label: Sur cette page
 ext_link_label: Lien direct
 less_than: moins de
@@ -28,7 +28,7 @@ author_label: 'Auteur :'
 comments_label: Laisser un commentaire
 comments_title: Commentaires
 more_label: En savoir plus
-related_label: Vous pourriez aussi aimer
+related_label: Vous aimerez peut-être aussi
 follow_label: 'Suivre :'
 feed_label: Flux
 powered_by: Propulsé par
@@ -47,8 +47,8 @@ comment_btn_submit: Envoyer le commentaire
 comment_btn_submitted: Envoyé
 comment_success_msg: Merci pour votre commentaire ! Il apparaîtra sur le site une
   fois approuvé.
-comment_error_msg: Désolé, une erreur s'est produite lors de l'envoi. Veuillez vous
-  assurer que tous les champs obligatoires sont remplis et réessayez.
+comment_error_msg: Désolé, une erreur s'est produite lors de l'envoi. Veuillez vérifier
+  que tous les champs obligatoires sont remplis et réessayer.
 loading_label: Chargement...
 search_label_text: Saisissez votre terme de recherche...
 search_placeholder_text: Saisissez votre terme de recherche...
@@ -60,9 +60,9 @@ stats_total_pages: Total des pages
 stats_categories: Catégories
 stats_tags: Étiquettes
 stats_last_updated: Dernière mise à jour
-stats_overview: Aperçu
+stats_overview: Vue d'ensemble
 stats_content_breakdown: Répartition du contenu
-theme_toggle: Basculer le thème
+theme_toggle: Changer de thème
 dark_mode: Mode sombre
 light_mode: Mode clair
 view_source: Voir la source
@@ -98,6 +98,22 @@ lang_machine_translated: auto
 lang_machine_translated_title: Traduction générée automatiquement
 lang_untranslated_note: Les langues marquées ne sont pas encore traduites — ces liens
   ouvrent la version originale.
-machine_translation_notice: Cette page a été traduite automatiquement à partir de
-  l'original en anglais.
+machine_translation_notice: Cette page a été traduite automatiquement depuis l'original
+  en anglais.
 machine_translation_view_source: Voir l'original
+diagram_label: Diagramme
+diagram_tools_label: Outils de diagramme
+diagram_zoom_in: Zoom avant
+diagram_zoom_out: Zoom arrière
+diagram_zoom_reset: Réinitialiser le zoom
+diagram_fullscreen: Afficher en plein écran
+diagram_fullscreen_close: Fermer le plein écran
+diagram_copy_source: Copier la source du diagramme
+diagram_copied: Copié
+diagram_copy_failed: Échec de la copie
+diagram_download: Télécharger en SVG
+diagram_error_title: Ce diagramme n'a pas pu être affiché
+diagram_error_hint: Vérifiez la syntaxe dans le Mermaid Live Editor. La source est
+  affichée ci-dessous pour ne rien perdre.
+diagram_source_label: Source du diagramme
+diagram_loading: Chargement du diagramme