fix(hero): forward the cover flag into the hero body partial

[markdumay]

Found while investigating gethinode/hinode#2107.

Problem

hero.hugo.html passes cover to utilities/section.html but omits it from the assets/hero.html dict. So at assets/hero.html:158:

{{ if not $args.cover }}my-md-auto align-self-end{{ else }}hero-image-full-height{{ end }}

$args.cover always resolved to the structure default false. The hero-image-full-height branch was unreachable, and the SCSS added in 36701b5 ("fix(hero): add full-height image styling for cover sections", Feb 2026) had never applied to a rendered page.

None of the six callers of assets/hero.html passed cover.

Change

One line: forward cover. The hero structure already declares it.

What this actually does — less than the class name suggests

Measured in the Hinode exampleSite at 1900×1031 with cover: true:

• Landscape illustrations: no change at all. Under object-fit: contain the width is already the binding dimension, so the rendered box is identical either way (428×241).
• Portrait illustrations: contained instead of overflowing. 989px tall with the class; 1284px without, inflating the section to 1332px — past the intended cover height.

The reason it does so little: the section is d-flex align-items-center, so its inner container is centred rather than stretched. Every height: 100% in that SCSS resolves against a 292px content-sized row, never the 940px section. So the class is a guard against over-tall illustrations, not the "fill the full height" feature its name and commit message claim.

Worth shipping as-is — it's a real improvement for portrait images and the branch is meant to be reachable — but the naming and intent are worth a second look. I did not rename or redesign it; that's a layout change beyond this fix.

Scope

Hero only. about, featured, panels, contact-form, and contact compose assets/hero.html as a layout primitive with their own fixed orientation and width choices; forwarding cover there would silently change existing renders for blocks that never had the behavior.

npm test passes.

🤖 Generated with Claude Code

[markdumay]

🎉 This PR is included in version 2.3.5 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀