I've discussed some changes to the Apps screen with Pascal lately. One thing we'd like to see is a clearer distinction between apps for editing content (typically content apps) and apps that publish such content.

More specifically, I propose we change the Apps screen in two steps to realize this idea:

1. Add example content apps for "News", "Products", maybe "Events", while still keeping the "Contacts" apps. The content of these apps must be used by the demo project in order to unleash its full potential.
2. Assemble content apps under the "Edit" group and add a second group (e.g. "Site" or "Gather/Collect/Assemble") for assembling such content on "Pages" using "Assets".

The attached, two screenshots show both steps.

We originally wanted to introduce such a change with 5.3, but the feedback I got was consistently sceptical to right out negative. The distinction between "page" and "non page" apps seems to feel too artificial still.

I've thus decided to split this idea off the rest of the changes (mentioned in MGNLUI-2843) and only introduce them once we have a clearer idea about and an explicit focus on content pools and content apps in one of the releases following 5.3.

My gut feeling also tells me that especially the second change would be best done once we add "virtual trees" to represent sites.