Tridion Blog

Customer Advocacy for Tridion

Alvin Reyes — Mon, 24 Feb 2025 23:21:36 GMT

It's been over two decades in the communities of Tridion, across Tridion Sites and Tridion Docs, back to when the products had different names. We've asked and answered questions, submitted product enhancements, and written hundreds, if not thousands...(read more)

Re-platforming your structured content into a new CCMS (podcast)

Wali Naderi — Thu, 03 Nov 2022 15:27:47 GMT

Introduction and background On Sep. 26, 2022, Scriptorium conducted this podcast ‘Re-platforming your structured content into a new CCMS’ with Chip Gettinger, VP – Of Global Solutions Consulting at RWS. Chip was invited to speak abo...(read more)

How taxonomies from WAND can kickstart semantic AI projects in Tridion?

Wali Naderi — Thu, 29 Sep 2022 14:03:26 GMT

On July 14, 2022, Semantic Web Company (SWC), WAND, and Tridion teams convened to discuss and understand how Pool Party (SWC product) taxonomies can kick start semantic AI projects in Tridion Sites and Tridion Docs. And also discuss the expert-curate...(read more)

Leveraging the power of knowledge graphs in technical documentation

Wali Naderi — Thu, 29 Sep 2022 13:15:06 GMT

RWS and Pantopix conducted a joint webinar on July 12, 2022, to discuss taxonomies and knowledge graphs, one of the top trends in applied artificial intelligence today. It covered the benefits of applied AI in technical documentation and the various ...(read more)

Optimize your field service efficiency with Dynamic Content Delivery

Wali Naderi — Mon, 29 Aug 2022 13:43:48 GMT

On April 25th, RWS and its partner, Fluid Topics held a session to educate their potential users on the ways in which their combined solution can deliver efficiency and cost savings to field service organizations. Both agreed that the content (core) ...(read more)

Manage the content’s performance efficiently with Tridion CMS and Content Bloom

Wali Naderi — Mon, 29 Aug 2022 11:38:21 GMT

On June 30th, RWS Tridion and its partner, Content Bloom, held a webinar highlighting how their combined solution can deliver content insights and help enterprises optimize and drive max ROI from their respective content. Pankaj Gaur, Director at Co...(read more)

Things You Can Do with SharePoint in Tridion Sites and Docs

Wali Naderi — Mon, 28 Jun 2021 14:48:00 GMT

Things You Can Do with SharePoint in Tridion Sites and Docs Today, about 190 million users from more than 250,000 organizations across the globe use SharePoint to store, organize, access and share data from different devices, create intranet team sit...(read more)

Seamless App Development and Content Delivery with Containerization and Microservices

Wali Naderi — Wed, 16 Jun 2021 12:27:00 GMT

Seamless App Development and Content Delivery with Containerization and Microservices Most of the modern application development involves use of a combination of different technologies. And hence application development is linked and dependent on the...(read more)

The #TridionMakesItEasy challenge

Denis Davies — Tue, 10 Nov 2020 09:39:00 GMT

Enter our competition for a chance to win a $200 voucher and a gift bag of SDL goodies. Share a post on LinkedIn, Facebook or Twitter between now and the end of the Tridion Expert Summit telling us how Tridion has made your life easier. It’s th...(read more)

Introducing SDL Tridion, the Intelligent Content Platform

Arjen van den Akker — Thu, 16 Jul 2020 12:04:00 GMT

In the press release that we issued today you will see that we’ve introduced the next generation of our intelligent content platform – SDL Tridion. It’s our unique way of bringing together information inside and outside your busines...(read more)

SDL Tridion DX Provides a Single Solution

Lennert Fransen — Thu, 31 Oct 2019 13:08:00 GMT

SDL Tridion DX Provides a Single Solution for Brands to Create, Manage, Translate and Deliver Content to Customers, Partners and Employees. October 9, 2019, Maidenhead, U.K. SDL (LSE: SDL), a global leader in content creation, translation and de...(read more)

SDL Calls On Brands to Rethink Global Content Strategies as the Future of Content Becomes Autonomous

Denis Davies — Wed, 20 Feb 2019 11:38:00 GMT

Hi all,

Yesterday we issued the below announcement to media, calling on brands to rethink their current global content strategies, and prepare for a digital future where content supply chains are autonomous, machine-first and human optimized, and capable of delivering any type of content to worldwide audiences.

https://www.sdl.com/about/news-media/press/2019/rethink-global-content-strategies.html

Thanks, Denis

Six Ways to Engage With Worldwide Audiences in 2019

Denis Davies — Thu, 24 Jan 2019 13:50:00 GMT

Hi all, this morning we announced six recommendations for businesses looking to engage with worldwide audiences in 2019.

The recommendations are based on a Forrester Consulting study, ‘Today’s Content Supply Chains Prevent Continuous Customer Journeys,’ which looks at the content challenges facing companies when building a global customer experience strategy.

Here's a link to the full release!

https://www.sdl.com/about/news-media/press/

Denis

New release SDL Tridion DX - Launched

Pramod Mandhre (former member) — Thu, 08 Nov 2018 08:38:00 GMT

On Wednesday (Nov 7), SDL announced a new release of SDL Tridion DX, which is based on a latest release of SDL Tridion Sites 9 and SDL Tridion Docs 13 SP2. Both are capable of publishing through a shared online delivery stack called Dynamic Experience Delivery (DXD). It is accompanied by a new version of DXA, which brings together two separate DXA streams.

The SDL Tridion DX focuses on “Continuity of Experiences,” which refers to the platform’s ability to bridge the pre-sale, sale and post-sale phases of the customer journey. In particular, this release of SDL Tridion DX enables companies to better blend in-depth product information in the customer’s overall journey.

The key new features of SDL Tridion DX are:

The release of SDL Tridion Sites 9 and its Dynamic Experience Delivery (DXD) capabilities enable dynamic content mashups between marketing content & product information using a taxonomy-driven approach.
The ability to share SDL Tridion Sites taxonomies with SDL Tridion Docs so content across both systems can be tagged identically.
DXA 2.1 which brings together the regular version of DXA from SDL Tridion Sites with the self-service portal – DXA for Dynamic Documentation – from SDL Tridion Docs.
Fully functional Experience Optimization based on Elastic search. It provides much faster and simplified implementation and requires a lighter infrastructure footprint.
Specific new features for SDL Tridion Sites 9, including editorial improvements (in particular: Regions) and other technology updates.
Support for DITA 1.3 in SDL Tridion Docs 13 SP2.

Visit our SDL Tridion DX webpage to learn more about our latest product updates.

To learn more about our latest announcement, read our New SDL Tridion DX Release Transforms Content into Digital Experiences.

Also for great product videos check out our videos page!

Bootcamp Exercise: Content Models in Sites and Docs

Alvin Reyes — Thu, 12 Jul 2018 23:17:00 GMT

I'm back from a Partner Bootcamp, where I created the following ice-breaking exercise to help Sites and Docs practitioners understand how their respective content models compare. For more about boot camps read my last post. Otherwise, read on to see how you might adapt this exercise for your next presentation.

Step 1: Volunteer or Voluntold

First I asked two volunteers to kindly come up to draw and answer a few questions. These can be anyone familiar with at least the main concepts in Sites and Docs.

Step 2: Definitions

I then had them start with the basics with these questions:

What is the basic content-containing element in the software?
What is it stored as?
What defines its definition?

Both Sites and Docs store modular pieces of content as XML, however, Docs leverages the DITA OASIS standard to offer a bit more "in-content" structure such as embedded and conditional content as well as references.

Step 3: Content Types

We then compared common types of content between the systems with these prompts:

Based on these definitions, what are the basic types of content you see in implementations (e.g. article or topic)? Write some examples.
Do you see any bad practices or types that shouldn't be used by customers?

For example, a Docs setup might have topic types such as Task, Concept, or Reference, whereas Sites might have schemas such as Article, Blog, Carousel, Link List, and so forth.

I joked about some infamous schema and item names such as "Article 2," "Article-do-not-use," and "Home Page (Old) Old."

Step 4: "Pages" and Outputs

We then drew how content comes together and how the source content is transformed into an output.

We ended up with logos, topics, banners, and lists across the two drawings.

Both Sites and Docs can render content into nearly any machine-readable format imaginable. Though their content storage attempt to both be semantic and agnostic of the rendering, Sites does offer a selection for editors to choose a different "template" to change the layout and/or rendering of content.

Step 4: Variations

This is where the difference between Sites and Docs becomes apparent and was the conclusion for my quick-and-dirty on-the-spot ice-breaking exercise.

Though we didn't actually draw Publications, BluePrints, or Baselines this last part explored and discussed how both Sites and Docs handle variations of the same or related content in really unique, powerful, yet complementary ways.

Variations Within a Sites Publication

Within Sites, the delivery side is relatively agnostic or unaware of the history of any piece of content. The delivery site shows the "latest-and-greatest" published version of an item. However, BluePrinting enables the combination of shared, global content with local control or localizations of variations.

The BluePrint is set up for editors and editors have the choice to tweak and adjust (localize) content in the given context of their Publication. And any given Publication may have a mix of shared and localized content based on the use case, which might be source content translated into a specific target and/or content localized for a given market or even channel, device, or customer segment.

Variations Across Docs Publication

Docs, however, allows technical writers the ability to create and explicitly use different (historical) versions of an item as well as branch those versions. The same topic may appear in different Publications but might have different versions, related to each other through a shared GUID. A publication's Baseline determines which versions of items resolve for use in a given published Publication.

The takeaway is that both Sites and Docs handle variation in content, but almost across different dimensions leveraging BluePrinting with inheritance/localization in Sites versus Baselines with versions/branching in Docs.

I wrapped up the exercise, which was hopefully a nice break from the slides.

Your Turn

Feel free to try this exercsise or a variation of it at your next knowledge sharing session or presentation. Previously I've had my workshop participants predict the Sites Content Manager, which seemed to have gone well. Others I've had enact the concept of Component Templates, which I will never do again. Your mileage may vary but I'd love to hear how your next exercise goes.

Have favorite drawings or diagrams of the Sites or Docs content models? Did I explain things correctly or is there a better description or good list of terminology you'd like to share?

Leave a comment and perhaps post some examples. I'm also looking for others to start exploring, sharing, and explaining the intersection between Sites and Docs! Bloggers welcome!