create-site

Automate end-to-end AEM Edge Delivery site onboarding from GitHub repo creation to live preview.

1|Updated Oct 7, 2024
One-click install
npx skills add https://github.com/valithedge/etisalatedge --skill create-site-valithedge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-site
Source: https://github.com/valithedge/etisalatedge/tree/main/.agents/skills/create-site
Command: npx skills add https://github.com/valithedge/etisalatedge --skill create-site-valithedge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines the end-to-end onboarding of a new AEM Edge Delivery site, handling repository setup, DA content provisioning, and live preview wiring.

Core Features & Use Cases

  • Automates GitHub repository creation from the Adobe boilerplate for new EDS projects.
  • Provisions initial DA content (nav.html, footer.html, index.html) and connects AEM Code Sync for deployment.
  • Triggers and validates a live preview URL and preps handoff details for the user.

Quick Start

Provide the required inputs (GitHub org, repo name, and site name) to initialize the end-to-end AEM Edge Delivery site.

Frequently Asked Questions about create-site

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

FAQPage Schema
How do I automate AEM Edge Delivery site onboarding from scratch?

You can automate the complete AEM Edge Delivery site onboarding by orchestrating GitHub repo creation, AEM Code Sync installation, DA token management, and live preview activation. You only need to provide your GitHub org, repo name, and site name.

What initial DA content is provisioned for a new AEM Edge Delivery site?

Initial DA content provisioning generates nav.html, footer.html, and index.html files to establish core site structure. This step connects AEM Code Sync for deployment to your newly created GitHub repository.

Do I need an existing GitHub repository to set up an AEM Edge Delivery preview?

No existing GitHub repository is needed to set up an AEM Edge Delivery preview. The automation creates the repository from the Adobe boilerplate, installs aem-code-sync, and triggers the live preview URL validation.

What inputs are required to initialize an end-to-end AEM EDS project?

To initialize an end-to-end AEM EDS project, you must provide your GitHub organization, target repository name, and site name. These inputs drive automated repository creation, DA token management, and preview activation.

Can I use this automation if I already have an AEM Code Sync installation?

This automation applies when no repository or data already exists. If you already have an AEM Code Sync installation or an existing repository, this end-to-end onboarding flow is not the best fit for your workflow.