SDL releases Tridion Sites 9.5

SDL Tridion Sites 9.5 marks a major step towards a fully rejuvenated user experience for SDL Tridion practitioners, while also including improvements in Search and Content Delivery.

Experience Space – our new and improved user interface
How the Dynamic Experience Delivery component has been improved with better search and easier headless publishing
How the functional and technical features of each release compare in simple summary tables

Please refer to the community link for the announcement

What’s new in SDL Tridion Sites 9.5

Refer to my blogs Link for more details and you can download the datasheet from our website refer to link

Topology Manager

Topology Manager forms the bridge between the Content Manager and Content Delivery environments. By decoupling the two environments, it becomes easy to swap out environments on either side, and to separate concerns by specific roles in your organization.

Topology Manager maps logical publishing targets selected by the end user to physical publishing destinations on the presentation environments. Because Topology Manager is a separate software component from Content Manager, it makes it easy for you to extend the delivery environment to include mode endpoints, or to move your delivery environment into the Cloud.

Topology Manager has no clients or APIs, only a database. The user interface consists of a number of PowerShell cmdlets.

Topology Manager concepts

Use Topology Manager to communicate information between a Content Manager environment on the one hand, and one or more Content Delivery environments on the other hand.

Web application

At the most basic level, each publishable Publication in Content Manager maps to a Web application. Multiple Publications can map to the same Web application. Each Web application is part of a Web site, and is represented by an ID and a context URL (relative to the Web site’s base URL).

Web site

A Web site has an ID and a base URL. One Web site contains one or more Web applications.

Content Delivery environment

A Content Delivery environment, identified by an ID, and accessible through a Discovery Endpoint URL and a set of credentials, represents a number of Content Delivery Capabilities and a collection of one or more Web sites, hosted on one or more Presentation Servers.

Purpose

Every Content Delivery environment has a Purpose. A Content Delivery environment’s Purpose makes clear to what end the environment is being used.

For example, an environment with a Purpose called “Staging” is intended to be used as a staging environment; an environment with a Purpose called “Live” is intended to be used as a live environment.

Topology

A Topology defines a complete publishing environment: it consists of a set of Content Delivery environments, each with a distinct Purpose. A Topology is a concrete instance of a Topology Type. For example, given a Topology Type that defines two Purposes “Live” and “Staging”, a Topology defines what the words “Live” and “Staging” actually stand for. The Topology must specify one Content Delivery environment for each of the Purposes defined in its Topology Type.

If your organization has multiple publishing environments, it will also have multiple Topologies. For example:

Your implementation supports different definitions for “Live” and “Staging” that depend on what is being published. For example, in some situations you may want to define “Staging” and “Live” as Content Delivery environments in the cloud, while in other situations “Staging” and “Live” might refer to on-premises Content Delivery environments. In this scenario, you would define one Topology Type that defines the Purposes “Staging” and “Live”, and two Topologies, one used for on-premises publishing and another for cloud publishing.

Another example might be that, depending on regulatory concerns or to optimize performance, you want the servers associated with “Staging” and “Live” environments to reside in a specific geographic location. In this case, you would again have one Topology Type defining “Staging” and “Live”, and any number of Topologies, one for each geographic location.

If you have multiple Topologies defined for a Topology Type, the mapping from the Publication to the Web application determines which of the Topologies content gets published to.

Topology Type

A Topology Type is a list of Purposes, that is, a list of the types of environment you can publish to. Content may pass through a number of environments before going live, depending on the publishing workflows your organization supports.

For example, for legally sensitive content, your organization may require one staging environment for editorial review, and another for legal review. This would result in a Topology Type with three Purposes: “Staging Editorial”, “Staging Legal” and “Live”.

At the same time, content that requires no legal review may require only one staging environment, which would entail another Topology Type, with only two Purposes: “Staging” and “Live”.

Business Process Type

In Content Manager, a Business Process Type represents a number of settings that together define a certain type of business process in your organization. Put simply, it defines how content is allowed to flow through your organization, both while it is being managed and when it gets published. In the context of publishing, a Business Process Type refers to a Topology Type and contains a number of Target Types (as many as the Topology Type has Purposes). Each publishable Publication must have one and exactly one Business Process Type associated with it.

Target Type

Target Types are the items that the end user selects when publishing (or unpublishing) content. Each Target Type has a Purpose. Target Types would typically be named after their Purpose, so they would be “Live” and “Staging”. Note that the physical location where the content will end up depends not only on the Target Type(s) selected, but also on the Publication from which the publish action takes place.

In the Business Process Type, Target Types can be given a Minimal Approval Status, meaning that publishing to that Target Type is impossible until it has reached at least the Approval Status specified; and they can be given higher or lower priority than the default, to accelerate publishing to a live environment when possible, or delay publishing to a staging environment when necessary. You can also restrict the ability to publish to a Target Type to a certain subset of your users.

# Create Topology Type 

EnvironmentPurposes : Define Staging and Live Target.

Add-TtmCdTopologyType -ID DemoTopologyType -Name "Demo Topology Type" -EnvironmentPurposes @("Staging", "Live")

# Create Content Delivery Environment ( Staging )

Add-TtmCdEnvironment -ID DemoStagingCdEnvironment -DiscoveryEndpointUrl https://localhost:8082/discovery.svc -EnvironmentPurpose Staging -AuthenticationType OAuth -ClientId cmuser -ClientSecret '******'

# Create Content Delivery Environment ( Live )

Please make sure the  dicovery port is different if you are running on the same machine
Add-TtmCdEnvironment -ID DemoLiveCdEnvironment -DiscoveryEndpointUrl https://localhost:8082/discovery.svc -EnvironmentPurpose Live -AuthenticationType OAuth -ClientId cmuser -ClientSecret '*****'

# Create Topology

Add-TtmCdTopology -Id DemoTopologyType -Name "Demo Topology" -CdTopologyTypeId DemoTopologyType -CdEnvironmentIds @("DemoStagingCdEnvironment", "DemoLiveCdEnvironment") 

# Create Website

Add-TtmWebsite -Id Staging_Website -CdEnvironmentId DemoStagingCdEnvironment-Baseurls @("https://demo.staging.com")

Add-TtmWebsite -Id Live_Website -CdEnvironmentId DemoLiveCdEnvironment-Baseurls @("https://demo.live.com")

# Create Mapping

Add-TtmMapping -Id EN_STAGING_Mapping -PublicationID "tcm:0-40-1" -WebApplicationId DemoStaging_Website_RootWebApp -RelativeUrl /en;
Add-TtmMapping -Id ES_STAGING_Mapping -PublicationID "tcm:0-41-1" -WebApplicationId DemoStaging_Website_RootWebApp -RelativeUrl /es;

Tridion Sites 9.5 Semantic Content Models

Semantic Content Models

.

Semantic Content Models’ allows you to define a mapping between the Tridion content fields and how they are queried through the GraphQL API.

This abstraction mechanism removes dependencies between the two, so that future changes to your content model don’t directly impact your front-end applications. As a result, your front-end developers can build engaging digital experiences more easily, without needing to know the inner workings of SDL Tridion

  • Customers can define their own semantic content models using GraphQL Schema Definition Language
type Post {
     id: String!
     title: String!
     publishedAt : DateTime!
     likes: Int! @default(value: 0)
     blog: Blog @relation(name:"Posts")
}

Allow customers to query filter using familiar concepts ( for example : Article , News,Post,Blog etc.)

type Blog {
  id: String!
  name: String!
  description:String
  posts: [Post!]! @relation(name: "Posts")
}

Semantic Content Models in DXD

Semantic content models exposed natively in the content API

page(namespaceId: 1, publicationId:2 , pageId:76 {
 content {
     ... on UntypedContent {
          data {
          }
        }
    }

Refined GraphQL API to support custom schema types within existing root queries ( Items,component,page

page(namespaceId: 1, publicationId:2 , pageId:76 {
 content {
     ... on Post {
          id
          title
        }
    }

Tridion Sites 9.5 Search

Why SDL Tridion Sites Search

.

SDL Tridion Sites now ships with out-of-the-box support for Elasticsearch-based search for published content, helping you find published content within pages, components and binaries. You can also search for content from SDL Tridion Docs, providing federated
search capabilities across both unstructured and structured content. People searching on your website or other digital channels can now find all the relevant information quickly and easily, without the need to perform multiple searches across your marketing content or
in-depth product and service information.

  • Customers currently have to implement their own solution ( SI4T or custom Deployer extension)
  • Optimized for SDL Tridion Sites data model
  • Makes use of existing Elasticsearch infrastructure (XO and Tridion Docs search) – upgraded to Elasticsearch 7
  • Exposed through existing Content Service ( GraphQL)
  • Predefined Content Service
  • Configurable using profile
  • Uses Data pipeline ( requires existing sites content to be re-published
# Content Service
applications.properties
# broker: default
profile to enable broker results
# search: enables search
spring.profiles.active=${springprofilesactive:broker,search)

GraphQL Search

  • New root queries to support search across both Sites & Docs
  • Supports combining results with broker
  • Supports cursor based pagination
searchById(indexName,identifier):
[Result]

searchByField(after,first,indexName,field,strict,value,resultFilter,sortBy):
SearchConnection

searchByCriteria(after,first,indexName,field,strict,value,resultFilter,sortBy):
SearchConnection

searchByRawQuery(after,first,indexName,field,strict,value,resultFilter,sortBy):
SearchConnection

SDL Tridion Docs + Tridion Sites

  • Find matching content across Tridion Docs Technical & Tridion Sites marketing publications
  • Retrieve matching topics & pages
  • Response will include matches across both namespace

Tridion Sites 9.5 Semantic Data Publishing Models

Publishing Model

New data publishing capabilities allow you to define – at the content schema level – which fields need to be published to DXD, as well as which ones are searchable. This highly granular control over what data is transferred to DXD adds extra security to your
environments.

Data Publishing

Publish content as structured date ( JSON) next to the existing rendered content

Standard data model – no need in data modifications or custom tem

Benefits of Data Publishing

  • It is enabler for strongly typed models that we will cover today as well as Tridion Sites search – out of the box search on content delivery side .
  • Data publishing is a publishing content as structure data in JSON format next to existing rendered content
  • We use standard data model so no need in data modifications or any custom template

New field properties for the Schema

Applicable for semantic content models

Each Schema field will have checkbox to specify

  • if it should be published
  • if it should be indexed on DXD

General Settings for Schema

  • Possibility to exclude item from publishing or indexing
  • Applicable for Component Schema , Metadata Schema and Multimedia Schema

ECL data publishing

  • Connectors defines if binary should be included or passed by reference
  • External metadata fields are always published and indexed

Template-less publishing: future is near

  • Before SDL Tridion 9.5 – contains static and dynamic components
  • Data publishing is template-less publishing – no more templates . All components and or dynamic
  • Template resolving behavior is still preserved
  • Possibility to not specify a template

What’s new in SDL Tridion Sites 9.5

  • Experience Space – our new and improved user interface 
  • How the Dynamic Experience Delivery component has been improved with better search and easier headless publishing 
  • Access Management
  • Searching in headless world
  • How the functional and technical features of each release compare in simple summary tables

A new user experience


SDL Tridion Sites 9.5 focuses on delivering major improvements for employees who work in Content Manager Explorer (CME). We have gathered input from a large number of customer interviews, user experience (UX) sessions, and through an extensive pilot period – combined with ideas and enhancements for usability improvements that we collected previously through Support, SDL Ideas, the SDL Community and other channels.

Experience Space – an exceptional new way of working

The name of the new user interface is Experience Space. It’s a workspace that helps you build great experiences faster
and easier, with less clicks and better defaults. It also speeds up onboarding of new employees and reduces
training needs.

Experience Space broadly offers the same capabilities of the current CME – referred to as the Classic UI from now
onwards – but with some important features added, such as an improved BluePrinting® viewer and an in-context page
preview with clear actions and panels.

Besides offering easier content management, it also ships with a brand new Rich Text Editor that improves accessibility
checks, copy/paste and table editing, and support for certain touch-enabled devices.

The new user interface supports your existing page and content models to facilitate a smooth transition. SDL Tridion
Sites 9.5 ships with both the Classic UI and Experience Space so they can be used in parallel.

Dynamic Experience Delivery (DXD)

Dynamic Experience Delivery (DXD) is the content delivery component of SDL Tridion. It has been improved in two key areas – querying content through the GraphQL API and
Elasticsearch-based search.

Headless Content Publishing

To make headless content publishing even easier, SDL Tridion Sites 9.5 redefines the way content is published from your content manager to your content delivery (DXD) environments – as well as how it can be queried from there.

New data publishing capabilities allow you to define – at the content schema level – which fields need to be published to DXD, as well as which ones are searchable. This highly granular control over what data is transferred to DXD adds extra security to your
environments.

Content is published to DXD in JSON format for easy headless content consumption. The new JSON publishing (depicted in green below) runs in parallel with your existing template/rendering mechanism, to ensure backward compatibility.

Once JSON content has been published to DXD, a new feature called ‘Semantic Content Models’ allows you to define a mapping between the Tridion content fields and how they are queried through the GraphQL API. This abstraction mechanism removes dependencies
between the two, so that future changes to your content model don’t directly impact your front-end applications. As a result, your front-end developers can build engaging digital experiences more easily, without needing to know the inner workings of SDL Tridion.

Search

SDL Tridion Sites now ships with out-of-the-box support for Elasticsearch-based search for published content, helping you find published content within pages, components and binaries. You can also search for content from SDL Tridion Docs, providing federated
search capabilities across both unstructured and structured content. People searching on your website or other digital channels can now find all the relevant information quickly and easily, without the need to perform multiple searches across your marketing content or
in-depth product and service information.

Since SDL Tridion Experience Optimization uses the same technology, you can also personalize the customer experience across various content types, all using the same technology and infrastructure
footprint.

Access Management

A new Access Management UI allows you to configure external identity providers such as Auth0, PingIdentity and Microsoft Azure AD – supporting protocols including SAML 2.0, OpenID Connect, Windows Authentication and LDAP. SDL Tridion also keeps an audit
trail of changes made to identity provider settings and user profiles, so you can always see who has changed what and when.

Summary of features launched per release