For AEM Project development and delivery — we use the Author, Publish, Maven commands and Local Dispatcher setup (Start, Stop etc.)
For Mac Users — we can optimise the process by setting up the Alias for the frequently used commands which will improve the productivity — we will not need to look for the path again and again.
Continue readingAEMaaCS sdk now comes with a docker dispatcher which can be run in a docker container. Setup is straightforward, just follow the below steps.
Continue readingA very common use case is to use multilingual/localised XF’s for header and footer for multilingual site. By default this is how the OOTB template is available in the AEM archetype as well and is the recommended approach to implement header and footer in Touch UI.
Continue readingA very common use case is to use Experience Fragments/XF’s for Header and footer in editable template. In fact this is how the OOTB AEM archetype implements header and footer. However you would very soon notice issues with the caching of XF’s and would need to device a caching strategy. Lets discuss the issues and how to resolve them.
Continue readingWhen dialog is opened the checkbox should be selected by default.
Steps to achieve this in touch ui
Continue readingAEM provides OOTB multi-field in which only one widget/field can be configured as part of the multi-field.
For example, have a look at the OOTB list component
(/libs/foundation/components/list/cq:dialog/content/items/column/items/
setStatic/items/well/items/pages) which only has a single field in a multifield.
In most cases this might not suffice your requirement. You might need a composite multi-field with 2 or more fields as part of the multi-field.
To achieve this there are multiple options. You can choose to go with either of them.