Repository navigation
Al folio migration - #3
Merged
Merged
Conversation
The migration carried over the news text but none of the photos. Recovered the 10 images from the source archive, where they live as CSS background images on divs whose aria-label is the caption the site displayed -- that pairing is what maps each photo to its news item. Rework _includes/news.liquid to take an `images:` list per item: - Thumbnails float right of the item text so it wraps alongside, dropping to full width below 576px. A clear on the cell keeps a tall photo from spilling into the next row. - Thumbnails are responsive webp (~57KB), but medium-zoom opens the untouched 2048px jpg via data-zoom-src, which drops srcset/sizes on the zoomed clone so the reader gets the original rather than an upscaled 480px variant. - Every image carries the archive's caption, plus separate descriptive alt text -- a caption like "Fincantieri Day" tells a screen reader nothing about the photo. Nine items gain images; Jan 2023 carries both of its SciTech talks. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
Present AOE 4065-4066 on the teaching page as the year-long sequence it is, with an entry per offering (2025-2026, 2024-2025) rather than two separate course bullets, and give each offering a photo gallery. Seed 2024-2025 with the senior design expo photo, which came from the Google Sites archive but had no news item to attach to. Offerings live in _data/air_vehicle_design.yml, following the people.yml and resources.yml pattern: adding a photo is a data edit plus a file drop under assets/img/teaching/air-vehicle-design/<year>/, with no template changes. The gallery is a wrapping flex grid, so it takes one photo or a dozen. Extract _includes/zoomable-figure.liquid -- responsive webp thumbnail, full-resolution zoom via data-zoom-src, caption -- rather than duplicating that markup here, and move the news page onto it so the two share one implementation. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Describe what changed and why.
Ownership Routing
docs/BOUNDARIES.md.al-folio) or I am porting a routed change and linked the owning repo issue/PR.Owning repo (if not starter):
Related issue/PR:
Plugin Ecosystem (if applicable)
If plugin-related, provide:
al_folio_min/al_folio_max):Starter Wiring Changes
Gemfiledependency wiring._config.ymlplugin activation/config._data/featured_plugins.ymlmetadata.Validation
npm cibundle exec jekyll buildnpm run lint:prettiernpm run lint:style-contracttest/integration_*.sh) as needednpm run test:visual) as neededNotes
Compatibility, migration implications, and follow-ups: