Skip to content

AGENTS.md

Latest commit

 

History

History
45 lines (32 loc) · 2.48 KB

AGENTS.md

File metadata and controls

45 lines (32 loc) · 2.48 KB
Raw

Galette Hugo Migration - Agent Summary

This document serves as a reference for future AI agents or developers working on the Galette website migration from Jekyll to Hugo.

Project Overview

The objective was to port the Galette website while preserving its original design, multi-language support, and historical content (posts and pages).

Key Achievements

1. Multi-language Support

  • Implemented using Hugo's native i18n features.
  • Configuration resides in hugo.toml under [languages].
  • Content is organized by language subdirectories in content/ (e.g., content/fr/, content/en/).
  • Translation strings are managed in i18n/*.yaml.
  • Created a langselector.html partial that maintains the original language order and highlights the active language.

2. Layout & Design

  • Base Structure: Defined in layouts/_default/baseof.html.
  • CSS Architecture: Uses SASS (assets/sass/). Main entry point is main.scss, which imports modular files from galette/.
  • Known Fixes:
    • Removed redundant <body> tags in partials that were breaking the layout.
    • Simplified CSS selectors (removed strict body > children) to accommodate Hugo's generated HTML structure.
    • Fixed the "Download Box" (aside#galette) styling by correcting linear-gradient syntax and using theme-consistent orange variables.
    • Restored the right-hand sidebar using CSS Grid within section.wrapper.

3. Content Migration

  • Automated scripts (migrate_content.py, fix_links.py, migrate_yaml_to_i18n.py) were used to convert Jekyll front matter and handle cross-references.
  • Preserved historical post dates and slugs.

Technical References

  • SASS Variables: assets/sass/_variables.scss contains the primary color palette (e.g., $galette-orange, $galette-blue).
  • Partials: Found in layouts/partials/, including specialized components like galettebar.html and langselector.html.
  • Building: Use hugo --gc --minify to generate the production site in the public/ directory.

Future Recommendations

  • Content Sync: Ensure any new content added to the original Jekyll sources (if still active) is properly migrated using the available scripts.
  • Link Validation: Periodically run a link checker on the built site to ensure RelPermalink logic correctly handles the multi-language path prefixes.
  • Minification: Always use the --minify flag to ensure the final CSS/JS matches the production-ready state.

Created on 2026-03-23 by GitHub Copilot.