One-click install
npx skills add https://github.com/Focus-GTS/eds-content-ops-skills --skill content-migration-focus-gts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: content-migration
Source: https://github.com/Focus-GTS/eds-content-ops-skills/tree/main/skills/content-migration
Command: npx skills add https://github.com/Focus-GTS/eds-content-ops-skills --skill content-migration-focus-gts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bulk content migration from a traditional CMS to AEM Edge Delivery Services (EDS) is hard because EDS is document-based, so teams must redesign content structure, templates, and query indexing while preserving metadata and SEO.

Core Features & Use Cases

  • Source-to-EDS mapping: Analyzes representative pages from AEM, WordPress, Drupal, or other CMSs and maps content types and fields to EDS document conventions (sections, blocks, metadata tables).
  • Template and schema generation: Produces complete EDS document templates and a metadata schema aligned to what authors and listing/query views need.
  • Query index configuration: Generates helix-query.yaml rules so listings and search can index migrated metadata reliably.
  • Migration execution paths: Provides both manual workflows (small migrations) and scripted workflows (large migrations) including extract/transform/import/validate.
  • Post-migration validation: Outputs an EDS-specific validation checklist using .plain.html to confirm document rendering and head metadata correctness.

Quick Start

Ask an AI agent to plan an 8-step migration by analyzing 5–10 representative source pages, generating the EDS templates and helix-query.yaml, and producing step-by-step author instructions for bulk importing.

Frequently Asked Questions about content-migration

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

FAQPage Schema
How do I migrate content from WordPress to AEM Edge Delivery Services?

Migrating WordPress content to AEM Edge Delivery Services requires mapping source content types to EDS document sections, blocks, and metadata tables, then executing scripted or manual workflows to extract, transform, and import data.

What is the best way to structure document templates for AEM EDS migration?

Structuring document templates for AEM EDS migration involves analyzing representative source pages to generate EDS document conventions, including sections, blocks, and metadata tables that align with authoring and query view requirements.

How do I configure helix-query.yaml for migrated metadata in EDS?

Configuring helix-query.yaml for migrated metadata requires generating query indexing rules that map metadata schema fields so EDS listings and search can reliably index and retrieve the migrated content.

Can I use bulk automation scripts to move Drupal content into EDS?

Yes, you can use bulk automation scripts to move Drupal content into EDS by applying scripted extract, transform, import, and validate workflows designed for large-scale migrations from traditional CMS platforms.

How do I validate AEM Edge Delivery Services content after migration?

Validating AEM Edge Delivery Services content after migration involves running a post-migration checklist using the .plain.html suffix to confirm document rendering and head metadata correctness aligned to EDS conventions.

What metadata schema design is needed for AEM EDS document-based authoring?

Metadata schema design for AEM EDS document-based authoring requires defining metadata tables that map source CMS fields to EDS conventions, ensuring authors and listing views have the structured data needed for indexing.