Prohlížíte obsah nápovědy pro verzi:
- 6.4
- 6.3
- 6.2
- Starší verze
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
- SCF Play - child of the main page on which to play
- SCF Play - child of the main page on which to play
- 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 touch-optimized 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:
-
From the classic UI Welcome page, select Websites.
Alternatively, access the classic UI for Websites directly by browsing to /siteadmin.
When /etc/designs/an-scf-sandbox 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"; %>
select node /content/an-scf-sandbox/en/jcr:content
in the entry area at the bottom of the Properties tab, type the following values for a new property: - Name: cq:designPath
- Type: String
- Value: /etc/designs/an-scf-sandbox
- Click the green [+] Add

Poznámka:
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.