AEM 6.4 has reached the end of extended support and this documentation is no longer updated. For further details, see our technical support periods. Find the supported versions here.
In this section, you create the following pages which all use the page template:
SCF Sandbox Site, which will redirect to the English version of the main page
SCF Sandbox - The main page for the English version of the site
Although this tutorial does not delve into language copies, it is designed so the root page may implement detection of the preferred language for the user through the HTML header, and redirect to the appropriate main page for the language. The convention is to use the two-letter country code for the node name of the page, e.g., “en” for English, “fr” for French, and so on.
Now that there is a page template, we can establish the root page of the website in the /content directory.
The standard UI currently provides blueprints for creating sites. As this tutorial is creating a simple site, the classic UI is useful.
To switch to the classic UI, select global navigation and hover over the right side of the Projects icon. Select the Switch to Classic UI icon which appears:
The ability to switch to the classic UI must be enabled by an administrator.
From the classic UI Welcome page, select Websites.
Alternatively, access the classic UI for Websites directly by browsing to /siteadmin.
In the explorer pane, select Websites and then in the toolbar select New > New Page.
In the Create Page dialog, enter the following:
SCF Sandbox Site
an-scf-sandbox
In the explorer pane, select the page you just created, /Websites/SCF Sandbox Site
, and click New > New Page:
SCF Sandbox
en
In the explorer pane, select the page you just created, /Websites/SCF Sandbox Site/SCF Sandbox
, and click New > New Page
SCF Play
play
This is how the website now appears in the Websites console. Notice that child pages of the item selected in the explorer pane are displayed in the right pane where they can be managed.
This is the repository view of what was created using the Website tool and the template:
When [/etc/designs/an-scf-sandbox](setup-website.md#setupthedesigntreeetcdesigns)
was created using the designs section of the Tools console, the property ``
cq:template="/libs/wcm/core/templates/designpage"
was defined, which provides the optional ability to reference design assets in a script using currentDesign.getPath()
. For example
<% String favIcon = currentDesign.getPath() + “/favicon.ico”; %>
cq:designPath
String
/etc/designs/an-scf-sandbox
Click the green [+] Add
The respository should appear as follows:
[ Trouble saving? Re-login! ]
The use of cq:designPath is optional and is unrelated to the use of clientlibs, which are essentially required as the SCF components use clientlibs to manage their JS and CSS.