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.
Developing and managing content
Use these tools and processes to develop and manage your website.
Projects
Projects are used to change a set of items on your site and ensure that they are published together at the same time. A new project has a default workflow that allows content to be reviewed and approved before it is published.
Scope of edits
When you edit pages in a project, you use workflow for approving changes before you publish them until they are approved. If you edit pages without selecting a project, your changes are published immediately.

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.
  - 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.
    - Previewing as another user
      You can preview changes to your website without logging out and logging on again as another user. This preview capability is used to quickly verify that users with different access levels see only content that they are authorized to see. You can preview changes as a specific user or as an unauthenticated user.
    - Projects
      Projects are used to change a set of items on your site and ensure that they are published together at the same time. A new project has a default workflow that allows content to be reviewed and approved before it is published.
      - Project review state
        If you select at least one approver for a project, the project must be submitted for review before it can be published.
      - Project States
        When you use a project, the project progresses through a series of states.
      - Ways to publish a project
        Publishing a project refreshes the live website with your changes.
      - Project Publishing
        An outline of the process of publishing a project.
      - Drafts and projects
        You can create, update, and approve pages in a draft state, without affecting the published site. When you work with pages, you can edit pages as drafts, manage drafts with approval workflow, and then syndicate to publish changes.
      - Scope of edits
        When you edit pages in a project, you use workflow for approving changes before you publish them until they are approved. If you edit pages without selecting a project, your changes are published immediately.
      - Project Validation
        An outline of the validation process.
      - Projects and syndication
        Projects are included in syndication, the method that is used by HCL Web Content Manager to replicate data from a web content library on a syndicator server to a web content library on a subscriber server. Although projects are syndicated with other items in a library that is being syndicated, you cannot use the subscriber copy of the project to update or publish your project. Work with projects on the syndicator server only.
      - Projects and custom workflow actions
        Each workflow stage contains default actions, but you can also create custom workflow actions by creating a custom workflow plug-in.
      - Best practices for projects
        Use these tips and guidelines to develop and publish projects more effectively.
    - Workflow and change management
      You can manage changes to web content items either by creating drafts, by using workflows, or adding items to projects.
    - HCL Web Content Integrator
      The HCL Web Content Integrator is a solution for integrating externally managed web content with HCL Portal. By using standard content syndication feed technologies based on RSS 2.0, the Web Content Integrator provides a loosely coupled mechanism for transferring published content and metadata to the portal after they are approved in the source system. When the content and metadata are transferred to the portal, it is possible to use the built-in content management features of Web Content Manager to secure, personalize, and display the content to users.
    - WebDAV
      With WebDAV for HCL Digital Experience, you can use standard operating system tools to create, modify, and delete web content rather than the standard authoring portlet.
    - Blogs
      Use blogs and blog libraries to provide news and commentary on a variety of subjects pertinent to your intranet and extranet sites. Blogs and blog libraries typically combine text with graphics and links to other blogs and websites. Entries that you create and post are arranged in reverse-chronological order, with the newest entry displayed first. Readers can post comments about your entries, fostering discussions and online networking. You can manage your own blog entries and comment on other blog entries. You can also incorporate tagging and rating as you would with other WebSphere Portal content.
    - Wikis
      Use wikis to share community content on a variety of subjects pertinent to your intranet and extranet sites. Wikis typically combine text with graphics and links to other wikis and websites. You can monitor and manage your own wiki articles.
    - Installed portlets
      Learn about the portlets that are provided with HCL Digital Experience.
    - Renditions
      Renditions are different versions of an image component or element. Renditions can be thumbnails or smaller versions of an image formatted for mobile devices.
    - Video start and end points
      File components or elements that have a video file that is stored in an HTML5 video format, which includes MP4, webM, or ogg, are stored in Brightcove and have a Brightcove ID.
  - 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.

Scope of edits | HCL Digital Experience

When you edit pages in a project, you use workflow for approving changes before you publish them until they are approved. If you edit pages without selecting a project, your changes are published immediately.

When you edit pages, it is good practice to work within a project. When you are working in a project, any changes that you make to a page affect only the view within the project. After the project is approved and published, the changes are then available to all users.

Note: Changes to private pages and community pages are not part of a project. When you are working in a project, actions that personalize or create a private page are not visible.

When no project is selected, you are modifying the published site. Changes to public pages affect all users and are available immediately. While you work on the published site, changes that other users are making within active projects are not visible.

Default workflow for pages in projects

To make the page changes available on the published site, you must submit the page for review and approval. The steps for the workflow depend on what is defined for the page. By default, a simple workflow is assigned to page or URL mapping drafts. The default workflow (Express Workflow) has only two states: draft and published. For pages that use this workflow, submitting the draft moves the page to the publish pending state. When all other changes in the project are published, the pending draft page is also published. After all items in the project reach the pending state before publishing, you can publish the project by clicking Publish in the project menu.

Note: If you use the authoring portlet to edit the access settings for a page that is part of a workflow, you cannot modify the approvers. To change the approvers for the page, you must set the approvers on the workflow stage that currently contains the page.

However, you can change the assigned workflow in the user interface to include more review and approval stages on the project level in Web Content Manager. After the draft changes in the project are approved and published, the updated pages are visible to all users. For details on using a custom workflow, see Adding workflow to managed pages.