[PAGES-1179] Upgrade Pages Visual editor Created: 18/May/23  Updated: 13/Sep/23

Status: Open
Project: Magnolia pages module
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Mykola Assignee: Unassigned
Resolution: Unresolved Votes: 1
Labels: None
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)
Epic Link: AuthorX improvements
Team: AuthorX

 Description   

Upgrade Pages Visual editor

Problems:
1) Current Pages app requires refresh after saving dialog
2) Each action fires loading state (even simple click or scroll, which sometimes can take couple seconds)
3) Dialog hiding page/component which we're editing (also can't move and resize)

All these problems together make user experience feel slow and outdated.
New generation editors like Builder.io, Gutenberg, Divi, Elementor, WPBakery all using client side UI to update data and edit things on a page. Sometimes even without opening dialog (eg. plain text or image)

Proposition:
1) Instead of [save -> refresh -> render with new state] consider [save -> update DOM with new state -> update JCR via REST]. Possible risk: lose some of the info from server side request.
2) don't fire loader on each click/scroll/etc.
3) Make dialog a sidebar instead of modal + make it resizable/draggable/collapsible/etc. Many competitors (like Divi) choosing sidebar because it's not hiding page when editing. Combining clear visibility with live updating via REST can make editing much faster and more user friendly.


Generated at Mon Feb 12 06:25:50 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.