It would be great to be able to view your image library from the keystone CMS. For example if a user would like to use an already uploaded image/document in multiple posts etc.

From https://github.com/keystonejs/keystone/issues/428 I don't think this has been implemented yet, and would like to see it done. Mainly, it would be nice to support nested pages and have a dropdown menu in the navbar. (The navbar in the live site, rather than the admin UI) I've implemented something myself to allow one-level of dropdown menu. Where we currently compare key and section, I have added subkey and subsection fields, then edited the default template accordingly. My navLinks in middleware.js looks like this: http://pastebin.com/qgELHZuR Happy to PR this implementation (which you can see live here: https://www.students4students.org.uk/ ), but it's perhaps a little too simplistic?

Right now, if a user edits published content, the changes go live immediately. Frequently, an editor may want to change an already published piece of content, and want to save their changes to either preview or finalize their content and publish at a later date. Two related issues, #320 and #608 could then allow users to preview unpublished/staged content prior to publishing. Source: https://github.com/keystonejs/keystone/issues/909

A very important feature for any CMS. We're hard at work towards this and it's firmly on our roadmap.

I am trying to upload a csv file via an upload button in Keystone Admin UI to insert the content of the CSV file into the mongodb database. For example, I have a blog post CSV file and I want to upload it to the Post table in the Keystonejs database. Source: https://github.com/keystonejs/keystone/issues/1434

https://github.com/keystonejs/keystone/issues/150

https://github.com/keystonejs/keystone/issues/67 https://github.com/keystonejs/keystone/issues/2358 https://github.com/keystonejs/keystone/issues/1522

https://github.com/keystonejs/keystone/issues/84

If multiple roles were available in the admin UI, it would open the door to create a much more robust CMS system, and would pave the way for the following: Restricted access on certain fields/document types (great for companies that trust some employees with only specific tasks, but still need them to be administrators). This could be used two ways, one would be to hide fields/documents, the other would be to make them visible but not editable. Groups to place admin users in to restrict their access/open the door for a document pipeline. Document pipeline for things that need to be approved by multiple groups or individuals before going live. The default would be no additional approvals, save makes the information live, but an n-length chain could be created forcing a new document to pass through one or more group/individual approvals before it becomes live

Would be useful to have select fields that can generate their values dynamically based on the value of other fields in the item (or an other condition). For example, a list of cities that depends on the country selected in another field. Not sure how this would interact yet with features like the ability to pluck other values from the currently selected one, may need further investigation to ensure full support (or a new field type). Source: https://github.com/keystonejs/keystone/issues/298