Details
-
Improvement
-
Resolution: Unresolved
-
Minor
-
xCM 6.0.0
-
None
Description
After some discussion, it looks like being great to be able to mask certain fields according to the container usage.
For instance we are often creating a lot of different CND because we only want to list:
- a single big text on such a ctnlist
- a big text and a title on another ctnlsit
- a big text and a title and an image on a third one
- etc...
Finally all these "objects" are not designed after a semantic need but after some display and rendering consideration. This is a totally wrong approach. All these objects could perfectly be defined on the same "article" content definition (then easing reuse, copy-pasting, ...).
And what the template developer wants is to only display some fields to the author and perhaps mask opitnla or not required one (because not used on the current page view). so a "masking" option which would "hide" some field in the container engine would be nice and would simplify the trends which consist in multiplying the number of content definitions according to each page template rendering needs.