Adobe's new Universal Editor is built for editing content no matter which type of frontend application is used. It is completely decoupled from AEM but integrates nicely with it. We've seen it work well with Edge Delivery Services, but is it also a good fit for frontends built with React/Next.js, An...

As I've been working with AEMaaCS since its early days, the OOTB Adobe-managed Fastly CDN option used to be very limited for customization. Therefore, we've seen many enterprise customers deciding on the bring-your-own CDN option to accommodate specific requirements. This option is still valid, but ...

We've seen websites running on Adobe Edge Delivery Services (EDS) achieving record Lighthouse scores for performance. But, what is the secret behind Adobe's approach towards such great front-end performance? What is the technology behind it and what are the consequences of implementing it on your we...

Hi @pratikshah,to achieve this you will need to create custom configuration for your different DEV environments and set DEV/QA/INT as environment variable. For example, your configuration might look like this:{ "instanceEnvironment": "$[env:INSTANCE_ENVIRONMENT;default=dev]", "instanceType": "au...

Hi @Mario248,in AEMaaCS I would not recommend creating content in lower-level environments and then pushing it to Production. A better strategy is to setup content directly in Production Author. Now obviosuly content should not go live before its properly tested on publish. You can achieve this on P...

Thank you both, I was able to figure out from the examples you shared that this JSON configuration can be loaded in a script of a specific type. For example in Next it would be: <Script id="aio-group-definitions" type="application/vnd.adobe.aue.model+json" ...

Hello, I am doing a POC with Next.js and Universal Editor and I see Adobe has recently publish documentation on Model Definitions & Component Types: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/developing/universal-editor/field-types.As I am not 10...

Here is a bash script I use on Mac to fix all symlinks in case they got broken by pulls from Git:  project_root=$(pwd) cd dispatcher/src/conf.d/enabled_vhosts enabled_hosts=$(ls *.vhost) for host in $enabled_hosts; do rm $host ln -s ../available_vhosts/$host $host done cd $project_root cd dispatc...

Agree with the suggestion previous colleagues have provided.For me, on MacBook, symlinks sometimes get broken after checkout from Git.Here is a bash script to recreate all symlinks. Hope it helps.  project_root=$(pwd) cd dispatcher/src/conf.d/enabled_vhosts enabled_hosts=$(ls *.vhost) for host in $e...