Editing Page Properties

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.

Page Properties

The properties are distributed across several tabs.

Basic

• 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.

    • The new tag is created when you hit Enter.
    • The new tag is shown with a small star on the right indicating that it is a new tag.

  • 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.

  • Override - Check to define the brand slug on this page.
    • The value is inherited by any child pages unless they also have their Override values set.
  • Override value - The text of the brand slug to be appended to the page title.
    • The value is appended to the page title after a pipe character such as “Cycling Tuscany | Always ready for the WKND”

• 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 welcometo the page identified by the path /v1.0/startpagefor the website http://example.com, then http://example.com/welcomewould be the vanity URL of http://example.com/content/v1.0/startpage

  CAUTION

  Vanity URLs:

  • Must be unique. Ensure that the value is not already used by another page.
  • Do not support regex patterns.
  • Should not be set to an existing page.

  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.

Advanced

• 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.

  • For example, if you define an alias of 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
  • Creating an alias sets the sling:alias property on the page node, which only impacts the resource, not the repository path.
  • Pages accessed by aliases in the editor cannot be published. Publish options in the editor are only available for pages accessed via their actual paths.
  • For further details, see Localized page names under SEO and URL Management Best Practices.

• 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.

  NOTE

  Closed user groups for the page are defined on the Permissions tab.

  CAUTION

  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.

Thumbnail

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

• Social Media sharing

  Defines the sharing options available on the page. Exposes the options that are available to the Sharing core component.

  • Enable user sharing for Facebook
  • Enable user sharing for Pinterest
  • Preferred XF variation
    Define Experience Fragment variation used for generating metadata for a page

Cloud Services

• Cloud Services

  Define properties for cloud services.

Personalization

• ContextHub Configurations

  Select the ContextHub Configuration and Segments Path.

• Targeting Configuration

  Select a Brand to specify a scope for Targeting.

  NOTE

  This option requires the user account to be in the Target Adminstratorsgroup.

Permissions

• Permissions

  In this tab you can:

  • Add Permissions

  • Edit Closed User Group

  • View the Effective Permissions

  CAUTION

  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.

  NOTE

  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

• Blueprint

  Define properties for a Blueprint page within multi-site management. Controls the circumstances under which modifications are propagated to the Live Copy.

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.

Site Structure

• Provide links to pages that provide site-wide functionality, such as Signup Page, Offline Page, among others.

Editing Page Properties

You can define page properties:

• From the Sites console:

  • Creating a page (a subset of the properties)

  • Clicking or tapping Properties

    • For a single page
    • For multiple pages (only a subset of the properties are available for editing en masse)

• From the page editor:

  • Using Page Information (then Open Properties)

From the Sites Console - Single Page

Clicking or tapping Properties to define the page properties:

1. Using the Sites console, navigate to the location of the page for which you want to view and edit properties.

2. Select the Properties option for the required page using either:

   • Quick actions
   • Selection mode

   The page properties are shown using the appropriate tabs.

3. Either view or edit the properties as required.

4. Then use Save to save your updates followed by Close so you can return to the console.

When Editing a Page

When editing a page, you can use Page Information to define the page properties:

1. Open the page for which you want to edit properties.

2. Select the Page Information icon to open the selection menu:

   

3. 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:

   • Cancel
   • Save & Close

4. Use the Save & Close button to save the changes.

From the Sites Console - Multiple Pages

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.

You can select multiple pages for bulk editing by various methods, including:

• When browsing the Sites console
• After using Search to locate a set of pages

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

  • If any of the pages are in a live copy, then a message is shown when the properties are opened.

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

    • You can select/deselect if necessary

  • Tabs

    • As when viewing properties for a single page, the properties are ordered under tabs.

  • A subset of properties

    • Properties that are available on all selected pages and have been explicitly defined as available to bulk editing are visible.
    • If you reduce the page selection to one page, then all properties are visible.

  • Common properties with a common value

    • Only properties with a common value are shown in View mode.
    • When the field is multi-value (for example, Tags), values are only shown when all are common. If only some are common, they are only shown when editing.

  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.

    • The new values are applied to all selected pages when you select Done.
    • When the field is multi-value (for example, Tags), you can either append a new value or remove a common value.

  • Fields that are common, but have different values across the various pages, are indicated with a special value such as the text <Mixed Entries>.