We've now learned how to override our studio's default structure and make a list of custom items. Now, let's look at how we can group our single documents in a manually-created group to open a secondary list for our settings.
If you're unfamiliar with setting up the Structure Builder API, be sure to check out the previous articles in this series.
Learning the Structure Builder API
This collection of articles will walk you through all the basics of using Structure Builder to create custom editing experiences.
- Introduction to concepts
- Set up structure builder in your project
- Create a link to a single edit page in your main document type list
- Manually group items in your main document type list
- Dynamically group documents in a document list
- Create custom document pane
We'll create a list of "Settings Documents" to allow our editors clear, structured navigation through all the different global settings our frontend will require.
Before we change our structure to group our new documents, we need to create two new singletons. Review this article's steps on creating a singleton and create a "Colors" and "Main Navigation" document. These can have whatever schema makes sense for your site (or just a title, if you want to get to this article's main topics). These documents should have a type of
navigation and matching IDs.
Now that we have more than one document governing our site's settings, it would make sense to group these into one pane instead of having three individual items in our first panel.
To do this, we'll change the
.child() method on our "Settings" list item to reflect a new list instead of a document.
// /deskStructure.js import S from '@sanity/desk-tool/structure-builder' export default () => S.list() .title('Base') .items([S.listItem().title('Settings').child(S.list()// Sets a title for our new list.title('Settings Documents')// Add items to the array// Each will pull one of our new singletons.items([S.listItem().title('Metadata').child(S.document().schemaType('siteSettings').documentId('siteSettings')),S.listItem().title('Site Colors').child(S.document().schemaType('colors').documentId('colors')),S.listItem().title('Main Navigation').child(S.document().schemaType('navigation').documentId('navigation'))])),// We also need to remove the new singletons from the main list...S.documentTypeListItems().filter(listItem => !['siteSettings', 'colors', 'navigation'].includes(listItem.getId()))])
Each singleton document is now a specific item under the "Settings Documents" list. They each also need to be removed from the main document type list, as well. To do that, add the singletons' IDs to the array used to filter the
Now that we have a manually grouped set of settings for our site, let's add a set of dynamic groups to filter documents by category or author.