The AEM Sites implementation guide is a one stop shop for all your AEM Sites implementation needs. From how to get started to final configurations – our guides aim to help you at every step of your AEM Sites implementation journey. Some handy links below:
1) Discovery and Requirements: A handy checklist that ensures you have all answers from your stakeholders before embarking on an implementation. https://adobe.ly/2sybMsC
2) Architecture: A step-by-step guide to content modeling, application architecture, and Creative/Marketing Cloud integrations. https://adobe.ly/2sybS3s
3) Installation and Provisioning: A guide that details out everything you need to know about installation and provisioning for AEM Sites. https://adobe.ly/2thRfWv
4) Configuration and Implementation: A comprehensive guide to address all your queries on key AEM Sites implementation features. https://adobe.ly/2ti9eMu
5) Administration: A guide to help you through the application administration and system maintenance processes. https://adobe.ly/2siqorY
6) Migration: A guide detailing out content migration and repository migration approaches using OAK tools. https://adobe.ly/2uBZNXo
Hope you find these helpful! Let us know if we can help you in any way!
I am new to AEM and am still learning. I want to implement a search component and have been able to do so with various approaches. Can someone please explain the difference between using a queryBuilder API and not using one for the component? And which approach should be used in what situations?
Also, HTL is used in place of JSP in AEM these days, and I have created the search component using JSP, would it be considered as a bad approach?
I am new to AEM and just begun to understand the logistics of AEM. I would like to know why there was a strong need to switch from JSP to HTL?
It's great to listen that you started learning AEM. HTL has more advantages over JSP like
1) Increased Security
2) Simplified Development
3) Reduced Costs
For Further Reference you can go to this link Overview
I've been working on creating a column control component and been using the following link for reference : Adobe Experience Manager Help | Creating Adobe Experience Manager Custom Column Components. But it seems to work fine in AEM 6.2 and not in AEM 6.3.It would be great if someone could help me with the issue.
AEM project structure can be created using Lazybones or Maven Archetype. Eclipse IDE or Intellij IDEA can be used as the environment for working on the backend. The following links has the steps to create the project structure.
It depends on which IDE you are comfortable working with. Personally I feel that IDEA feels context. IDEA indexes the whole your project, analyses everything it has, and even builds the syntax tree. Thanks to it, at any time, wherever you put the cursor, IDEA knows where you are and what can be done there.
While loading sling model, I get an error that says "Cannot find the sling model in the repository". Can someone please help me resolve the issue.
This is a very common error. To resolve this, under the core of the project in the pom.xml check and modify the <Sling-model-Packages> under the maven-plugin. If the package is not same as the package used then this error occurs. Hope this helps!
Hi, I was under a project which included multifield values involving sling model, could anyone help me in displaying those values on the page after entering those values in dialog .
When you are overriding OOTB Text Component all default plugins will be added, in order to disable any of default plugins overlay OOTB Text component cq:dialog in your component add that plugin under rtePlugins node which you want to disable and add features property to it and leave the value as empty to disable plugin. Here is a link which u can go through Configuring the Rich Text Editor
I want to use an out of the box component with a dialog box, but I want the dialog box to be disabled (ie., shouldnt pop up when clicked). Can someone help me with this?
We can disable the dialog box though we are inheriting from OOTB Component for that we use some properties in Sling Resource Merger Concept Using the Sling Resource Merger in AEM here is the link where you can refer to. So you need to add a property sling:hideResource with true as its value under the cq:dialog node in your overriding component. I hope this works....