[MGNLSD-81] Use of proper nodetypes for all configuration data Created: 21/Nov/06  Updated: 17/Apr/13  Resolved: 17/Apr/13

Status: Closed
Project: Sitedesigner (closed)
Component/s: None
Affects Version/s: 1.0 Final
Fix Version/s: 1.2

Type: Improvement Priority: Critical
Reporter: Sameer Charles Assignee: Tom Wespi
Resolution: Outdated Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty

 Description   

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

Generated at Mon Feb 12 10:54:56 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.