Job Description :
Job description:
AEM Environment Basics
Basic understanding of why we use a CMS and what problems AEM can solve for the business and for development teams.
Basic knowledge about the AEM Asset Manager (DAM) and what we use it for. The user can navigate to the proper folders and upload new assets.
Understand how content is promoted to publisher as part of the daily release process.
Able to setup up and work with the code cloud repository with GIT using SourceTree for checking in code changes to a project.
Understands how to build and deploy AEM projects using Maven.
Has installed and configured Eclipse with the AEM Plugin. This plugin can be used to develop OSGI bundles, Components, Templates, and Content and integrates with an AEM instance so that all changes can be deployed directly on the AEM server.
Basic AEM Knowledge
Has experience authoring pages in AEM using both the Touch UI and the Classic UI
Knows how to import and export AEM component packages and install them to move code and content updates between AEM environments.
Has a good knowledge of common page component and template.
Can create new templates and page components from scratch.
Understands the file structure and how inheritance works in AEM
Knows how to extend out-of-the-box AEM components.
Can create custom components and dialogs for content implementers to interact with.
Has a good understand of AEM workflows and how they are used to perform specific tasks in a standard way.
Basic understanding of the lifecycle of OSGI Bundles.
Understands how JS and CSS are included on pages in AEM using ClientLibs
Understand Angular/ReactJS dependencies in an AEM component
Install AEM with different run modes (Author and Publish)
Develop OSGI bundles, components and services in AEM to extend the functionality of the basic out of the box tool set to meet specific CMS needs of users
Maintain Configurations stored on AEM server. The user needs to understand where the different configuration files are located and what their purpose is.
Design user dialogs for content implementers to use to maintain content in AEM.
Building a single component having multiple layouts based on configuration settings available to content implementors. This reduces the number of components that must be maintained by allowing a single component to be used in different page designs.
Strong understanding of to organize project content using AEM Launches and how to debug problems with deployment of Launches. Can also resolve merge conflicts between launches.
Understand how to use Handlebars JS to translate Angular/ReactJS variables when mixed with content in AEM. This allows authors to preview content similar to how it will look on a live page.
Complete understanding of build process including the ability to edit and configure packages using the AEM package manager.
Ability to update segmentation rules in AEM to manage personalization of specific content on a page.
Understand how to do a data/content migration from CQ to AEM. This can significantly reduce the development hours needed to migrate projects from CQ 5.x to AEM 6.x.
Maintain pom.xml used by Maven to manage builds and deploys.