It's a common pattern to create so called "Settings"-pages to make it possible for editors to fill out details used for various purposes on a site. These "pages" should be unique and only one instance of them should exist.
With the Sanity CMS it's possible to create these as actual Singletons, with a preset, known, key/id, and it's actually not possible to create duplicates of these.
Is there any way to do something similar when modelling content for Optimizely and this SDK/CLI?
- Mark a content type as a singleton?
- Make it impossible to create more than one instance of that content type?
- Make it easy to look it up using a known key?
It's a common pattern to create so called "Settings"-pages to make it possible for editors to fill out details used for various purposes on a site. These "pages" should be unique and only one instance of them should exist.
With the Sanity CMS it's possible to create these as actual Singletons, with a preset, known, key/id, and it's actually not possible to create duplicates of these.
Is there any way to do something similar when modelling content for Optimizely and this SDK/CLI?