Organizing documents in Sanity Studio for a custom page-builder schema type

Hey there! 🙂 I am using Sanity with NextJS and my goal is to configure Sanity Studio with page-builder functionality. My only challenge in doing this is that I have not yet found a logical/meaningful way of organising the documents created with my custom page-builder schema type. All my dynamic page documents are listed in the same document list regardless of where they belong on the sitemap. For example: pages that are subpages of subpages (like ".com/services/it-consultancy/data-analyst") end up in the same list view as top level pages (like ".com/services" or ".com/about"). This gets messy quickly with 30+ pages to be created.
How can I configure or customise Sanity Studio pane/list behaviour to sort and nest pages based on where they belong on the sitemap? Or do I need to think differently about this - is there an alternative approach that's better? Thank you very much in advance!
😊

I'd be curious about the hierarchy aspect of the project. We can definitely throw a couple of tips your way as we currently have a page builder built over here: https://www.userfylabs.co.uk/ in what I would consider quite a scalable way

Perfect, thanks for the assistance so far! 😊 As per now, all pages are being generated from the same schema document (page.js). For example, using the same page-builder schema template I want to be able to create a page for ".com/services/subpage/nested-subpage" and for ".com/services". I have not applied any filtering to deskStructure.js so all these page documents (from page.js schema model) are listed inside the same view, regardless of what is specified inside the slug field. But I will experiment with this, as proposed by

Can I ask - how do you define parent pages of a new page in your system? Would you recommend using an array of "references" to other page documents in order to create the path?

Hi we're actually in the process of figuring out the best way of doing this ourselves. We're using this tutorial here (https://www.sanity.io/guides/hierarchies-graphs-navigation#7a89a57242da ) to form our baseline. E.g dependent on how rigid your .com/services/subpage/nested-subpage is, this might work, however if you were going to create .com/*dynamic*/subpage/nested-subpage it becomes harder.
Something else that's going to help you for understanding current path is this:
https://www.sanity.io/plugins/better-slug

Also this might help as well.
https://gist.github.com/MastaAaron/24193bd83e1a41523d4d78b859e441c7

Yes, .com/*dynamic*/subpage/nested-subpage would be representative for what I want to achieve. Nice..! That slug extension looks quite useful indeed

Yes, .com/*dynamic*/subpage/nested-subpage would be representative for what I want to achieve. Nice..! That slug extension looks quite useful indeed

Thank you very much for that gist. Looks like this achieves exactly what I was looking to do 🙏

Hey Mikkel, didn't see this come through. Glad you're getting some progress. If it's any help that slug extension is pretty good but there's some issues with the length of the slug cutting off. That being said, this might help too: https://www.sanity.io/schemas/easy-peasy-url-slug-d2400b42
I've just popped it up earlier today because I was working on it this morning and it was driving me nuts.

Good luck on the project, and please let me know how you get on
🎉