Home
HCL Digital Experience 9.5 [Legacy content]
Setting up a website
Setting up a website includes, creating pages, adding navigation, setting up search, and adding content to the site. Themes are used to customize the portal's look-and-feel. Out-of-the-box templates and the site wizard can help you set up your portal site faster. You can add wikis and blogs to your site and let users tag and rate content on your site.
Building the website
Building a website includes creating libraries, pages, and web content. You also create links and navigation to your content, and assign access to different types of users, such as editors and viewers.
Static content
Static content is part of every website. In a portal site, static content can be rendered as static page or it can be added to specific content areas on a page.
Creating a static page
You can create a new portal page by starting with a static HTML file or an HTML fragment. If you revise the HTML, you can refresh the page to render the changes in the portal.
Portlets for adding dynamic elements to static pages
If you want to add dynamic elements such as portal navigation to your static pages, you can use portlets that the portal provides.
The SPA Resource Addressability portlet
The SPA Resource Addressability portlet allows you to add a dynamically computed list of links to portal resources to a static page. This list is produced dynamically via a POCURI (Piece Of Content URI).

HCL Digital Experience 9.5 [Legacy content]
- Overview
  HCL Digital Experience provides a single access point to web content and applications, while it delivers differentiated, personalized experiences for each user across multiple touchpoints, such as web, mobile, hybrid mobile/web applications, and more.
- Supported migration paths
  Migration is supported between equivalent HCL Digital Experience offerings.
- Supported installation and upgrade paths
  Installation and upgrade is supported between equivalent HCL Digital Experience offerings.
- Getting the software
  New and existing users need to register at the HCL Software License Portal and download their entitled HCL Digital Experience package(s).
- Creating your website
  Review the following topics to understand how to create your website using the latest HCL Digital Experience.
- Installing HCL Digital Experience
  Review the planning information on HCL Digital Experience, then select your operating system and installation pattern that most reflects your business needs.
- Configuring
  Run the following tasks after you install and deploy HCL Digital Experience. They address tasks that are typically run one time and have a global effect. Some configuration changes are made more frequently or do not have a global effect. These tasks are addressed in the Administering section.
- Backup and restore
  Backup and recovery of data files and databases is an essential operation for any business system, particularly for data and applications that run in production environments. Create and follow a plan for backing up and recovering data on all tiers of your HCL Digital Experience deployment. IBM Installation Manager must also be included in backup and recovery planning. If you back up the HCL Portal file structure and then install a fix pack, your HCL Digital Experience and IBM Installation Manager become out of sync after you restore the HCL Portal file system. This condition is not recoverable.
- Migrating
  Successful migration requires significant planning and preparation, understanding the tools that are involved, and careful execution of the appropriate steps in the order provided.
- Integrating
  Integrate HCL Digital Experience with software such as HCL Sametime to enable your users to collaborate more easily. You can also use the unified task list portlet to integrate HCL with your backend business process software, such as IBM Process Server.
- Administering
  Use the administration tools that are provided with the HCL Digital Experience to do various day-to-day administration tasks.
- Securing
  Security tasks include setting up property extension databases and custom user repositories, configuring and activating SSL, and configuring authentication. In addition, tasks such as activating Federal Information Processing Standards (FIPS) and NIST SP800-131a security modules and configuring external security managers such as Security Access Manager might be required to secure your portal environment.
- Monitoring
  HCL Portal includes tools and features to help you monitor the portal site.
- Setting up a website
  Setting up a website includes, creating pages, adding navigation, setting up search, and adding content to the site. Themes are used to customize the portal's look-and-feel. Out-of-the-box templates and the site wizard can help you set up your portal site faster. You can add wikis and blogs to your site and let users tag and rate content on your site.
  - Website building blocks
    Unless you are familiar with the HCL Digital Experience and HCL Web Content Manager website model, review the building blocks. Building blocks are the different parts that make up the website framework, such as pages, navigation, themes, content, content libraries, and more.
  - Creating reusable assets
    Use reusable assets to store or generate content that is used in more than one place in your website.
  - Building the website
    Building a website includes creating libraries, pages, and web content. You also create links and navigation to your content, and assign access to different types of users, such as editors and viewers.
    - Site Builder
      Site Builder is an application that you can use to create site templates or section templates for use with HCL Digital Experience.
    - Content Template
      The Content Template (CTC) is a set of templates that accelerate the process of building a website. You should also install the Content Template with Site Builder so you can build sites based on Content Template components.
    - Content libraries
      Content libraries store the assets for your website, including but not limited to pages, content, images, authoring and presentation templates, and workflows.
    - Setting up access
      Access controls allow you to assign access to who has the ability to view rendered constant and pages, and who has the ability to edit or administer content, pages, or features.
    - Taxonomy
      Before creating a taxonomy, you should analyze how the taxonomy will be used in your site to determine the best structure for your taxonomy.
    - Navigation
      Navigation is defined by your page hierarchy and your site area hierarchy. Navigation elements include your page theme, menus, and navigators.
    - Elements
      Create a website by, building templates, and specifying other key components of the system. When these items are in place, you can begin adding elements to your templates and use them to create content items.
    - Tags
      Tags are used in your markup to reference content that is stored or generated by elements, or to display metadata from different items.
    - Setting up search for site visitors
      Learn about the initial considerations for setting up search for site visitors before you begin configuring and administering search on your website.
    - Taxonomies, Categories, and keywords
      The combination of taxonomy and categories enables control what displays in menus.
    - How to store translated text in a content item or site area
      Translated text can be stored in a content item or site area. The translated text can then be referenced in web content tags, or as localized text in web content authoring portlet forms.
    - Hiding content
      You can hide portlets and widgets on a page so they are present but not visible in the page layout.
    - Static content
      Static content is part of every website. In a portal site, static content can be rendered as static page or it can be added to specific content areas on a page.
      - Creating a static page
        You can create a new portal page by starting with a static HTML file or an HTML fragment. If you revise the HTML, you can refresh the page to render the changes in the portal.
        Example HTML markup for defining a portal page
        Use these code samples as examples of HTML markup to create a portal page.
        Class attributes for portlets on static pages
        When you place a portlet on a static HTML page to be rendered by the portal, use a suitable CSS file to format the portlet. The CSS file makes use of the portlet microformat. You can make use of this microformat if you want to render portlets on your static HTML page with a skin of your choice. When you write the static page, you can use CSS or JavaScript techniques to convert the microformat into a friendly user interface. The portlet references in the static HTML page are replaced by the content of the portlet and the portlet microformat.
        Class attributes for a portlet container on static pages
        To render a portlet container on a static page, you use a CSS file that makes use of the container microformat. One of the benefits is that users with the required access rights can later move the portlets by drag and drop.
        Class attributes for components on static pages
        When you place a component on a static HTML page to be rendered by the portal, use a suitable CSS file to format the portlet. The CSS file uses the component microformat. You can use this microformat if you want to render components on your static HTML page with a skin of your choice. When you write the static page, you can use CSS or JavaScript techniques to convert the microformat into a friendly user interface. The component references in the static HTML page are replaced by the content of the component and the component microformat.
        Navigation options for static pages
        You can provide navigation for your static pages by using either the portal theme or by making use of the navigation microformat.
        Portlets for adding dynamic elements to static pages
        If you want to add dynamic elements such as portal navigation to your static pages, you can use portlets that the portal provides.
        The Navigation portlet
        The Navigation portlet allows you to add dynamic portal navigation to a static page. When writing a static portal page you can configure the starting point of the navigation and the number of navigation levels by using the initialization parameters.
        The Breadcrumb Trail portlet
        The Breadcrumb Trail portlet allows you to add the navigation path to your static pages. The breadcrumb trail starts at the content root and goes down to the currently selected static page.
        The SPA Resource Addressability portlet
        The SPA Resource Addressability portlet allows you to add a dynamically computed list of links to portal resources to a static page. This list is produced dynamically via a POCURI (Piece Of Content URI).
      - Static resources
        In addition to the HTML file that describes the page, static pages can contain resources such as images, scripts, and styles. Learn about the static resources that are available when you are using static pages.
      - Dynamic page metadata
        HTML defines some elements that refer to information that is managed as page metadata on portal pages. You can use the dynamic page metadata rewriting feature to place this information into the static HTML code automatically.
      - Including static content pages in your portal
        You can create a new portal page by starting with a static HTML file or an HTML fragment. If you revise the HTML, you can refresh the page to render the changes in the portal. To include, update, and administer your static content pages, you can use any of the portal administration tools, Manage Pages portlet, XML configuration interface, or the Portal Scripting Interface.
      - Using WebDAV to manage pages and static content
        WebDAV for HCL Digital Experience provides a simple and easy way to administer portal resources. Both administrators and users can use it.
    - Dynamic content
      Dynamic content is generated when a page is rendered and is based on a set of predefined criteria such as the current user, the metadata of the current page. It allows you to deliver content specifically customized for the current user, or to deliver content customized for a campaign or product in your organization.
    - Content as a Service pages
      Starting with version 8.5 CF05, HCL Digital Experience introduces the concept of Content as a Service pages. The Content as a Service pages can be used to render content that is managed by your HCL Web Content Manager in different data formats.
    - URLs
      Portal URLs do not look like plain HTTP server URLs over a simple file system. Portal URLs have a complex structure and include a large compressed and encoded XML Navigation State document. The stream of random characters in a Portal URL is the Navigation State document. Full Portal function depends on correctly maintaining this Navigation State document during all the operations a user might do in Portal. Forcing Portal URLs to look like plain HTTP server URLs over a simple file system structure cripples the function of HCL Portal.
  - Authoring tools
    There are multiple ways to create and manage content including using the site toolbar, inline editing, and the authoring portlet.
  - Preparing for content authors
    Before content authors can create content you must prepare your site to be ready for content creation, including preparing the site toolbar, enabling inline editing, and creating templates.
  - Developing and managing content
    Use these tools and processes to develop and manage your website.
  - Delivering web content
    The type of delivery method you use to deliver web content to your viewers depend on the type of content that is being delivered, and the type of viewers your website is intended for.
  - Vanity URLs
    You can associate vanity URLs with portal pages and labels. Vanity URLs are short URLs that people can easily remember. They are shorter than full HCL Portal URLs. They are sometimes also called marketing URLs. You can publish vanity URLs for marketing campaigns through different channels, such as email or print. This way, you can use vanity URLs to direct customers to a specific portal page or content item. Interested site visitors who want to view your campaign can then remember or copy the short vanity URL and type it into the browser address field.
  - Social rendering
    HCL Digital Experience page editors can use social rendering to feature social data that is hosted on a remote HCL Connections server in the context of portal pages.
  - Setting up marketing campaigns
    Use these tools and features to setup marketing campaigns for your website.
  - HCL Web Content Manager Multilingual Solution
    The HCL Web Content Manager Multilingual Solution is a set of tools that are used to manage translated versions of localized and regionalized websites.
  - Syndicated Feed Portlet
    The Syndicated Feed Portlet for HCL Digital Experience offers enhanced feed subscription and presentation capabilities.
- Staging to production
  During portal solution development, the solution is initially developed, tested, and refined on one server or a limited number of servers. The solution is deployed later on live systems, referred to as the production environment. The process of moving the solution from the development environment to the production environment is called staging.
- Developing
  This section includes developer documentation on extending applications and development assets for HCL Portal and HCL Web Content Manager.
- Docker and Containerization
  Find topic information about Docker and Containerization for HCL Digital Experience.
- Practitioner Studio
  Practitioner Studio is a newly designed user experience for HCL Digital Experience. Please see the following pages to understand how the new navigation is organized.
- HCL Experience API
  This shows developers how to provision, configure, and use the HCL Experience API with the HCL Digital Experience 9.5 platform.
- HCL Content Composer
  The HCL Content Composer delivers simplified processes for creating and managing Digital Experience site content.
- HCL Digital Asset Management
  HCL Digital Asset Management (DAM) adds a central platform to store and include rich media assets in Digital Experience site content to present engaging, consistently branded experiences across digital channels.
- The Woodburn Studio demo site
  The Woodburn Studio is a website that demonstrates the use of some of the popular HCL Digital Experience features.
- Reference
  View information that can help you use our product documentation including terms of use, trademarks, and more.

The SPA Resource Addressability portlet | HCL Digital Experience

The SPA Resource Addressability portlet allows you to add a dynamically computed list of links to portal resources to a static page. This list is produced dynamically via a POCURI (Piece Of Content URI).

Unique name

You can address the SPA Resource Addressability portlet by its unique name: wps.p.SpaResourceList .

Usage

You can embed the SPA Resource Addressability portlet into a static page by using the semantic tag portlet-window described in the topic about class attributes for portlets on static pages. When rendering the page, the server replaces the tag with the portlet microformat, and the portlet renders the list of page links by using the navigation microformat. The portlet accepts the following configuration parameters that you can embed by coding a definition list ( <dl> ) in the static page:

uri: This is the POCURI to an ATOM feed. The list of resource links is the list of alternate links in this ATOM feed.
<any parameters>: All other parameters are taken as parameters for the POC (Piece Of Content) DataSource that produces the ATOM feed.