This course will teach you how to build and debug Adobe Experience Manager (AEM) packages and how you can use them to import and export content to and from AEM's Java Content Repository (JCR.) Software required: Adobe Experience Manager, Maven.
Adobe Experience Manager (AEM) is regarded as the leading commercial Web Content Manager (WCM.) At the core of becoming an AEM developer is a thorough understanding of AEM's content packages. In this course, Fundamentals of Building from Projects in AEM, you'll learn how to build AEM packages and how they import and export content from AEM's Java Content Repository (JCR.) First, you'll explore the development lifecycle for creating packages for AEM. Next, you'll discover how you can work on content and code in a file system, like your computer, and how we map that content inside the JCR. Finally, you'll learn how to use Maven to generate AEM packages. When you're finished with this course, you'll have a foundational knowledge of AEM packages that will help as you master AEM development. Software required: Adobe Experience Manager, Maven.
Tyler Maynard has been a technology enthusiast since blowing up his parents 486 DX trying to
install a Voodoo 1. In between teaching Node.js at UVU and developing AEM websites you can find
Course Overview Hello everyone. My name is Tyler Maynard and welcome to my course, AEM Fundamentals: Building from Projects in AEM. I am a AEM developer at Zions Bank. Are you new to AEM development and want to understand more about the primary way we can import and export content from Adobe Experience Manager? Or maybe you're like myself: A web developer who one day found themselves working on a AEM project. Well, have no fear, because in this course we will go into depth on how we can create, collaborate, and install projects into Adobe Experience Manager. A few of the topics we will cover include the development life cycle for creating packages for AEM, how we can work on content and code in a file system, like your computer, and how we map that to content inside of AEM's JCR. We'll also talk about how we can use Maven to generate our AEM packages. By the end of this course, you'll be positioned to contribute to AEM projects by developing, building, and installing AEM content packages. Before beginning this course, you should be familiar with using command line interfaces, like the terminal or command prompt, and be aware of what AEM is, but I approach the topic as if you are completely new to AEM. I hope you'll join me through this journey to learn how we develop AEM packages with the AEM Fundamentals: Building From Projects in AEM course here at Pluralsight.
AEM Packages and Vault - Pushing Content into the JCR Welcome back, Pluralsight friends. In this module, we're going to be looking at AEM Packages and Vault, mainly pushing content into the JCR. We'll start this module by looking over an AEM Package, and really help us define what one is. After that, we're going to look at mapping JCR nodes to a file system. This will help us understand how we go from something that we can work with, to something that sits inside the JCR. After that, we're going to talk about importing and exporting content with a tool called Filevault. And finally, we'll talk about AEM's Package Manager, and get our hands on it, so we can see what it does.
Working with AEM in IDEs So far, everything we've been doing is really working from the terminal or the console. With modern development, we're typically using IDEs to assist us and to make our lives a little easier. Now let's talk about working with AEM projects inside of IDEs. Over this module, we're going to be talking about setting up Eclipse and IntelliJ for development. We'll also be talking about running our Maven builds from inside IntelliJ and Eclipse. Then we'll talk about how we can debug our code inside of AEM by opening a port and connecting our IDEs to it. And then finally I'll show you guys some AEM specific plugins that we can use alongside of our IDE development. Whenever we use an IDE for development, we need to do some configuration. Typically we have to load our Maven project into our IDE, and then configure our IDE for our build. When I talk about configuring the IDE, I'm mainly talking about how we can choose the appropriate version of the JDK we want to compile our code with, how to select the appropriate installation of Maven because a lot of IDEs come with Maven built in, and then we also need to configure our run configuration in case we have to activate any profiles.