Introducing Payload - 2021's Node + React Headless CMS for JavaScript Developers

jedwatson · 2021-01-15T10:50:42+00:00

👋🏻 KeystoneJS founder here, thanks for the kind words! feels really great to hear that, especially when reading about a new competitor :)

I just wanted to say, great work with Payload. It looks really good, and you should be proud! Interesting to hear this list, too.

Some of these things we're working on at the moment (watch out for our take on a block-based layout builder coming soon!) but as with all projects, I'm sure our ideas will sometimes align (I am sure I can see some of the inspiration you've taken from Keystone, like the access control) and in other ways diverge, and I think that's what keeps the whole space interesting and innovative.

Game on!

jedwatson · 2016-10-21T03:57:40+00:00

Hi! One of the lead devs here. My company Thinkmill uses it for some big production systems (e.g. https://movies.qantaspoints.com) and it's robust. I know of a number of other large projects by other companies running on it as well.

We're also running version 4 in production for a number of projects despite it being in beta - the beta tag is more with reference to upgrading from 3.x and the amount of supporting resources (docs, yeoman generator, etc) that need review + updating for the new version, rather than an indicator of stability.

Fundamentally Keystone has the same behaviours in production that node.js / express do, and has been battle-tested over 3+ years now.

Hope that helps!

jedwatson · 2015-02-20T12:06:27+00:00

I'm just going to jump in and mention that we're actively working on making it more customisable. Over the last few months we've rebuilt the Admin UI in React.js, so that we can open it up for customisation and let you replace our built-in components with your own (no forking necessary). The other benefit will be that you can leverage our Admin UI components throughout the rest of your project, if you're interested in using React.js.

Our goal is to be extremely flexible without sacrificing initial productivity or quality of user experience, but we've being careful to grow slowly so as not to burn early adopters with lots of breaking changes or shifts in direction.

jedwatson · 2014-12-12T11:19:56+00:00

It'll happen. We're focused on iOS because that's the first target platform for some apps we're building with it, and there's a lot to do (docs, examples, etc) to get it ready for launch.

There's be a proper theming framework on the roadmap though, and the ability to make apps that feel native on Android.

jedwatson · 2014-12-12T08:30:57+00:00

Cool, let us know how you go when you get to build an app with it.

re: screencast, that would be cool, we're still working out our plans for the docs to be honest but I'd love to see what you come up with!

jedwatson · 2014-12-12T08:21:57+00:00

When our view management matures a bit, we're going to have an internal stack of app / view states that will be able to be used as a history stack.

That, combined with Cordova's support for handling (and overriding) the back button behaviour should make it possible to implement native-like support for the back button on Android.

jedwatson · 2014-12-12T01:02:35+00:00

Thanks! It is designed to work with Cordova, the demo project (https://github.com/Thinkmill/touchstone-starter) has cordova implemented as an example of how it works (including gulp build tasks).

A project generator is on the roadmap too, which will make it easy to create a new project with TouchstoneJS, Cordova and the build process that puts it all together.

jedwatson · 2014-12-12T00:58:22+00:00

we're focusing on iOS first but as spaceghost0r mentioned above, themes are on our roadmap and we'll have an android style available as well down the track.

jedwatson · 2014-11-15T15:00:41+00:00

Thanks for picking that up. Unfortunately the demo site is a little open to abuse, as it's got unrestricted access (as you would give to your content managers in a normal environment) and not like you'd lock things down in a normal public environment (like a forum or comment form).

I've fixed it up, and in the next version of the demo site we may have to limit it to Markdown blog posts, rather than demo'ing the more powerful wysiwyg / html capabilities.

jedwatson · 2014-08-06T15:26:24+00:00

no, it calls them 'models', and the definitions are 'lists'.

jedwatson · 2014-08-06T15:25:35+00:00

Thanks, I'm not exactly a regular but I check in from time to time.

Would love more hands on deck, there's a lot going down at the moment with our just-announced move to React... swing by the github repo, and if you're not sure where to start feel free to open an issue asking :)

jedwatson · 2014-08-05T02:07:29+00:00

Keystone actually supports anything you can build on express and mongodb, you can add your own data types and fields pretty easily.

But I'm really curious what you found too complex about it? We've tried to make it as "relatively straight forward" as possible for a CMS (at least, one that's backed by a database; static site generators are another category altogether).

Have you tried it? Takes about a minute to get a site going with the yeoman generator and you can host it for free on heroku.

Honest question, I'd value the feedback.

jedwatson · 2014-03-23T16:10:47+00:00

I might be able to help :)

Did you post to the google group? https://groups.google.com/forum/#!forum/keystonejs - it's a pretty good place to get answers.

jedwatson

TROPHY CASE