Posts

Featured Post

Understanding Adobe I/O with AEM

Image
Audience : Adobe Architects, Developers Read time : 10 minutes  Let us consider a typical enterprise level digital marketing eco-system containing Adobe solutions. Consider some typical BAU scenarios in such enterprise eco-system. Second party and third party providers might want to upload data to AAM on regular basis Native android/IOS application wants to access personalized offers from target and target in-turn gets its content from AEM. AEM author wants to push email templates to campaign and offers to target A custom visualization in tableau needs data in a certain format that combines analytics data and campaign success rate from target. Send WhatsApp and email notification to subscribers when a new page is created in microsite built on AEM. In this big eco-system of applications, security, scalability, performance with which they talk with each other plays a very important role. With the ever-expanding Adobe’s cloud suite of products, there is always a need for one-stop solution

AEM SPA Editor Demystified

Image
Intended audience : CMS Developers, Architects.   Pre-requisites : Basics of SPA (Single Page Application).   It's been a while since Adobe released AEM SPA editor. The support was added officially in SP3 for 6.4. A detailed explanation on how this functionality works is provided by Adobe  here . Hence, I will not go into the "How to...” part in this blog. Also, I will not be going into the "SPA" part of it as there are a huge number of blogs and tutorials dedicated to the topic. Instead, I will try to answer some abstract questions (which I had and couldn’t get an answer elsewhere) like:     Why is SPA editor needed at all? What problems is it trying to solve?  And how is it solving those  problems?   As the name "SPA Editor" suggests, does it just give just editing functionality for Single Page Applications? Was it not there in the first place? What's new here?   Should I use it in my application? If yes, how?   I don’