Suryakand's Blog

1. Introduction This is first part of multi-part series where we'll talk about how Lazybones is useful in AEM projects. Starting new project from scratch/base is an exciting task and we want to give our best whenever we are starting something new. We try to pour all our past experiences and learnings together to make sure that we are not doing same mistakes that we have done or found in other projects. Developing large projects goes through various phases: 1) Requirement gathering and analysis 2) Create high level and low level architecture and technical design 3) Choosing frameworks/libraries for development 4) Choosing unit testing frameworks 5) Hooking up build scripts 6) Choosing dependency management tool 7) Defining DevOps strategy 8) Infrastructure – Cloud or In House 9) And many more…. Individual people might have worked on different projects and each of them might have faced different problems and might have learned many best practices. It’s qu

AEM allows us to create content for various channels. In large enterprise ecosystem AEM is central system to deliver content to mobile, web, email, big screens and devices like echo show. Same content can be rendered in different ways and formats and that is a big advantage of AEM. In this article, we are going to look at one specific challenge that becomes very visible when AEM delivers content via email, mobile etc. The challenge is making sure that links embedded in emails and content delivered via email are not broken. There are various ways in which you can fix this problem: Dynamically determine the host URL based on incoming request (sling request and resolver) but, this is not possible in all situations (especially when original request is not originated from a resource/page served by same AEM instance) Create your own OSGi configuration to store AEM instance host domain. This needs to be different for Author and Publisher Hardcoded URLs … a big NO for this Haven’t