List View on Any Arbitrary Page

[Myster]

We would like ListView to be arbitrarily available on any node.
Probably to any content editor (although possibly restricted to admin-level users)
Chris gives this use case on the forum:

My use case is that I have a client with a particularly large number of child pages under one section of their content tree and I think browsing this would be more suited to the listview.

I don't want to change the doc type to listview because that would affect large parts of their content tree which we don't want to display in that way.

My use case is similar:

We like to build websites mostly from a generic page type, variability comes from the block grid.
having to switch doctype (which is now very hard) seems like the wrong solution to this problem.

This should include the way the content picker treats list view with pagination and search.

[Myster]

Perhaps the tree should make an exception for the Current Page so as to be able to access any children.

▶️ Foo Page set with listview (collapsed)
🔽 Bar Page Set with listview (expanded)
  🔽 Current Page (expanded but starts collapsed)
    ▶️ Child of selected (can be expanded too if it has children)
  ✳️ _Other_Children_ (click to see list view in right pane)
▶️ Some other page

Perhaps the listview should not be a 'tab' or 'app' on the content rather it should be a 'faux-node' on the tree, and when clicked it opens in the right pane without any content 'app' to confuse navigation.

▶️ Foo Page set with listview (collapsed)
🔽 Bar Page Set with listview (expanded)
  ✳️ _Children_ (click to see list view in right pane)
▶️ Some other page

[hfloyd]

@Myster - You can add a property to a doctype with a Listview DataType without setting the Content Type's "Listview" property. I do this frequently. Then the tree is unaffected, but you have the display and sorting options available on the "parent" node.

DocType Configuration:

Back-office UI: