excat-footer-orchestrator

Orchestrate AEM EDS footer migration and parity validation with content and visual comparisons.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/aemdemos/summit-dsg --skill excat-footer-orchestrator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: excat-footer-orchestrator
Source: https://github.com/aemdemos/summit-dsg/tree/main/.agents/skills/excat-footer-orchestrator
Command: npx skills add https://github.com/aemdemos/summit-dsg --skill excat-footer-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates the migration and parity validation of site footers to eliminate manual rework and visual/content mismatches when moving or replicating footers across environments. It ensures links, legal/disclosure copy, social icons, and newsletter forms match the source and are implemented as content-driven, accessible blocks.

Core Features & Use Cases

  • Evidence-driven parity: Requires source evidence (URL and/or full-width screenshots) and compares DOM, spacing, iconography, and link order against the source.
  • Content-first workflow: Directs authors to keep user-visible copy in content locations (for example content/footer) and implement structure in blocks/footer rather than hard-coded strings.
  • Developer checks: Enforces linting, accessibility semantics, mobile-first breakpoints, and integration with repository hooks under .agents/hooks for automation and validation.
  • Use Case: Use when migrating or replicating an AEM EDS footer to ensure the migrated footer matches the production source and passes lint and accessibility gates.

Quick Start

Ask the orchestrator to "migrate footer" or "replicate footer" and attach the source URL and full-width screenshots for verification.

Frequently Asked Questions about excat-footer-orchestrator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate a website footer in AEM EDS without visual mismatches?

Footer parity validation checks that migrated link columns, legal text, social icons, and newsletter forms match the source by comparing DOM structure, spacing, and iconography against provided URLs or full-width screenshots.

How do I validate footer accessibility and linting during AEM migration?

You validate footer accessibility and linting during AEM migration by enforcing checks through repository hooks under .agents/hooks. The workflow requires content-driven authoring in blocks/footer to pass lint and accessibility gates automatically.

Does AEM EDS footer migration require source screenshots and URLs?

Yes, AEM EDS footer migration requires source evidence such as URLs and full-width screenshots. This evidence is necessary to perform accurate content and visual comparisons for link columns, legal text, icons, and forms.

What is the best way to structure content for an AEM EDS footer block?

The best way to structure an AEM EDS footer block is keeping user-visible copy in content locations like content/footer and implementing structure in blocks/footer. This content-first workflow avoids hard-coded strings for accessible authoring.

Can I use this footer migration workflow for primary navigation and headers?

No, this footer migration workflow is specifically designed for footer-specific validation and excludes header or primary navigation migration. It applies only to replicating and validating footer components in AEM EDS.