Provide a page object which enables page editing.

Use case: Page editor

The "main" object PageEditor
It represents the detail-subapp, I assume could be for both "states" preview-mode and edit-mode.

Not yet sure which other page object should provide the page_editor page_page.
Depends also a bit on what the return type of its methods should be to enable a "fluid API".

It could be the "root PageObject" which provides the PageEditor, given the pages app was opened. In this case PageEditor would extend ContentApp.

Required functions

In summary, the functions should enabling the creation and manipulation of components within areas.
Add, edit, move (comp).
It most cases it is hopefully sufficient to just click / select on bars of areas and components.
A tricky part is the "move component". Not yet sure how we could do that.

select area

Select an area by its given name.

PageEditor selectArea(String areaName);

Select component

Select an area ... by ... hm ... that's the tricky part. t could be:

• a number,
  • an int starting by 0 following the order (within an area ...)
  • ...
• a String
  • The (technical) node name such as "O", "00", etc. pp
  • a (sub)string of a text inside the comp. (e.g. the header)
  • Problem here: not every component has text. However, for testing reason this could be sufficient

Ticket requires further refinement. To be discussed with Federico.