[MGNLPN-167] Move "Preview as visitor" action from page editor to page preview Created: 12/Jun/14  Updated: 16/Jun/14  Resolved: 16/Jun/14

Status: Closed
Project: Magnolia Personalization
Component/s: Integration
Affects Version/s: None
Fix Version/s: 1.0

Type: Improvement Priority: Blocker
Reporter: Andreas Weder Assignee: Roman Kovařík
Resolution: Fixed Votes: 0
Labels: next, usability, ux
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:

 Description   

I've found during my tests that the "Preview as visitor" action in the page editor is actually in the wrong place. It should be located in the page preview, much for the same reasons that we also have moved the "choose audience" action there.

The visual page editor is only about editing the page. Once you're done, you verify your changes in the preview, choose an audience and check whether that works well for all your visitors. Similarly, both "choose audience" and "preview as visitor" should be accessible to reviewers as well. Moreover, it's bad usability due to the risk of accidental edits that you have to "edit a page" in order to get access to the "preview as visitor" action.

Please move the "preview as visitor" action from the page editor to the page preview in Pages. Move it into the same group as "choose audience", place it right below that action.



 Comments   
Comment by Philip Mundt [ 16/Jun/14 ]

Installation fails with

Could not install or update personalization-preview-app module. 
Task 'Order 'previewAsVisitor' actions' failed. 
(PathNotFoundException: /modules/pages/apps/pages/subApps/detail/actionbar/sections/pagePreviewActions/groups/editingFlow/items/previewAsVisitor)
Generated at Mon Feb 12 06:34:58 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.