Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Evolve18 | Satish Ramade | The case for Self balanced AEM

74 views

Published on

The case for Self balanced AEM:
- Content QA in AEM Production Author is not adequate and not the same as production live site.
- Things like personalization, vanity URLs, clunky interface, not true Publish look and feel, etc are the problems with Author. * To prevent Authors posting changes to live site, separation of duties, notifications, etc can be implemented with ACLs and workflows but problematic in many cases.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Evolve18 | Satish Ramade | The case for Self balanced AEM

  1. 1. #evolve18 THE CASE FOR THE SELF-BALANCED AEM Satish Ramade Agile Zone Friday Aug 17, 2018
  2. 2. #evolve18 2 • Best in the industry for content authoring and publishing • Almost magical integration with assets and Adobe Creative Cloud products • Personalization possibilities right within AEM • Adobe Marketing Cloud products seamless integration • Architectural solutions at the topology level to support insane amount of contents • Flexible integration with eCommerce engines and components • AND MANY MANY MORE…… AEM STRENGTHS
  3. 3. #evolve18 3 The focus of this hour is • Highlight the absence of robust content review and quality assurance (QA) functionality and find the possible solutions AEM WEAKNESS
  4. 4. #evolve18 4 • If only I had a better way to test the content outside AEM Author before the content goes live... • I am tired of my content going LIVE by mistake and without approval... • I just wish I could test my site in PRODUCTION before it goes LIVE... • I wish I could make testing my site simpler in terms of the cost and process... • I wish I did not have to move the content between environments before making it public… CAN YOU IDENTIFY WITH THESE FRUSTRATIONS?
  5. 5. #evolve18 5 • AEM Authoring Interface is not a true end user LIVE-like interface to test the quality of my content and approver can approve them. • Content creation is in production LIVE environment -- Authors can potentially post changes to live site, without approval process. • Personalization does not work in authoring interface • Third-party integration is not available in Author server preview • Typically, vanity URLs are not used in authoring interface • Lack of clean support for the functional Approach to Content WHAT IS THE PROBLEM?
  6. 6. #evolve18 6 IT FEELS LIKE THIS!
  7. 7. #evolve18 7 I HOPE TO SEE THIS!
  8. 8. #evolve18 8 THE CASE FOR THE SELF-BALANCED AEM CONTENT REVIEW AND QUALITY ASSURANCE (QA)
  9. 9. #evolve18 9 • Treating code and content same create lot of complexity • This won’t work (or the least very difficult and slow) as the content repository size is getting bigger. • Infrastructure cost amounts to the times # of environments. • Content deployment process gets very complicated since it requires reference changes APPROACHES BOTTOM-UP APPROACH PROD PERF QA INT DEV Code & Content
  10. 10. #evolve18 10 • Introducing a dedicated production content QA stack can entail great hardware and support costs. • Content deployment process gets very complicated since it requires reference changes • This won’t work (or the least very difficult and slow) as the content repository size is getting bigger. APPROACHES SIDE-WAY APPROACH
  11. 11. #evolve18 11 • Publish to LIVE server is intercepted by workflow • Workflow triggers on content add/update to send the request for approval • Author preview mode is to QA and review the contents. • Workflow based solution gets impossible in most cases due to processing overhead on the Author and Publish servers • Testing production contents in Author server brings the Author server’s inherent issues like author interface, vanity URLs, personalization, etc. APPROACHES WORKFLOWS & PERMISSIONS
  12. 12. #evolve18 12 THE CASE FOR THE SELF-BALANCED AEM CONTENT REVIEW AND QUALITY ASSURANCE (QA) LETS TALK ABOUT THE BALANCE – THE SOLUTION
  13. 13. #evolve18 13 • Provides a true end-user LIVE environment for content QA and review - the same codebase, third-party integration, vanity URLs and personalization • A Functional Approach to Content Management - Author creates content, Approvers approves it and Publisher publishes content to make it LIVE. • Delivers the CMS separation of duties one would expect, distinguishing between Author, Approver, and Publisher functions. Must be flexible as well to combine these roles. • It should not add extra overhead in terms of cost and processes • Does not add additional processing load on the AEM author server THE SOLUTION
  14. 14. #evolve18 14 THE SOLUTION
  15. 15. #evolve18 15 THE SOLUTION
  16. 16. #evolve18 16 THE BALANCE
  17. 17. #evolve18 17 • A lightweight, non-intrusive AEM add-on with a small footprint that offers powerful functionality • The only off the self addon available in the market to address the content QA and review problem • Works within the AEM design and infrastructure without adding overhead or modifying the codebase • It leverages one of the existing or new production publish servers as content QA server • Provides enhanced interface for author and new UI for approver and publisher THE SOLUTION AGILE ZONE CONTENTQA
  18. 18. #evolve18 18 THE SOLUTION AGILE ZONE CONTENTQA
  19. 19. #evolve18 19 ABOUT US LinkedIn linkedin.com/in/satishramade Satish Ramade Title Technologist Contact Us www.agilezone.com Mail satish.ramade@agilezone.com Phone (248) 470-4862
  20. 20. #evolve18 THANK YOU!

×