Justin Edelson's guest appearances

Justin Edelson

Adobe Experience Manager Podcast

David Gonzalez

Jason Meyer

Cedric Huesler

Anton Zuponcic

Dan Klco

Brett Birschbach

OwlTail

One of our last interviews at Adobe Summit 2017 was with our friend Justin Edelson (current Team Lead, Engineering Response Team at Adobe).  He took some time to discuss a couple of topics with Joey and I.  This is part 2 of that conversation (part 1 here).  This week’s podcast will focus on ACS AEM Commons.  As we have discussed before, ACS AEM Commons is a great resource for any Adobe Experience Manager implementation.  It saves both time and money.  Of course you already know that, right?  RIGHT?!  In this podcast, we talk about where ACS AEM Commons is going next.  The big question is how they can broaden the contributor base.  They want to have a greater amount of submissions and pull requests coming from the customer and implementation partner development groups working with AEM, instead of specifically from Adobe Consulting Services.  If you have ideas, then feel free to reach out to David Gonzales and Justin Edelson to share them.  

<p>One of our last interviews at Adobe Summit 2017 was with our friend <a href="http://aempodcast.com/tag/justin-edelson/" rel="nofollow" target="_blank">Justin Edelson</a> (<a href="https://www.linkedin.com/in/justinedelson" rel="nofollow" target="_blank">current Team Lead, Engineering Response Team at Adobe</a>).  He took some time to discuss a couple of topics with Joey and I.  This is part 2 of that conversation (<a href="http://aempodcast.com/2017/podcast/aem-podcast-adobe-summit-interview-justin-edelson-core-components/" rel="nofollow" target="_blank">part 1 here</a>).  This week’s podcast will focus on <a href="https://adobe-consulting-services.github.io/acs-aem-commons/" rel="nofollow" target="_blank">ACS AEM Commons</a>.  As we have discussed before, ACS AEM Commons is a great resource for any Adobe Experience Manager implementation.  It saves both time and money.  Of course you already know that, right?  RIGHT?!  In this podcast, we talk about where ACS AEM Commons is going next.  The big question is how they can broaden the contributor base.  They want to have a greater amount of submissions and pull requests coming from the customer and implementation partner development groups working with AEM, instead of specifically from Adobe Consulting Services.  If you have ideas, then feel free to reach out to <a href="https://twitter.com/unicornless" rel="nofollow" target="_blank">David Gonzales</a> and <a href="https://twitter.com/justinedelson" rel="nofollow" target="_blank">Justin Edelson</a> to share them.  </p>

AEM Podcast: Adobe Summit Interview with Justin Edelson about ACS AEM Commons

One of our last interviews at Adobe Summit 2017 was with our friend Justin Edelson (current Team Lead, Engineering Response Team at Adobe).  He took some time to discuss a couple of topics with Joey and I.  This is part 1 of that conversation.  This week’s podcast will focus on Core Components.  This is Adobe’s new method for handling the default set of components that come with Adobe Experience Manager.  At Summit Justin also led a lab discussing how to work with the new Core Components.  While the lab was not recorded, for obvious reasons, the booklet that was used in it is available for download here(Adobe Summit 2017 Core Components lab booklet).  Join us for a discussion with one of the leading Adobe development minds behind Adobe Experience Manager as we talk about AEM’s Core Components and how they went about their methods and reasoning for setting it up the way they have.  Part of the discussion was also the demise of the Classic UI, because these Core Components are only for the Touch UI.  At the time it was not known what would happen, but as I have written about before in my article “Bye Bye Classic UI”, we have a better idea of its end of life.  Take a listen!

<p>One of our last interviews at Adobe Summit 2017 was with our friend <a href="http://aempodcast.com/tag/justin-edelson/" rel="nofollow" target="_blank">Justin Edelson</a> (<a href="https://www.linkedin.com/in/justinedelson" rel="nofollow" target="_blank">current Team Lead, Engineering Response Team at Adobe</a>).  He took some time to discuss a couple of topics with Joey and I.  This is part 1 of that conversation.  This week’s podcast will focus on <a href="http://aempodcast.com/tag/core-components/" rel="nofollow" target="_blank">Core Components</a>.  This is Adobe’s new method for handling the default set of components that come with Adobe Experience Manager.  At Summit Justin also led a lab discussing how to work with the new Core Components.  While the lab was not recorded, for obvious reasons, the booklet that was used in it is available for download here(<a href="http://aempodcast.com/wp-content/uploads/2017/07/L4205-workbook.pdf" rel="nofollow" target="_blank">Adobe Summit 2017 Core Components lab booklet</a>).  Join us for a discussion with one of the leading Adobe development minds behind Adobe Experience Manager as we talk about <a href="https://github.com/Adobe-Marketing-Cloud/aem-core-wcm-components" rel="nofollow" target="_blank">AEM’s Core Components</a> and how they went about their methods and reasoning for setting it up the way they have.  Part of the discussion was also the demise of the Classic UI, because these Core Components are only for the Touch UI.  At the time it was not known what would happen, but as I have written about before in my article “<a href="http://aempodcast.com/2017/community-news/bye-bye-classic-ui/" rel="nofollow" target="_blank">Bye Bye Classic UI</a>”, we have a better idea of its end of life.  Take a listen!</p>