Set up Your Pipeline set-up-your-pipeline

Create a front-end pipeline to manage the customization of your site’s theme.

The Story So Far story-so-far

In the previous document of the AEM Quick Site Creation journey, Create Site from Template, you learned how to use a site template to quickly create an AEM site that can be further customized using front-end tools and now you should now:

  • Understand how to obtain AEM Site templates.
  • Learn how to create a site using a template.
  • See how to download the template from your new site to provide to the front-end developer.

This article builds on those fundamentals so you can set up a front-end pipeline, which the front-end developer will use later in the journey to deploy front-end customizations.

Objective objective

This document helps you understand front-end pipelines and how to create one to manage the deployment of your site’s customized theme. After reading you should:

  • Understand what a front-end pipeline is.
  • Know how to set up a front-end pipeline in Cloud Manager.

Responsible Role responsible-role

This part of the journey applies to the Cloud Manager administrator.

Requirements requirements

  • You need to have access to Cloud Manager.
  • You need to be a member of the Deployment Manager role in Cloud Manager.
  • A git repo for the AEM environment must be set up in Cloud Manager.
    • This is generally already the case for any active project. However if it is not, see Cloud Manager Repositories documentation available under the Additional Resources section.

What is a Front-End Pipeline front-end-pipeline

Front-end development involves the customization of JavaScript, CSS, and static resources that define the styling of your AEM site. The front-end developer will work in their own local environments to make these customizations. Once they are ready, the changes are committed to the AEM git repository. But they are only committed to the source code. They are not yet live.

The front-end pipeline takes these committed customizations and deploys them to an AEM environment, generally production or non-production environments.

In this way, front-end development can work separately from and parallel to any full-stack back-end development on AEM, which has its own deployment pipelines.

The front-end pipelines can only deploy JavaScript, CSS, and static resources to style your AEM site. Site content such as pages or assets cannot be deployed in a pipeline.

Access Cloud Manager login

  1. Log into Adobe Cloud Manager at

  2. Cloud Manager lists the various programs available. Select the one you want to manage. If you are just starting with AEM as a Cloud Service, you likely only have one program available.

    Selecting a program in Cloud Manager

You now see an overview of your program. Your page will look different but similar to this example.

Cloud Manager overview

Note the name of the program that you have accessed or copy the URL. You need to provide this to the front-end developer later.

Create a Front-End Pipeline create-front-end-pipeline

Now that you have accessed Cloud Manager, you can create a pipeline for front-end deployment.

  1. In the Pipelines section of the Cloud Manager page, select the Add button.


  2. In the pop-up menu that appears beneath the Add button select Add Non-Production Pipeline for the purposes of this journey.

  3. On the Configuration tab of the Add Non-Production Pipeline dialog that opens:

    • Select Deployment Pipeline.
    • Provide the pipeline with a name in the Non-Production Pipeline Name field.

    Add pipeline configuration

  4. Select Continue.

  5. On the Source Code tab:

    • Select Front End Code as the type of code to deploy.
    • Make sure that the correct environment is selected under Eligible Deployment Environments.
    • Select the correct Repository.
    • Define which Git Branch the pipeline should be associated with.
    • Define the Code Location if the front-end development is located under a particular path in the selected repository. The default value is the root of the repository, but often front-end development and back end are under different paths.

    Source code info for adding pipeline

  6. Select Save.

The new pipeline is created and visible in the Pipelines section of the Cloud Manager window. Tapping of clicking the ellipsis after the pipeline name reveals options to further edit or view details as necessary.

Pipeline options

If you are already familiar with pipelines in AEMaaCS and want to learn more about the differences between the different types pipelines including further details about the front end pipeline, see Configure CI/CD Pipeline - Cloud Services linked in the Additional Resources section below.

What’s Next what-is-next

Now that you have completed this part of the AEM Quick Site Creation journey you should:

  • Understand what a front-end pipeline is.
  • Know how to set up a front-end pipeline in Cloud Manager.

Build on this knowledge and continue your AEM Quick Site Creation journey by next reviewing the document Grant Access to the Front-End Developer, where you will onboard the front-end developers into Cloud Manager so they have access to your AEM site git repository and pipeline.

Additional Resources additional-resources

While it is recommended that you move on to the next part of the Quick Site Creation journey by reviewing the document Customize the Site Theme, the following are some additional, optional resources that do a deeper dive on some concepts mentioned in this document, but they are not required to continue on the journey.