Enonic Guillotine Query Builder

Procedures

Step 1: Scan the workspace for existing Guillotine usage

1. Execute node scripts/find-guillotine-targets.mjs . to inventory files containing Guillotine markers (query strings, library imports, endpoint references).
2. If a Node runtime is unavailable, search the workspace manually for guillotine, queryDsl, queryDslConnection, or /lib/guillotine in .ts, .js, .graphql, and .gql files.
3. Note the Guillotine version in use: if query(query: "...") string-based fields are found, the project uses the deprecated 5.x-style API; if queryDsl / queryDslConnection are found, the project uses 6.x+ DSL. Check for exports.extensions in guillotine/guillotine.js to detect Guillotine 7 Extensions API usage.
4. If both styles coexist, flag the deprecated usage for migration.

Step 2: Load the Guillotine API reference

1. Read references/guillotine-reference.md before composing any query.
2. Read references/compatibility.md when the workspace targets or migrates between Guillotine versions.

Step 3: Determine the query shape

1. Identify the operation the user needs:
   • Single content fetch: Use get(key).
   • Direct children: Use getChildren(key) or getChildrenConnection(key) for pagination.
   • Filtered search: Use queryDsl(query) for a flat list or queryDslConnection(query) for pagination, aggregations, or highlighting.