Learn how to quickly create a new AEM site using a site template.
In the previous document of the AEM Quick Site Creation journey, Understand Cloud Manager and the Quick Site Creation Workflow, you learned about Cloud Manager and how it ties together the new Quick Site Creation process and you should now:
This article builds on those fundamentals so you can take the first configuration step and create a new site form a template which you can then later customize using front-end tools.
This document helps you understand how to quickly create a new AEM site using a site template. After reading you should:
This part of the journey applies to the AEM administrator.
Site templates are a way to combine basic site content into a convenient and reusable package. Site templates generally contain base site content and structure as well as site styling information to get new site started quickly. The actual structure is as follows:
files: Folder with the UI kit, XD file, and possibly other files
previews: Folder with screenshots of the site template
site: Content package of the content that is copied for each site created from this template such as page templates, pages, etc.
Templates are powerful because they are reusable so that your content authors can quickly create a site. And since you can have multiple templates available in your AEM installation, you have the flexibility to meet various business needs.
The site template is not to be confused with page templates. Site templates described here define the overall structure of a site. A page template defines the structure and initial content of an individual page.
The simplest way to get started is to download the latest release of the AEM Standard Site Template from its GitHub repository.
Once downloaded you can upload it to your AEM environment as you would any other package. See the Additional Resources section for details on how to work with packages if you need more information on this topic.
The AEM Standard Site Template can be customized to meet your project’s needs and can obviate the need for further customization. However this topic is beyond the scope of this journey. Please refer to the GitHub documentation of the Standard Site Template for more information.
You can also choose to build the template from source as part of your project workflow. However this topic is beyond the scope of this journey. Please refer to the GitHub documentation of the Standard Site Template for more information.
Using a template to create a new site is very easy.
Sign into your AEM authoring environment and navigate to the Sites console
Tap or click Create at the top-right of the screen and from the drop-down menu select Site from template.
In the Create Site wizard, tap or click on Import at the top of the left column.
In the file browser, locate the template you downloaded previously and tap or click Upload.
Once uploaded, it appears in the list of available templates. Tap or click on it to select it (which also reveals information about the template in the right column) and then tap or click Next.
Provide a title for your site. A site name can be provided or will be generated from the title if omitted.
Tap or click Create and the new site is created from the site template.
In the confirmation dialog that appears, tap or click Done.
In the sites console, the new sites is visible and can be navigated to explore its basic structure as defined by the template.
Content authors can now begin authoring.
Site templates are very powerful and flexible and any number can be created for a project, allowing for easy creation site variations. Depending on the level of customization already performed on the site template you use, you may not even need additional front-end customization.
If you do require additional front-end customization, keep in mind that the front-end developer may not be familiar with the details of your content. Therefore it is a good idea to provide the developer with a path to typical content that can be used as a base of reference as the theme is customized. A typical example is the home page for the master language of the site.
In the sites browser, navigate to the home page of the master language of the site and then tap or click the page to select it and then tap or click Edit in the menu bar.
In the editor, select the Page Information button in the toolbar and then View as published.
In the tab that opens, copy the path of the content from the address bar. It will look something like
Save the path to later provide to the front-end developer.
Now that the site has been created, the theme of the site as generated by the template can be downloaded and provided to the front-end developer for customization.
On the sites console, show the Site rail.
Tap or click the root of your new site and then tap or click Download Theme Sources in the site rail.
You now have a copy of the theme source files in your download files.
In order for the front-end developer to preview the customizations using actual AEM content from your site, you must set up a proxy user.
In AEM from main navigation go to Tools -> Security -> Users.
In the user management console, tap or click Create.
In the Create New User window you must at a minimum provide:
On the Groups tab, add the proxy user to the
contributorstriggers AEM’s auto-completion feature for easy selection of the group.
Tap or click Save & Close.
You now have completed the configuration. Content authors can now begin to create content on the site preparation begins for front-end customization in the next step of the journey.
Now that you have completed this part of the AEM Quick Site Creation journey you should:
Build on this knowledge and continue your AEM Quick Site Creation journey by next reviewing the document Set Up Your Pipeline, where you will create a front-end pipeline to manage the customization of your site’s theme.
While it is recommended that you move on to the next part of the Quick Site Creation journey by reviewing the document Set Up Your Pipeline, 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.