AEM Learning Repository

In the process of debugging performance issues, we need to narrow down the load time of the page and hence the individual component/requests part of the page. Below are the few ways of finding out the same.  From Browser : The very first place where we look for the page load time is our browser's Developer tools->Network Tab  which will display the time taken for each of the requests that are part of the page. AEM Component load time: We have an OOB feature on the AEM Sites page to find out the load time of a component.  Open AEM Site Page in editor mode(with /editor.html) -> Switch to Developer mode from Edit mode -> Left rail in content finder area -> Components section -> Components available as part of the page will be displayed with the time taken. request.log:   request.log file available in ../crx-quickstart/logs folder will have a trace of each and every request and its duration.  There exist a Request Log Analyzer available OOB i

For reusing content, we have two great implementations available in AEM - Experience Fragments(XF) and Content Fragments(CF). It is important to understand the differences between the two which will help us arrive at when to use what based on our project/content set up.  Experience Fragments Content Fragments Composed of one or more AEM components Composed of structured/form-based data elements The content part of XF is any  AEM components  as such - Text, Image or any custom component part of our project. ie. Presentation-centric  The content part of CF is  text/image content  in the form of direct text type/RTE/Date type/Dropdown/Reference type for referencing any asset ie. Content-centric Created using Editable templates , implemented/treated as an AEM Page Created using Content Fragment Model , implemented/treated as an AEM Asset List of allowed components in XF can be controlled via policies in Editable templates Content in CF can be configured as di