Trados Business Manager
Language Weaver Connectors
Language Weaver Edge
Tridion Docs Developers
RWS User Experience
Internal Trados Ideas Community
RWS Community Internal Group
RWS Training & Certification
RWS Enterprise Technology Partners
Trados Approved Trainers
ETUG (European Trados User Group) Public Information
Nordic Tridion Docs User Group
Tridion West Coast User Group
Trados Studio Ideas
Trados GroupShare Ideas
Trados Team Ideas
Trados Team Terminology Ideas
Trados Enterprise Ideas
Trados Business Manager Ideas
RWS Appstore Ideas
Tridion Docs Ideas
Tridion Sites Ideas
Language Weaver Ideas
Language Weaver Edge Ideas
Managed Translation - Enterprise Ideas
LiveContent S1000D Ideas
Events & Webinars
To RWS Support
Detecting language please wait for.......
Templates in Tridion Sites are a cool feature, and power a lot of great implementations. When used in cooperation with BluePrinting and versioning support, so you can say that Tridion Sites is a content management system, a version control system, and a deployment solution. However, it requires proprietary knowledge about the template implementation. Also, looking into the common process of developing a website, the template design step was preventing the possibility to deliver content to the final presentation environment, be it a web app, mobile app, or something else.
Let’s see how the process changed with the introduction of the Semantic content models feature as part of Tridion Sites 9.5 release.
Of course, steps might be different looking at different requirements for different applications, although I expect that mentioned steps will be essential for most of them.
So they are:
Let’s go step by step to build our web application.
Before defining a content structure let’s look into basic design mocks for a website. We decided to use one of the popular nowadays approaches with big tiles and a header at the top.
Once a user clicked on the tile we will open a full article view.
Define your content model
Looking into this design mocks it is clear that we will need one Schema called article and two content representations (semantic content models) of it for the Home page and Article.
So let’s start with content modeling on the Schema level as a first step.
Title of the Article
Short description of the Article to be used on Home page
Full article text
Link to the large image that represents an article
As soon as we are done with it we can publish our content. So templating step is not needed anymore.
Define your semantic content models
Our next step is to define semantic content models that will be used in our application. You can define your models two ways either via qraphql schema file on content service side or via Add-on package, in both ways you need to use qraphql schema language definition. We have chosen second approach and came to the following list of semantic content models:
Both semantic models will use the same published content. In other words, having semantic models feature we are not creating renditions on the ContentManager side anymore, instead you can create them in GraphQL.
Additionally in Tridion Sites 9.6 version semantic models will be created automatically during publishing process based on Content Manager schema definition.
Once we are done with defining custom models on GraphQL side we can move further and start doing our webapp.
Build your web application
React was chosen as a framework having the following dependencies:
Application will have following components to get and visualize data:
If you would like to play with it yourself:
I suggest taking a look at the presentation for Tridion Expert Summit related to this theme: