Hi @FlorianGr, Please check this if it helps: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/how-to-add-and-edit-content-fragments-in-universal-editor-ue-for/td-p/748800 https://blogs.perficient.com/2025/04/21/aem-universal-editor-eds-headless-sectionblocks-propertiesrail-...

@RabiiRahmouni  1. Build Pipeline Integration: Monorepo vs. Split Repos for ClientLibs Best Practice: Keep the frontend build tooling co-located within the AEM repo, especially for Content and Experience-Driven projects (like AEM Commerce). Why: Tighter integration with the ui.apps structure (eg. c...

Hi @Mahesh_Gunaje, Install dependencies: npm install --save-dev eslint @typescript-eslint/parser @typescript-eslint/eslint-plugin eslint-plugin-react eslint-plugin-react-hooks eslint-plugin-jsx-a11y Create .eslintrc.js: module.exports = { root: true, parser: '@typescript-eslint/parser', parse...

Hi @elkinomnipro, 1. Use Frontend Build Tools (Webpack/Vite) for Optimization Handle all minification and bundling in your frontend pipeline before deployment: Bundle and minify your CSS and JS during build time. Output to AEM clientlibs: /apps/your-project/clientlibs/site/ ├── css.txt → include...

Hi @ryuushihou1990, You're correct - GraphQL does not support querying Content Fragments from different models in a single GraphQL query out of the box. Here is why? Each Content Fragment Model (CFM) is exposed via its own GraphQL schema endpoint. So when you fetch from: /graphql/endpoint/modelA ......

@nbg621  Yes, it still makes sense. evaluatePathRestrictions: true tells the index to support filtering based on path, such as when your query includes ISDESCENDANTNODE() or ISCHILDNODE(). If you remove includedPaths, it just means your index is now applicable across all content paths - not limite...

Hi @nbg621, Here’s how your index definition should look: { "jcr:primaryType": "oak:QueryIndexDefinition", "compatVersion": 2, "type": "lucene", "async": ["async"], "evaluatePathRestrictions": true, "includedPaths": ["/content/dam/folder1/folder2"], "indexRules": { "nt:base": { ...

Hi @Luca_Moreau, To support locale-specific Experience Fragments without duplicating content manually, follow this best-practice approach using Live Copies: Create a master XF:Author your Experience Fragment at a master location, eg. /content/experience-fragments/site/master/global-banner. Use MSM...

Hi @JelenaS123, Since not all GraphQL queries in AEM rely on JCR-SQL2, you can analyze performance by: Disabling GraphQL caching temporarily via /system/console/configMgr/com.adobe.cq.graphql.persistentcache.impl.GraphqlCacheImpl to measure true response times. Using tools like Postman, GraphQL Pl...

Hi @JelenaS123, I think, some GraphQL queries do not result in JCR-SQL2 executions, especially if the data is retrieved via direct resource access, in-memory resolution, or cached lookups rather than through the JCR query engine. GraphQL resolvers (especially for Content Fragments) can resolve nodes...