|
Currently sitedesigner keeps all config data under the node with the same node types, If you look at the content from outside magnolia
there is no clear separation.
It would be best if you have custom node types to hold design properties.
Problem starts when you share content with other applications or view this content from different services like webDAV.
- currently there is no way to filter these nodes except if we know the exact naming convention
- what happens if you do full text search? again we cannot filter on node types so a usual search on mgnl:contentNode or mgnl:content will also find data
from design preperties
|