The AEM CIF Core Components project serves as accelerator to get started with projects using AEM, CIF and Magento. The project contains re-useable Commerce core components which combine server-side rendered AEM components with client-side React commerce components (MPA) for dynamic experiences / data. The components use the Venia theme1.
This project is intended to be used in conjunction with the AEM Sites Core Components. AEM CIF Core Components use the AEM Sites Core Components as a foundation where possible and extending them.
For starting a new project please have a look at our archetype project. Also have a look at our Venia sample project that uses the WCM and CIF core components to deliver a stunning store-front experience.
See our wiki for usage and configuration instructions of the AEM CIF Core Components.
The latest version of the AEM CIF Core Components, require the below minimum system requirements:
|CIF Core Components||AEM as a Cloud Service||AEM 6.5||AEM 6.4||Magento||Java|
|2.2.0||Continual||6.5.7||-||2.4.2 ee||8, 11|
For a list of requirements for previous versions, see Historical System Requirements.
For AEM as a Cloud Service deployments this project requires the CIF Add-On provisioned on each AEM as a Cloud Service environment. The CIF Add-On is installed automatically, no extra deployment is needed. The CIF Add-On is also available for local development with AEM SDK from Software Distribution portal.
For AEM on-prem installations, this project requires the AEM Commerce Add-On for AEM 6.5 to improve the authoring experience by leveraging the product pickers, product assets view, and product consoles provided by the connector package. The AEM Commerce Add-On for AEM 6.5 is also available on the Software Distribution portal. It must be installed separately.
This project relies on the AEM Sites Core Components. They are typically installed as part of AEM. If you install AEM without sample content option you have to deploy them manually before using the AEM CIF Core Components.
Starting with 2.3.2, Magento supports cache-able GraphQL requests and starting with version 0.2.1 the CIF core components will use it by default. To make the components work with Magento 2.3.1 you can manually disable this feature in the following locations:
mvn clean installin the root folder to install the artifacts to your local Maven repository.
allproject and run a
mvn clean install content-package:install.
Here is a full video walk-through of the setup process.
If you want to build all the modules yourself and get all the latest (yet) unreleased changes, just build and install all the modules with the following command at the root of the repository:
mvn clean install -PautoInstallAll
This installs everything by default to
localhost:4502 without any context path. You can also configure the install location with the following maven properties:
aem.host: the name of the AEM instance
aem.port: the port number of the AEM instance
aem.contextPath: the context path of your AEM instance (if not
This project relies on the AEM 6.4.4
cq-quickstart UberJar. This is publicly available on https://repo.adobe.com
For more details about the UberJar please head over to the How to Build AEM Projects using Apache Maven documentation page.
The released version of the AEM CIF Core Components are available on the maven central repository. To include the AEM CIF Core Components package into your own project maven build you can add the dependency
<dependency> <groupId>com.adobe.commerce.cif</groupId> <artifactId>core-cif-components-all</artifactId> <type>zip</type> <version>x.y.z</version> </dependency>
and sub package section
<subPackage> <groupId>com.adobe.commerce.cif</groupId> <artifactId>core-cif-components-all</artifactId> <filter>true</filter> </subPackage>
You also need to add the AEM Commerce connector for Magento all package, see above. Make sure you add that as a dependency as well.
To connect the AEM CIF Core Components with your Magento instance follow the configuration steps. For a multi store / site setup one additional step is needed to link an AEM site to a Magento store view.
For customizing CIF Core Components, we provide use cases and examples in our documentation at Customizing CIF Core Components.
cd ui.apps npm install npm test
Karma will test with Chrome and Firefox. Make sure you have both browsers installed.
You can find the code formatting rules in the
eclipse-formatter.xml file. The code formatting is automatically checked for each build. To automatically format your code, please run:
mvn clean install -Pformat-code
npm test in the
ui.apps project. To automatically format your code, please run the following command in
npm run prettier:fix
webpack to build our clientlibs. Please read Packing Clientlibs with Webpack for more information.
Releases of this project are triggered by manually running
mvn release:prepare release:clean on the
master branch on the root folder of this repository. Once you choose the release and the next snapshot versions, this commits the change along with a release git tag like for example
core-cif-components-reactor-x.y.z. Note that the commits are not automatically pushed to the git repository, so you have some time to check your changes and then manually push them. The push then triggers a dedicated
CircleCI build that performs the deployment of the tagged artifact to Maven Central.
Important: this project does Maven reactor releases, do not trigger releases from sub modules!
Note: in case it is needed to update the version of a java bundle because of API changes and semantic versioning, one can easily update the parent POM version and all the POMs referencing the parent POM version by running the following command in the PARENT project folder:
mvn versions:set -DnewVersion=x.y.z-SNAPSHOT. This will ensure all projects have the same version.
Contributions are welcomed! Read the Contributing Guide for more information.
This project is licensed under the Apache V2 License. See LICENSE for more information.
1: "Venia" is the name of the sample progressive web app development by Magento. It has a specific theme which has been applied to our project, event though we're using classic AEM components ↩