Hi @NickBourlier, thank you for this RFC. Folders seem to be a useful feature for organizing content, but the lack of API support for the new content types is increasingly becoming a problem for our users. We offer apps that allow users to interact with content trees and we are unable to display content hierarchies below whiteboards, databases, smart links, and folders.
Nesting content below non-page content is probably not that common, but I’m sure this will change when folders are available and users no longer have to create empty “container pages” to structure their content.
To make our apps compatible with these changes, we need API endpoints that return all children of a specific piece of content, regardless of their type. Unless I’m missing something, such APIs are not yet available in either REST v1 or v2.