Contains We.Retail Journal SPAs for authoring on AEM.

This is the master branch, which contains latest release.

Go to development branch for the state of most recent work.

This project contains:

• content: Content Structure including /apps components and client libraries as well the /content specific sites and pages. The client library will be generated while building the SPAs.
• react-app: We.Retail Journal React application.

The application is using online Fonts included via Typekit.

You would either need a network connection or have the fonts installed on your computer:

• Proxima Nova Regular
• Bagatela Light

The project has the following minimal requirements:

• Java SE Development Kit 8 or newer
• Apache Maven 3.3.1 or newer

To build all the modules run in the project root directory the following command with Maven 3:

mvn clean install

The react-app module builds and transpiles the es6 javascript source code into a browser friendly 2015 version. It then creates a client library and copy the built javascript files in the content module. Run your Maven command lines from the root of the project to respect the module build ordering and ensure the latest version of the react-app module is used.

For ease of build and installation the following profiles are provided:

• autoInstallPackage - installs the package/bundle to an existing AEM author instance
• autoInstallPackagePublish - installs the package/bundle to an existing AEM publish instance
• autoInstallSinglePackage - package all the dependencies into a single content package and install everything to an existing AEM author instance
• autoInstallSinglePackagePublish - package all the dependencies into a single content package and install everything to an existing AEM publish instance

This project relies on the unobfuscated AEM 6.3 cq-quickstart. 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.

You can install everything needed to use the components on your running AEM instance by issuing the following command in the top level folder of the project:

mvn clean install -PautoInstallSinglePackage

You can also choose build environment by using setting build.environment property (format: colon + name):

mvn clean install -PautoInstallSinglePackage -Dbuild.environment=":production"

Available environments:

• empty string (default): non-production / development
• production: production

You can install local version of the NPM modules @adobe/cq-spa-page-model-manager and @adobe/cq-spa-component-mapping by changing a few lines in the react-app module's POM. By default, the released versions of those modules are transitively installed by @adobe/cq-react-editable-components but it is possible to override this and install local development versions instead.

First, build and link the local NPM modules you want to use by running (for instance, in your local checkout of @adobe/cq-spa-page-model-manager):

npm run build && npm link

Then use the npmLinkDeps profile when installing the project's bundles and packages such as:

mvn clean install -PautoInstallPackage,npmLinkDeps

You can install individual packages/bundles by issuing the following command in the top level folder of the project:

mvn clean install -PautoInstallPackage -pl <project_name(s)> -am

Please note that

• -pl/-projects option specifies the list of projects that you want to install
• -am/-also-make options specifies that dependencies should also be built