Define singleton objects

Not everything exists in multiples. In the CMS world there exists objects that are only “singular”. Everything on this page could be defined as one object called HomePage.

Right now, there is no data structure that represent a HomePage object above. I need to do an ugly hack and make it a list.

[JedWatson]

I’m pretty sure I’ve mentioned this elsewhere, but just to leave a note here as well: This feature is high on the list of things we’ll be addressing once 0.4 is released and stable.

The official implementation will be a streamlined workflow around the hacks that users have already established*, with a specific UI area to make editing singletons easy. We’ll open issues relating to how that’s planned to be implemented (as well as publish the designs we do for how it will work) when it’s coming up for active development.

We feel the pain of not having it (I’ve personally needed it on a few projects) but the call has been to stabilise the new React UI and Field Type components first, which despite the delay (it was a huge amount of work) I think will be the right one in the long term. Migrating data from workaround implementations to the official solution will hopefully be quite straightforward.

* one potential major difference may be that we keep all “singleton” objects in a single MongoDB collection and offload the schema completely to Keystone Lists, rather than wrapping Mongoose Schemas under the hood. Lists have matured a lot in the last few months and I think that’ll be viable, and not having a collection for each singleton is definitely preferable. Again, this will be finalised when the feature is up for development.

[flzozaya]

It’s now been over 1 year and 9 months since @JedWatson commented about this feature. Is there any progress on this??