Enonic Content Management

Procedures

Step 1: Identify the Enonic XP project and operation scope

1. Inspect the workspace for Enonic XP project markers: build.gradle with com.enonic.xp dependencies, src/main/resources/ directory structure, or gradle.properties with xpVersion.
2. Execute node scripts/find-enonic-targets.mjs . to scan for Enonic XP project markers and existing content operation files when a Node runtime is available.
3. If no Enonic XP project is detected, stop and explain that this skill targets Enonic XP content operations only.
4. Determine the target XP version from gradle.properties or build.gradle to select the correct API surface.
5. Classify the requested operation:
   • Bulk create: Importing content from external sources (JSON, CSV, APIs).
   • Bulk update: Modifying existing content matching query criteria.
   • Bulk delete: Removing content matching query criteria.
   • Migration: Moving or transforming content between paths, sites, or environments.
   • Query/Aggregation: Retrieving and analyzing content with NoQL and aggregations.
   • Long-running task: Any operation processing more than ~100 items that needs progress reporting.