Keystone-classic: Current status of the project

[ttsirkia]

I've been eagerly waiting next beta releases or even the production ready Keystone 4.0. However, it seems that the repository has been inactive over a month. I'm just wondering what is the current status of the project. Is there still something happening behind the scene or is the project abandoned as it very unfortunately looks like?

[wangshijun]

same question @JedWatson

[webdesign7]

I just started using keystone ( awesome cms ) .. and really would like to see status .. Thanks

[ghuroo]

I use it as my framework for most of the work I do.
So I would love to see it alive, even if with small improvements each time.

Also plan to help development as soon as I finish learning react.

[lucasvall]

Yes, any idea what is going on? No commit in 2 months? Anybody knows @JedWatson? No activity in his Twitter either (https://twitter.com/jedwatson?lang=en).
May be @Noviny has updates (I have seen him committing and also part of KeystoneJS organization)?
@bladey , @grabbou , @jstockwin , @LennyBoyatzis ? They all are part of the Keystone JS too.

[JedWatson]

Hey everyone, sorry for the delay between updates. We're doing a huge amount of work behind the scenes at the moment, and I'll update in full when we've got more information. I've also been taking some time off for personal reasons lately which hasn't helped us stay on top of comms 🙂

First up, 4.0 is in production for every project we've got, but there are a couple fixes left (including a change to our multer integration) that we want to push out before removing the 'beta' badge. I'm hoping to land these within a month. We've also completely rewritten the website and docs to go along with it, which has been a massive undertaking that probably isn't obvious yet.

Second, we've been doing a lot of R&D to work out the future direction of keystone (which we are very much committed to). This includes reviewing how to take advantage of newer JS features like async/await, what changes to the core would be needed, how to (finally) implement a proper plugin / custom field types system so the Admin UI is more extensible, as well as porting to ES6 / using classes / etc now that all those features have stabilised in the language and node.

I'm a bit frustrated with how slowly the project has moved over the last year, and I am personally working out how to make it feel "light" again - and discard some of the architectural thinking that was right back when it started in 2013, but is holding us back in 2017.

To clearly address any concerns we've abandoned the project, Thinkmill (my company) has four or five people working on Keystone constantly - not full time, but adding up to probably two FTE.

Wish I could say more now but until we're a bit more organised that's going to have to do. I am _really_ looking forward to finally pushing 4.0 out the door and starting to discuss our plans for the future with the broader community!

[ttsirkia]

Great news! Thanks @JedWatson for letting us know this.

[lucasvall]

Thanks for the update!

[christroutner]

Hey @JedWatson I'm not sure what the proper channel would be for this, so I'll put this here. I've implemented my own plugin extension code into KeystoneJS. I'm using it for ConnextCMS, but it's not specific to that project. It works more generally for KeystoneJS. I've been using it for the last few months and it's been working great. It allows me to update my local KeystoneJS repository without breaking any of my sites or needing to do any manual code fixes/updates.

I'm calling the KeystoneJS-only plugin a Site Template whereas the combined ConnextCMS/KeystoneJS plugin I'm calling a Plugin Template

[webdesign7]

Thanks @JedWatson , but what you mean by this ?

To clearly address any concerns we've abandoned the project, Thinkmill (my company) has four or five people working on Keystone constantly - not full time, but adding up to probably two FTE.

about what project you were talking about ? keystone or other one ?

[jstockwin]

@webdesign7 "the project" will mean KeystoneJS

[Norbz]

Any updates on this @JedWatson ?
We saw a bit of improvments in september / october with a few PR being merged in the project.

I am using Keystone in production for a few websites now. never used the templating engine, just using it to build a quick and simple backend, but I wish sometimes I could do just a little more on the backend configuration, nested-list and drilldown are the best examples of improvements we could have.

Migrating to ES6 would be a nice feature too, but I know this is taking a lot of time and efforts...

[brundonsmith]

@JedWatson, any news? Your last post was very encouraging but that was 10 months ago

[internetErik]

See https://github.com/keystonejs/keystone/issues/4551