The Keystone Roadmap
Keystone 6 is actively maintained and steadily improving. We've graduated to the @keystone-6
namespace on npm and have a stable set of APIs that you can confidently build on 🚀
Research & Development
Surveyed the landscape. Formed concepts around what a next-gen experience would look like. Started laying the foundations.
Community Preview
Published the New Interfaces as @keystone-next
on npm. Commenced iteration based on community & internal feedback.
General Availability Release
Stabilised the new architecture & APIs. Docs & example projects. Published as @keystone-6
on npm.
Maturity, community, & next-gen Admin UI
A better dev-configured editing experience. Maturity & features in Keystone core. More pathways to grow with Keystone.
What's up next
We're using the foundations we shipped in 2021 as a springboard to bring developers, project owners, and editors into more productive ways of working together. Our key areas of focus are:
- Schema-driven auth that streamlines how users authenticate with Keystone applications
- A next-gen Admin UI that unifies developer and editor collaborations in new and exciting ways
- Maturing the DX with better Types and capabilities for self-hosting and media management
Schema-driven authentication
Keystone operates on the schema-driven principle. Right now, authentication in Keystone is left up to the developers to implement. This leads to every Keystone project having auth handled in a slightly different way.
We want to change that and offer a predictable, schema-driven first-party authentication solution for Keystone.
Next-gen Admin UI
Our design and labs teams have re-imagined a state-of-the-art Admin UI. One that is responsive, accessible and functional. The fruit of this work led to Keystar UI, an internal design system we've been battle-testing with Keystatic.
This body of work will elevate the experience of authoring content in Keystone to the same high standards we have for authoring with Keystone's core APIs.
Maturing the Developer Experience
At Thinkmill, we have a longstanding commitment to open source that includes the likes of react select, classnames, Keystatic, and of course Keystone.
We'll continue to iterate on this knowledge and learning loop to make Keystone the easiest way to design and standup a GraphQL API on the web. Going all-in on Typescript has made the DX so sweet, but we want to take it further so that Keystone's the best Typescript > GraphQL developer experience in the ecosystem. ✨
We'll also focus on making better pathways for you to integrate Keystone with the deployment services you use most, so you can get the most out of where the modern web is going. Image and file management is an area we're actively iterating on, and we'll have more to share soon.
Feature roadmap
Here's what we've been working on, and what's coming next.
Recently released
- Fields & Schema
Singletons
A way to define a single object in schema that's editable in Admin UI and accessible in the GraphQL API. Handy for storing website & social settings, API keys, and more.
- Admin UI
Field Groups
It's often easier to work with content when the form is grouped into different sections of related fields. Learn more
- Core
Back-end APIs for Node.js apps
Access your GraphQL APIs from Node.js for greater flexibility when writing apps and hybrid use-cases.
Current focus
- Fields & Schema
Conditional fields
Dynamically showing fields based on the value of other fields is a great way to improve editing flow and content integrity.
- Admin UI
Next-gen Admin UI
Make the Admin UI responsive, accessible and i18n compliant with the battle-tested Keystar UI design system.
Next up
- Fields & Schema
Nested fields
Sometimes you need to manage data in structures that are nested and/or repeating. We're working on a way to define these in schema and have them stored as JSON field in the database.
- Core
Sortable lists
Certain list types come with a need to order the items they contain. We're looking in to an approach that's easy to implement in schema.
- Docs
Build & Deployment options
We're broadening our list of streamlined scenarios & looking into options for serverless environments.
Further afield
- Admin UI
Content preview
Built-in tooling for you to give editors a sense of how their content will be consumed by end users.
- Admin UI
Custom publishing workflows
Design your own journey from
draft
topublished
to meet the unique needs of your content team. - Admin UI
Relationship management
More powerful interfaces for managing different scales of related data, from small to really really large
- Core
GraphQL Subscriptions
Long lasting server operations that can change their result over time. Handy for updating your front-end in real time when important data changes in your backend.
- Core
Field Translations
A built-in schema-driven approach to supporting multilingual content projects.
- Core
Upsert mutations
If you want to update an item but aren't sure if it exists, this will update the item if it's there or create a new item with the data you've provided.
- Core
Serverless hosting
The future of deployment is serverless, and we're tracking the state of the ecosystem to make sure Keystone is ready for it.
- Core
Native full-text search
A way for you and editors to easily search for strings across your entire dataset. Handy for when you need something specific but don't know where it lives.
Got a feature you're after, or want to know more about the future?
Join the Keystone conversation on Slack, GitHub, and Twitter.
Start building today.
- 5 minute starters
- Example projects
- Free forever
- No lock-in