@agyawa , I see. true. But see if my way of packaging can help you. Above jenkins job packages at root page. Our production package definition is /content/mysite; /conf/mysite; /content/dam/content-fragments/mysiteWe build all non-asset content from productiondownload, install and publish full packa...

Hi @SarahBo2 , no, users need not have premium account. So on load of component, the SDK would be loaded with an auth token. The auth token is generated using an enterprise service account. So auth generation service must run at serverside protected. The token is loaded on browser and should run SDK...

Please refer to my answer in AEM community https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/adobe-events-tracking-trough-spotify-iframe/m-p/741042/highlight/true#M181892 Please reply if any issues faced. 

Ah. sounds then it becomes 2 step process. Jenkins to package and downsync into authorBulk Tree activation with `onlyActivated` filter Please refer to this article by Tad Reeves. So AEM introduced this newer `TreeActivation` process step that is resilient. Say 50,000 pages are to be published. We se...

Yes, you must create an embeddable under the wcmcore embed component. 2 ways to embed spotify sdk: 1) Create embeddable to load iframe ; 2) Create as custom component for additional features functionalities.  Embeddable:Step 1: Create spotify embeddable component. Under /apps/project/components/cont...

Echoing konstantyn reply, Content Copy tool has its limitationsInstead, we have a jenkins job that runs every saturday 1AM. It rebuilds content package in production, downloads to jenkins server, uploads into dev env author; installs; replicatesThis is build step command inside the job echo "#######...

thanks. actually its same as adobe documentation.  Seems there are 2 documentations to configure cdn.yaml. I followed second document. But missed to mark the /config folder in pipeline which was explained in first documentation. https://experienceleague.adobe.com/en/docs/experience-manager-learn/clo...

1 more worthy attempt might be to demote Node to 20. Do cache clean nvm use 20delete `rm -rf node_modules`delete `rm package-lock.json`clear cache `npm cache clean --force`then `npm install`and retry

Got it. its obvious, your author is NOT fronted with Dispatcher. But publisher, by default is fronted with dispatcher. Traffic has to pass dispatcher to reach publisher, and in your case, traffic got snapped at dispatcher itself before hitting publisher.  Now dont remove this rule as it might be int...

is this 'mem-fs' dependency, part of your code? is it in your package.json or just loaded by some dependency? coz 2 months back same issue was reported and suggested to move the dependency to peer dependency.https://github.com/yeoman/yo/issues/803#issuecomment-2552635393  worth a try if you are only...