• State Not Answered
  • +1 person also asked this people also asked this
  • Replies 2 replies
  • Subscribers 138 subscribers
  • Views 96 views
  • Users 1 member is here
Options
Related

Tridion Conditions in Fluid Topics

Jonathan Chandler

Hello everyone,

Has anyone successfully published content that includes multiple conditions (for example, customer X, customer Y, internal, external, series X, series Y, etc.) from Tridion to Fluid Topics and then had Fluid Topics segment or filter that information effectively?


In particular, I’m interested in learning:

  • Whether conditions were resolved in Tridion at publish time or passed through to Fluid Topics and managed on that side.
  • How conditional content was handled to avoid content duplication or condition explosion
  • How Tridion metadata and condition values were mapped to Fluid Topics facets, tags, or profiles
  • If a better long-term approach would be to scrap conditions and move to DITAVALS

If you use Tridion conditions and also publish content to Fluid Topics, I'd appreciate hearing how you do it, what works, what doesn't, and any best practices or resources that may help.


Thanks in advance for any insights you’re willing to share.
emoji
Rate translation
×
Suggest better translation
×
Parents
  • 0

    Hi   

    We also use conditions in Tridion Docs and publish to Fluid Topics.

    We have been thinking about being able to publish to Fluid Topics with all conditions applied and having Fluid Topics filtering on the conditions. We talked to Fluid Topics about this a few weeks back, and they seemed interested to move in this direction. As I understand they can now filter out topics from a publication using metadata, but not on a lower level (segments inside topics) yet.

    One problem I see (for us) is that our conditions do not match our metadata 1:1, so this might be one challenge. Also, in the output we send to Fluid Topics the conditional data is not included. However, this I think, is just a matter of configuring the files so that the conditional data is included from Tridion Docs. Then I guess Fluid Topics needs to figure out how to filter on this information. I do not think that it is a good idea to move from conditions in Tridion to DITAVALS. Conditions are very helpful when creating content and reviewing it in Tridion Docs. 

    Kr, Pia
    emoji
Reply
  • 0

    Hi   

    We also use conditions in Tridion Docs and publish to Fluid Topics.

    We have been thinking about being able to publish to Fluid Topics with all conditions applied and having Fluid Topics filtering on the conditions. We talked to Fluid Topics about this a few weeks back, and they seemed interested to move in this direction. As I understand they can now filter out topics from a publication using metadata, but not on a lower level (segments inside topics) yet.

    One problem I see (for us) is that our conditions do not match our metadata 1:1, so this might be one challenge. Also, in the output we send to Fluid Topics the conditional data is not included. However, this I think, is just a matter of configuring the files so that the conditional data is included from Tridion Docs. Then I guess Fluid Topics needs to figure out how to filter on this information. I do not think that it is a good idea to move from conditions in Tridion to DITAVALS. Conditions are very helpful when creating content and reviewing it in Tridion Docs. 

    Kr, Pia
    emoji
Children
  • 0 in reply to Pia Bäckman

    Hi Pia,

    Thanks for your response. This is very helpful. Doing all of the filtering on the Fluid Topics side is an interesting idea. Like you, our conditions and our metadata aren't a 1:1 match, so this would require some configuration changes. This would also only solve part of the equation since we're applying conditions to elements smaller than a section. In our case, I think a part of our solution here involves a cleanup of our conditions and a more cohesive strategy for when we use conditions instead of conreffing or using keys.

     

    Thanks again for your input. Good to know we're not the only ones working this way, and that there may be solutions on the horizon!
    emoji