Continuing the discussion from Future of Mosaic:
Modern page layout editors (think Wix, Weebly, Mobirise, Google Sites) have set new user expectations about page layout. I believe the concerns about Mosaic (or what comes after Mosaic) are therefore an important part of a bigger, holistic experience. However, we need to stay laser focused on the complete customer experience (CX), meaning the journey from "discovery" to a "customization deployment cycle".
Here's the CX Journey as I see it now (For the sake of simplicity, I'm leaving out the migration experience but it needs to be accounted for).
Case studies and features are valuable
Opportunity: an intro video would be good
Try and view use case demos: demo.plone.de or one of the others
A user is able to log in a see what it looks like to use Plone
Opportunity: A "guided tour" would help to point users in the right direction and showcase strengths in context
Content editing, page layout, management: demo.plone.de
This will probably be done at the same demo site, a few more "help" style videos would be good at this stage, they would make the distinction between the layout, editing and overall site management
Opportunity: I have more vague ideas, but I believe there is need for clear signifiers that support the distinctions of edit, layout, management. This needs more thought.
I strongly prefer some kind of cloud based install because it is faster to get started. In general, a fast, reliable install would be the goal here
Opportunity: Implement the fastest, most reliable installation solution for MOST of our target audience .
Customization and Deployment: docs.plone.org / training.plone.org ??
My general feeling here is that a user should be able to move from their first installation experience directly into customization, this is where TTW is valuable. There are still issues with TTW such as version control solutions and how to deploy, some solutions include "fat themes" but they still work best when customization is done on the filesystem
Opportunity: Complete the TTW experience, make it easier, make deployment and version control seamless.
I think Pastanaga is a piece of the puzzle, as it strives to provide a more consistent UI.
We should consider revisiting @djay's UX hitlist and see how it intersects with the suggested CX outlined above.