Issue Task Closed

#103118Re-invent PagePositionMap

Andreas Kienast 02/14/24, 13:57 updated 09/15/26, 20:36

Description

To give editors a better experience, the existing PagePositionMap needs to get reinvented. Its code is dusty, hard to read and the implementation is rarely used in Core.

For wizards that let an editor choose a page position, we need a new approach that may base on the new page tree.

Ideas

Build a new variation of the page tree that renders placeholders between nodes.
Drawbacks:
  • 100% increase of needed space for the tree to render
  • May look weird in wide areas (e.g. modals)
Combine the existing page tree with the behavior of the current PagePositionMap. The usage may “feel” like using a Link Browser.
Drawbacks:
  • PagePositionMap is still alive
  • Navigation may become clunky, as PagePositionMap allows to switch to another page

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.