Menuitems of type "Content" should be converted to that content instead

[Bellfalasch]

This is a tricky one. But we see many not necessary contents in xp after migration. We find these to be menuitems of type "Content" in CMS with one selected content. They will be converted into a Landing Page with a section parameter/config with that content selected and that content being placed elsewhere. So, two contents in XP are created.

This is a opportunity to merge these into one, making the migrated data more XP-like.

If these items could be identified, making that selected content, like an article, moved and made into the menuitem itself, it would "clean up" the migrated data a lot.

However, respect needs to be given to the "home" setting for published content. For those cases, the menuitem needs to become a Landing Page in XP.

Not sure if this might be easier to create as a script running in XP after convertion, since the data is basically just "massaged" into a better shape.

[Bellfalasch]

Basically, after CMS2XP we'll have all these CMS menuitems of type "Content" migrated into this:

• 1 Landing Page with a Section option with one Content selected.
• 1 Content (the one selected) as a child, contains the actual data.

This old CMS-pattern is useless in XP, a more natural way to store data is to just keep the Content, not the Landing Page - but transfer any menu-settings from it to the Content itself (like show in menu, etc).