Ability to configure a model as a “single instance model”.
Would be useful for content that isn’t meant to be duplicated, such as:
The UI should be updated to make the edition of single instance models more user friendly.
Not sure if it has any impact on the API, probably not.
Thanks! We have this on the radar and will be working on it later this year.
We have a lot of general translations that are not part of e.g. listings - for example buttonSave buttonCancel - The idea of the single instance model might solve that requirement!
@Michael Lukaszczyk Any ETA on this?
We’ll be soon able to share a more detailed roadmap. 👍
Any news about the release of this feature?
Need this!
@Cooper the transit enjoyer can you elaborate on your use case? This feature is planned to be worked on soon but we’d like to understand more use cases. There are several content structure improvements in the pipeline, such as modular components.
I’m running into a need for this now. On a site whose content is served from GraphCMS, I’d like to have a navigation bar, controllable in the CMS. I don’t want to create a “Navigation” model, because I don’t need multiple navigation bars. I want just one navigation bar, that could have a one-to-many relationship with Nav Items.
This would be great to have. My use case: I have a “photos” section on my website (https://www.jussivirtanen.fi/photos). For that, I had to create a “Gallery” model and add one instance with a title of “Photos” (as I thought it could be vague to have the same name for the model and the one piece of content I needed).
Then in my query, I need to query all galleries with the title of the one gallery I want to fetch. This is not a big deal, but having single instance models would remove the extra step required to create and fetch the content.
Can anyone from Hygraph give any ETA on this? I’m currently in a process of choosing CMS for a huge project. I need this feature and would like to know what’s the status of it.