Add footer-legal block for fortinet.com's second (gray) footer section - #25
Merged
Conversation
fortinet.com's footer has a whole section below the main black footer that this site didn't have at all: a light-gray strip (bg #e6e6e6, measured directly from .footer-row.copyrights) with a sponsor/partner badge row, a copyright line, an extended legal-links row, a tagline, and an "Also of Interest" links row. New block, not just more content in the existing footer block, since this section is a real markup/style if — full-bleed light gray rather than the black footer's centered-on-black columns, and needs its own section-level override of the generic centered "footer .footer > div" padding rule (matching the same full-bleed-override pattern already used in cards-panel.css). decorate() classifies each authored row by what it actually contains (images+links → badge row, text starting "Copyright" → copyright line, text containing "Also of Interest" → that row, 2+ links → the legal-links row, otherwise → tagline) rather than depending on a fixed row order, so an author isn't locked into an exact sequence. Self-hosted all 7 badge images (the Fortinet wordmark + 6 sponsor logos: Founders Cup, FC Barcelona, DP World Tour, PGA Tour Americas, Juventus, Romain Attanasio) from fortinet.com's own DAM, matching the same fetch-and-inline pattern used for carousel-story-dots.svg and the cards-trust watermarks. Badge order/spacing verified against fortinet.com's real x-positions — the wordmark sits well apart from the sponsor-badge cluster after it (margin-right:auto on just that first item), not an equal gap between every badge. Tested by injecting the block's expected authored markup directly into the live footer and running decorate() on it (the real /footer content lives in a connected CMS document, not this repo, and drafts/ pages don't apply to header/footer — both load from that same real content path regardless of which page you're viewing). Verified at 390px and 1464px widths against fortinet.com directly. The actual footer document still needs this block's markup added to render on the live site — see the content draft shared separately for the exact authored content (badges, copyright, legal links, tagline, "Also of Interest") to paste in, plus how to invoke a "Footer Legal" block section. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
Hello, I'm the AEM Code Sync Bot and I will run some actions to deploy your branch and validate page speed.
Commits
|
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
Adds a new
footer-legalblock for the second (light gray) section fortinet.com's real footer has below the main black footer — a sponsor/partner badge row, copyright line, extended legal-links row, tagline, and "Also of Interest" links. We didn't have this section at all.footerblock: this section is full-bleed light gray (#e6e6e6, measured directly from fortinet.com's.footer-row.copyrights), not centered-on-black like the columns above it — needs its own section-level override of the generic centeredfooter .footer > divpadding rule (same pattern already used incards-panel.css).decorate()classifies each authored row by what it actually contains (images+links → badge row, text starting "Copyright" → copyright line, "Also of Interest" → that row, 2+ links → legal-links row, otherwise → tagline), so an author isn't locked into an exact row order.No live demo URL — here's why
The real
/footercontent lives in a connected CMS document (Word/Google Docs-style, per.migration/project.json), not in this repo, and I don't have edit access to it. That also meansdrafts/test pages don't help here — header/footer always load from that same real content path regardless of which page you're viewing, even locally with--html-folder drafts.I tested this by injecting the block's expected authored markup directly into the live footer and running
decorate()on it in a real browser session, verified at 390px and 1464px against fortinet.com directly (see screenshots in chat).To make this visible on a real preview URL: add a new section to the footer CMS document with a "Footer Legal" block (one row per part: badges, copyright, legal links, tagline, "Also of Interest") — the exact content/table to paste in is in the content draft shared earlier in this conversation. Once that's in, the feature-preview URL will show it rendering, and I can re-verify against fortinet.com there.
Test URL
None yet — see above.
https://footer-legal-section--modernization-agent-test--samshao.aem.page/will show it once the footer doc has content for it.🤖 Generated with Claude Code