General blog posts - All Comments

RE: Track your documentation metrics with Tridion Docs

A Reyes — Thu, 29 Jan 2026 18:26:08 GMT

Nice post, Andriy! The value of a good system or approach is often invisible, especially with managed content. With content reuse, for example, everything from content creation to translation to compliance is smooth(er) than a copy-and-paste approach. It's nice to be able to tangibly see how content is reused.

I also appreciate that the value (with AverageSalaryPerHour for example) is customizable to the organization. It's about looking at the whole system for awareness and not singling out individuals nor blindly incentivizing behaviors (e.g., publishing activity is a reflection of requests and updates and should be used to inform, but not be incentivized!).

RE: Community Ideas in the latest and greatest Tridion Docs 15.2 release

Alvin Reyes — Wed, 25 Jun 2025 21:43:20 GMT

Well done and congrats on both the release and implemented community ideas! [emoticon:c0a12e93d274496e82c557ae460d6b0f]

One benefit of this kind of transparency is a shared understanding of what was changed and why. I recall at least one (Tridion Sites) product feature that was changed a few times before we realized we were going back and forth between two alternatives. [emoticon:388f399768cb4510bc3d4c26fd6771f6]

RE: Protecting critical content and improving auditing with Delete plug-ins

Dipo Ajose-Coker — Tue, 10 Jun 2025 17:01:16 GMT

Hey Andriy, excellent post, and you have inspired me to create a What if...? blog post on this idea. I'll send you a link when it's published. In the meantime enjoy some other What if...? moments here: https://www.linkedin.com/feed/update/urn:li:activity:7338248784239284224

RE: Protecting critical content and improving auditing with Delete plug-ins

Alvin Reyes — Mon, 02 Jun 2025 19:45:19 GMT

Nice post, Andriy!

I like the idea of allowing deletion requests by users which can then be acted on by other users (or perhaps automated). I've seen a CMS setup (in Tridion Sites) where deletions were not allowed by regular users, so even accidentally copy-and-paste errors or test content needed a manual request to an admin to remove the content.

A real business requirement would be to be able to research and possibly restore any content that has been made public before. This often comes up with as part of a regulatory requirement to retain content that has potentially been seen by the public for a certain number of years. So being able to programmatically "catch" and handle a deletion request is a more nuanced and user-friendly approach to meeting the actual legal requirement.

And good reminder on the dependencies between publication, version, and language. Dependencies make deletions tricky. [emoticon:c4563cd7d5574777a71c318021cbbcc8]

RE: Structured for success - How Tridion Docs elevates Agentic AI retrieval

Alvin Reyes — Fri, 16 May 2025 18:09:05 GMT

Excellent explanation, Ben! I appreciate how you described the background and opportunity as well as provided tangible resources from the technical perspective. Just being made aware of the Model Context Protocol helps make a rather vague concept of "agentic" more tangible. I appreciate the protocol explicitly recognizes the importance of context, which is where (the lack of context) can cause so many issues with or even without AI!

RE: Structured for success - How Tridion Docs elevates Agentic AI retrieval

Arjen van den Akker — Fri, 16 May 2025 12:32:39 GMT

Thanks Ben, ths is a fabulous piece of writing. Much appreciate the clarity and depth...

RE: Tridion Docs OpenAPI: How to make the first call

Damian Jewett — Fri, 13 Dec 2024 22:33:55 GMT

I tried following all of these steps into order to retrieve a bearer token so I can access the OpenAPI, but when I try running my token endpoint in Postman, I always get "error": "invalid_client". The token endpoint I'm using looks like this: https://<docs cms domain>/ISHID/connect/token

I added the new service user in AM, then added a new user in the Docs CMS Settings. Then I added both the service user's name from AM, as well as the client ID to the user in the Docs CMS, under External ID, separated by a comma, similar to your animation.

Where can I find a sample POST request or other documentation that will clarify what all of the headers, body, etc. should look like in my POST request?

RE: A guide how to understand Tridion Docs’ new Reuse Metrics

Andriy Zhidko — Tue, 17 Sep 2024 11:53:12 GMT

Thank you to all who voted and participated in the exercise.

The right answer is: All 14; new 7; reuse 7; degree 50%

RE: How you could build a custom Web Application using Modern Authentication on Tridion Docs 15?

Alvin Reyes — Thu, 15 Aug 2024 19:00:12 GMT

Great post, thanks for all the detail [mention:4378d160b5934f2b9165c00a0567302b:e9ed411860ed4f2ba0265705b8793d05:label=Ivo] and the recommendations and caveats on how implementers could build on the Demo Application!

For use cases, I'd like to add that Access Management, in general, is great for helping secure and consolidate Tridion Docs-related applications on the backend ("back office") Content Manager side. Think custom reporting, batch tools, and things like alternative UIs for your writers, reviewers, or internal devs.

For a delivery-side application for your customers, consider a portal like Genius or the Dynamic Experience Delivery (DXD) Content Delivery (CD) API to build your own experience.

RE: Unveiling the Grid View: The Journey to Organize Space

Yasemin Aydos — Tue, 13 Aug 2024 07:42:06 GMT

Thank you Alvin! Yes, number of virtualized images are calculated in the client-side. Screen resolution and browser size percentage also effective on that, a virtualized grid renders the visible part and an extra row which is the first row that you will see when you scroll down. If we take the example in screen shot, we are seeing 15 images in 3 rows, in addition to those next row also loaded to make it ready for scrolling. Lets say next row is a full row with 5 images, then 5 more images are loaded and the rest are virtualized.

Hope that explains the virtualization behavior of our Grid View.

RE: Community Ideas in Tridion Docs 15.1

Alvin Reyes — Thu, 08 Aug 2024 18:00:56 GMT

Even better than "quality of life" improvements are ones inspired or recommended by the community. [emoticon:0f36700dfeb3494fa10d47dd9e1f90a1] Nice improvements!

RE: Unveiling the Grid View: The Journey to Organize Space

Alvin Reyes — Mon, 05 Aug 2024 22:51:46 GMT

Nice post, Yasemin! Great focus on performance with some flexibility with the Grid resolution setting. We'll want to be sure to cover the setting in new implementations and upgrades.

Are the number of "virtualized" images calculated client-side somehow? Like does screen resolution, browser size percentage, or resizing the browser impact what's virtualized (automatically)?

In the example screenshot I see 15 images. Would those be the ones virtualized or are there more beyond just what's seen, if that makes sense?

RE: A guide how to understand Tridion Docs’ new Reuse Metrics

F. Gress — Thu, 06 Jun 2024 13:57:57 GMT

I'm sorry, I'm trying to understand what is going on here.
Is "Tridion Docs’ new Reuse Metrics" an actual existing new feature (in v15), or one still being proposed/explored/developed?
It seems like this is just a philosophical debate about the formula.
Are we voting on the formula?

RE: Community Ideas in Tridion Docs 15.1

Julia Ziobro — Wed, 05 Jun 2024 17:10:13 GMT

I wish I could give this article five thumbs up and I'm sorry my company can't devote the time to upgrade until September! We will benefit from nearly all of these improvements, especially Where Used, focus on new items, and the Draft space fixes/changes.

RE: A guide how to understand Tridion Docs’ new Reuse Metrics

Andriy Zhidko — Wed, 05 Jun 2024 16:43:47 GMT

Hello [mention:7b0a723c3e724114b8e0c21a920e8c71:e9ed411860ed4f2ba0265705b8793d05]

Thank you for taking the time and read the blog.

Let me cover your questions one by one.

1. In our example and the way we calculate the reuse degree, we can calculate the relative reuse degree for Q1 and Q2 separately.

In case a reuse degree is required for a time interval that includes Q1 and Q2 then publications Z and Y will be included.

Could you please elaborate more regarding the second part of the question?

2. When new topics are added to Z and Y in Q2 this information will be logged and counted during the calculation process

Important to note that the timestamp when publication is created does not influence the calculation process, we are not aggregating data around this time stamp. A time when a topic is added to publication is important (and is being tracked) since this is the fact of reuse. These facts of reuse on a timeline can be calculated for a given time interval.

3. In our initial implementation indeed you will not be able to see which topics are reused. But this can be improved in future versions.

You have an option to see a system-wide reuse degree or filter by a Product that is metadata assigned to Publication. A Group of Products can represent a Business Unit.

I will cover UX capabilities in the following blogpost.

4. Content references as I explained require an effort to maintain them centrally that can be even higher than the value of reuse of the parts of the content.

The granularity of reuse that we chose is document level while for content reference it is only parts of the document.