Web Content Management Software Resources

Hi! This is actually possible today using the Structure Builder API. You can follow this tutorial to set it up: https://www.sanity.io/docs/create-a-link-to-a-single-edit-page-in-your-main-document-type-list The reason we have gone with this approach is that in many cases you want more instances of your “singleton documents” once a project matures and grows. For example, you have a “settings document” for a website, but then you want to add a second website property to your Sanity project. Then you can opt out of the singleton configuration and support multiple settings documents with the same fields.

Hi! There are many ways of localizing content, regardless of where you plan to present it. I would start by reading up on the documentation to figure out what type of localization of the content model suits your use case best: https://www.sanity.io/docs/localization You can also check out this tutorial for Gatsby and Sanity specifically. https://www.gatsbyjs.com/blog/2019-03-01-localization-with-gatsby-and-sanity/ But it pretty much boils down to that you get content on localized fields in Gatsby's GraphQL API. Best of luck!

Hi! Our JavaScript client has always supported full CRUD operations against our APIs. You can check out the documentation here: https://www.sanity.io/docs/js-client Let us know if this wasn't what you were thinking of!