• Onboarding content authors to a new project
• Training content managers
• Project handover to client authoring team
• Creating author-focused documentation

allGuides

cd

ALL_GUIDES=$(cat .claude-plugin/project-config.json 2>/dev/null | grep -o '"allGuides"[[:space:]]*:[[:space:]]*true')
if [ -z "$ALL_GUIDES" ]; then
  # Navigate to git project root (works from any subdirectory)
  cd "$(git rev-parse --show-toplevel)"
  # Verify it's an Edge Delivery Services project
  ls scripts/aem.js
fi

• You MUST run the

  cd

  command above using the Bash tool
• All subsequent steps operate from project root
• Do NOT use absolute paths to verify — actually navigate
• Guides will be created at

  project-root/project-guides/

scripts/aem.js

"This skill is designed for AEM Edge Delivery Services projects. The current directory does not appear to be an Edge Delivery Services project (

scripts/aem.js

not found).

Please navigate to an Edge Delivery Services project and try again."

• NEVER use "EDS" as an acronym for Edge Delivery Services in any generated documentation or chat responses
• Always use the full name "Edge Delivery Services" or "AEM Edge Delivery Services"
• This applies to all output files (PDF, HTML, markdown) and all communication with the user

project-guides/AUTHOR-GUIDE.md

1. First, create the directory:

   mkdir -p project-guides

2. Then write to:

   project-guides/AUTHOR-GUIDE.md

project-guides/

AUTHOR-GUIDE.md

docs/AUTHOR-GUIDE.md

/workspace/AUTHOR-GUIDE.md

project-guides/AUTHOR-GUIDE.md

project-guides/AUTHOR-GUIDE.pdf

• ❌ Do NOT read or analyze

  fstab.yaml

  — it does NOT exist in most projects and does NOT show all sites
• ❌ Do NOT create

  .plain.html

  files
• ❌ Do NOT use

  convert_markdown_to_html

  tool — this converts the FULL guide to HTML with raw frontmatter visible, which is NOT what we want
• ❌ Do NOT tell user to "convert markdown to PDF manually"
• ❌ Do NOT save markdown to root directory or any path other than

  project-guides/

• ❌ Do NOT say "PDF will be generated later" or "at session end" — generate it NOW

1. Run

   mkdir -p project-guides

   to ensure directory exists
2. Generate markdown content with YAML frontmatter (title, date)
3. Save to

   project-guides/AUTHOR-GUIDE.md

   (EXACT PATH - no exceptions)
4. IMMEDIATELY invoke PDF conversion (see Phase 5.2)
5. Clean up all source files (only PDF remains)
6. Final output:

   project-guides/AUTHOR-GUIDE.pdf

"What is your Config Service organization name? This is the

{org}

part of your Edge Delivery Services URLs (e.g.,

https://main--site--{org}.aem.page

). The org name may differ from your GitHub organization."

• DO NOT use

  AskUserQuestion

  with predefined options — ask as a plain text question
• Organization name is MANDATORY — do not offer a "skip" option
• Wait for user to type the org name before proceeding
• If user doesn't provide a valid org name, ask again

• Analyzing

  fstab.yaml

  — does NOT show all sites in repoless setups
• Reading

  README.md

  — may be outdated or incomplete
• Inferring from codebase structure — misses CDN configs and additional sites
• Using git remote URLs — org name may differ from Config Service org
• Making assumptions based on project folder names

ORG=$(cat .claude-plugin/project-config.json | grep -o '"org"[[:space:]]*:[[:space:]]*"[^"]*"' | sed 's/"org"[[:space:]]*:[[:space:]]*"//' | sed 's/"$//')

**📁 REQUIRED ARTIFACT:** `.claude-plugin/sites-config.json`

**API Reference:** https://www.aem.live/docs/admin.html#tag/siteConfig/operation/getConfigSites

---

The response is a JSON object with a `sites` array (each entry has a `name` field). Extract site names and construct per-site URLs:
- **Preview:** `https://main--{site-name}--{org}.aem.page/`
- **Live:** `https://main--{site-name}--{org}.aem.live/`

Multiple sites = **repoless** setup. Single site = **standard** setup.

**Then fetch individual site config for code and content details:**

```bash
AUTH_TOKEN=$(cat .claude-plugin/project-config.json | grep -o '"authToken"[[:space:]]*:[[:space:]]*"[^"]*"' | sed 's/"authToken"[[:space:]]*:[[:space:]]*"//' | sed 's/"$//')
curl -s -H "x-auth-token: ${AUTH_TOKEN}" "https://admin.hlx.page/config/${ORG}/sites/{site-name}.json"

{
  "code": {
    "owner": "github-owner",
    "repo": "repo-name",
    "source": { "type": "github", "url": "https://github.com/owner/repo" }
  },
  "content": {
    "source": {
      "url": "https://content.da.live/org-name/site-name/",
      "type": "markup"
    },
    "contentBusId": "..."
  }
}

• code.owner

  /

  code.repo

  — GitHub repository

• content.source.url

  — Content mountpath (e.g.,

  https://content.da.live/org/site/

  )

• content.source.type

  — Content source type (markup, onedrive, google)

• DA URL:

  https://da.live/#/{org}/{site}/

  (derived from

  content.source.url

  )
• Block Library:

  https://da.live/#/{org}/{site}/.da/library

fstab.yaml

• DA access (request from admin)
• Preview/publish permissions

1. Go to DA: [link]
2. Navigate to the correct folder
3. Create new document
4. Use blocks from Library sidebar
5. Add Metadata block at bottom
6. Preview → Publish

1. Save markdown to:

   project-guides/AUTHOR-GUIDE.md

   • File MUST start with YAML frontmatter:
     yaml

     ---
     title: "[Project Name] - Author Guide"
     date: "[Full Date - e.g., February 17, 2026]"
     ---

   • Date format: Always use full date with day, month, and year (e.g., "February 17, 2026"), NOT just month and year
2. IMMEDIATELY after saving the markdown, invoke the PDF conversion skill:

   Skill({ skill: "project-management:whitepaper", args: "project-guides/AUTHOR-GUIDE.md project-guides/AUTHOR-GUIDE.pdf" })

3. Wait for PDF generation to complete (whitepaper skill auto-cleans source files)

• Skip the PDF conversion step
• Tell user "PDF will be generated later" — generate it NOW

• Config Service API was called (

  https://admin.hlx.page/config/{ORG}/sites.json

  )
• Site list came from API response, NOT from fstab.yaml or codebase analysis
• DA/Block Library URLs derived from Config Service content source, NOT assumed from code.owner/repo

• Quick Reference table with all project URLs
• All blocks documented in table format
• All templates documented with required metadata
• Configuration sheets documented
• Publishing workflow explained
• Common tasks documented
• Section/page metadata options listed
• Troubleshooting included

• PDF generated successfully
• All source files cleaned up (only PDF remains)

1. Use tables for compact reference information
2. Keep language simple - avoid technical jargon
3. Use examples from actual project content
4. Test procedures before documenting them