As a developer, I can configure multiple apps which function similar to the stock pages app, it has a "Page Editor", so that I can meet the requirements of the authors.

With 6.2 it became much easier to have multiple pages apps, so much so that the Pages app framework (Extension) was retired. However there are several issues which still cause obstacles. These obstacles should be removed.

To consider and evaluate:

• Can be accomplished with configuration.
• Can freely choose workspace name.
• Can use all personalization features in the pages app.
• Can use the "preview as visitor" app.
• Can freely choose nodetype for pages.

Context

One of the reasons that people choose Magnoila is the pages app due to it's WYSIWYG editing paradigm. They also like that Magnolia allows one to separate content editing into different apps for different types of content. They want to do this with the pages app editing. 

For example some customers create "category pages" in a separate app from the Pages app - because they are not part of a heirarchy of pages - they are loaded dynamically when customers request a category in an ecommerce shop.

Or sometimes customer will use an additional pages app to craft re-usable chunks that can be included in multiple pages, kind of like a "tour" in a content app could be included in multiple pages. 

Logically, it makes more sense for these things to be in seprate apps, since they are not really pages.

Considered - but not included

• Headless personalization can correctly retrieve personalized content from the apps.
• Using personalization in other apps.

Notes

This is related to:

Campaign Manager (Extension)

Pages app framework (Extension)

Creative Fragments (Planned)

Internal Reference

https://wiki.magnolia-cms.com/display/PMTEAM/Page+Editor+in+Any+App+-+Product+Sheet

https://magnolia.productboard.com/portal/1-magnolia-roadmap/tabs/fe503919-6dd8-43b7-bdca-e60dced2babd/features/14299156/portal/expanded