Tridion Conditions in Fluid Topics

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