You can define the required properties for a page. These can vary depending on the nature of the page. For example, some pages might be connected to a live copy while others are not and the live copy information becomes available as appropriate.
The properties are distributed across several tabs.
Title
The title of the page is shown in various locations. For example, the Websites tab list and the Sites card/list views.
This is a mandatory field.
Tags
Here you can add or remove tags from the page by updating the list in the selection box:
After selecting a tag, it is listed below the selection box. You can remove a tag from this list using the x.
A new tag can be entered by typing the name in an empty selection box.
With the drop-down functionality, you can select from existing tags.
An x appears when you mouse-over a tag entry in the selection box, which can be used to remove that tag for this page.
For more information about tags, see Using Tags.
Hide in Navigation
Indicates whether the page is shown or hidden in the page navigation of the resulting site.
Branding
Apply a consistent brand identity across pages by appending a brand slug to each page title. This functionality requires use of the Page Component from release 2.14.0 or later of the Core Components.
Page Title
A title to be used on the page. Typically used by title components. If empty, the Title is used.
Navigation Title
You can specify a separate title for use in the navigation (for example, if you want something more concise). If empty, the Title is used.
Subtitle
A subtitle for use on the page.
Description
Your description of the page, its purpose, or any other details you want to add.
On Time
The date and time at which the published page becomes activated. When published, this page remains dormant until the specified time.
Leave these fields empty for pages that you want to publish immediately (the normal scenario).
Off Time
The time at which the published page becomes deactivated.
Again leave these fields empty for immediate action.
Vanity URL
Enter a vanity URL for this page, which can let you have a shorter and/or more expressive URL.
For example, if the Vanity URL is set to welcome
to the page identified by the path /v1.0/startpage
for the website http://example.com,
then http://example.com/welcome
would be the vanity URL of http://example.com/content/v1.0/startpage
Vanity URLs:
Configure Dispatcher to enable access to vanity URLs. See Enabling Access to Vanity URLs for more details.
Redirect Vanity URL
Indicates whether you want the page to use the vanity URL.
Language
The page language.
Language Root
Must be checked if the page is the root of a language copy.
Redirect
Indicate the page to which this page should automatically redirect.
Design
Indicate the design to be used for this page.
Alias
Specify an alias to be used with this page.
private
for the page /content/wknd/us/en/magazine/members-only
, then this page can also be accessed via /content/wknd/us/en/magazine/private
sling:alias
property on the page node, which only impacts the resource, not the repository path.Inherited from <path>
Indicates whether the page is inherited. and where from.
Cloud Configuration
The path to the configuration.
Allowed Templates
Define the list of templates that are available within this sub-branch.
Enable (Authentication Requirement)
Enable (or disable) the use of authentication so you can access the page.
Closed user groups for the page are defined on the Permissions tab.
The Permissions tab allows the editing of CUG configurations based on the presence of the granite:AuthenticationRequired
mixin. If page permissions are configured using deprecated CUG configurations, based on the presence of cq:cugEnabled
property, a warning message is shown under Authentication Requirement and the option is not editable, nor are the Permissions editable.
In such a case the CUG permissions must be edited in the classic UI.
Login Page
The page to be used for login.
Export Configuration
Specify an export configuration.
Shows the page thumbnail image. You can:
Generate Preview
Generate a preview of the page that you want to use as a thumbnail.
Upload Image
Upload an image that you want to use as a thumbnail.
Select Image
Select an existing Asset that you want to use as the thumbnail.
Revert
This option becomes available after you have changed the thumbnail. If you do not want to keep your change, you can revert that change before saving.
Social Media sharing
Defines the sharing options available on the page. Exposes the options that are available to the Sharing core component.
Cloud Services
Define properties for cloud services.
ContextHub Configurations
Select the ContextHub Configuration and Segments Path.
Targeting Configuration
Select a Brand to specify a scope for Targeting.
This option requires the user account to be in the Target Adminstrators
group.
Permissions
In this tab you can:
The Permissions tab allows editing of CUG configurations based on the presence of the granite:AuthenticationRequired
mixin. If page permissions are configured using deprecated CUG configurations, based on the presence of cq:cugEnabled
property, a warning message is shown and the CUG permissions are not editable, nor is the Authentication Requirement on the Advanced tab editable.
In such a case the CUG permissions must be edited in the classic UI.
The Permissions tab does not allow the creation of empty CUG groups, which can be useful as a simple way to deny access to every user. To do this, CRX Explorer must be used. See the document User, Group, and Access Rights Administration for more information.
Blueprint
Define properties for a Blueprint page within multi-site management. Controls the circumstances under which modifications are propagated to the Live Copy.
Livecopy
Define properties for a Live Copy page within multi-site management. Controls the circumstances under which modifications are propagated from the Blueprint.
You can define page properties:
From the Sites console:
Creating a page (a subset of the properties)
Clicking or tapping Properties
From the page editor:
Clicking or tapping Properties to define the page properties:
Using the Sites console, navigate to the location of the page for which you want to view and edit properties.
Select the Properties option for the required page using either:
The page properties are shown using the appropriate tabs.
Either view or edit the properties as required.
Then use Save to save your updates followed by Close so you can return to the console.
When editing a page, you can use Page Information to define the page properties:
Open the page for which you want to edit properties.
Select the Page Information icon to open the selection menu:
Select Open Properties and a dailog box opens letting you edit the properties, sorted by the appropriate tab. The following buttons are also available at the right of the toolbar:
Use the Save & Close button to save the changes.
From the Sites console, you can select several pages then use View Properties to view and/or edit the page properties. This is referred to as bulk editing of page properties.
Bulk editing of properties is also available for Assets. It is similar, but differs in a few points. See Editing Properties of Multiple Assets for details.
There is also the Bulk Editor. This editor lets you search for content from multiple pages using GQL (Google Query Language), and then edit the content directly using the Bulk Editor before saving your changes to the originating pages.
You can select multiple pages for bulk editing by various methods, including:
After selecting the pages and then clicking or tapping the Properties option, the bulk properties are shown:
You can only bulk edit pages that:
Share the same resource type
Are not part of a livecopy
Once you have entered Bulk Editing, you can do the following:
View
When viewing Page Properties for multiple pages, you can see the following:
A list of the pages impacted
Tabs
A subset of properties
Common properties with a common value
When no properties with a common value exist, a message is displayed.
Edit
When editing Page Properties for multiple pages:
You can update the values in the fields available.
Fields that are common, but have different values across the various pages, are indicated with a special value such as the text <Mixed Entries>
.
The page component can be configured to specify the fields available for bulk editing. See Configuring your page for bulk editing of page properties.