Conditional Content Tagging
Hello!
We have teams which we are migrating over to Optimizely SaaS who have a need for conditional content tagging. What I mean by that is when a category is selected on a block, it shows specific fields that are unique to that category. A category could have 0 unique fields or multiple unique fields.
This is important to help prevent our content model or blocks from getting "messy". The only way around this, that we've found, would be to either list out all available fields, which would be confusing to content authors, or have a unique block per category, which requires managing a large number of potential extra blocks (instead of max 1 per team, it could be 5,10 depending on category count).
If I am wrong regarding current available solutions or you need any more information on our use case, please let me know. Otherwise, we hope this could be implemented in the future.
Thanks!
-
Craig Mazer
commented
Strong +1. Concrete example: our dynamic table component offers Calendar and Tuition variants, but the date fields stay visible even when Tuition is selected. Native conditional/dependent field logic (show/hide fields based on a selection within the same form) would let us avoid content-type composition workarounds and keep the content model clean.