In the way it’s built now, yes. BUT What if a document is actually a Data View. Where you can set a database and it will create in line mentions of all the entities. Then you can move them around and change them. This is what Notion’s Wiki feature does, and i think its quite in line with making a Document View more around structured data. When you delete a sub page on the page, it actually gets deleted, not just the mention.
Use case: Your user guide
You probably have an automation running to make the bullets and inline mentions, but this could be a more robust solution if a document was a view, no? Just a thought, not sure how many other use cases there are to this, but I found it quite neat and a potential “solution” to the current document struggle.
Actually, that page is manually created (no automation) and we’re not too concerned if the order is different to the smart folder order.
Plus, there are some pages that we choose to not show, and some we choose to show in different places than the ‘parent’ as far as the smart folder is concerned.
There’s always a bit of a trade-off when choosing to go the ‘confluence way’ (i.e. nested hierarchy, any page can only have one parent) or going the ‘wiki’ way (any page is reachable from many places, via hyperlinking, and the tree structure is not applicable)
)