The core goals of Keystone are:
- allow fast definition of schema and application structure
- provide content management that matches any application structure
- allow effortless and flexible access control configuration
- provide the most intuitive GraphQL API
- comprise small independent packages that can be added and combined as required
- allow freedom of choice and interoperability outside these narrow areas of control
Keystone is not trying to be:
- an ORM like Knex or Mongoose
- a simple database wrapper like Prisma
- a front-end hosting service like Netlify
- an application hosting service like Heroku
- a database provisioning service like MongoLab
- a build or deployment tool
- a template engine (Keystone is headless)
We want people to use these types of services interchangeably with Keystone with as little effort as possible. Rather than position itself as a competitor to any of the above, Keystone empowers people by not limiting these choices.
There may be complementary services, plugins or packages that tie in with the above. Although we will avoid adding these features to 'core' we want to provide a supportive environment for these to be developed within the Keystone community.
We also want to ensure Keystone works well with static sites and serverless architecture. This goal will help keep Keystone light-weight, nimble, customisable and not tied to a specific architecture, in-line with our core goals.
A lot of work has been done on Keystone's core architecture. In this area Keystone 5 is significantly more mature than Keystone 4 was. We'd like to add database transactions, slightly refactor some of the internal workings of relationship fields and make the experience of database migrations easier. Aside from this we imagine the core architecture will remain largely the same.
In the short term we want to focus on a better onboarding experience and making it easier to build typical applications with Keystone. This involves better error messages, documentation and examples, extensibility of the AdminUI as well as new field types and adapters.
All PRs in these areas will be welcome. The list of features and bugs below represents identified tasks that align with Keystone's core goals and current focus. Although the core goals of this project will remain the same, some tasks may evolve, new tasks may be added and priorities might change. For the latest list of Roadmap tasks, take a look at our Roadmap Milestone on Github.
- Options pages (#1639)
- Better seeding of initial data (#301)
- Migrations (#299)
- Virtual\Dynamic fields (#1117)
- Repeating sections (#313, #195)
- Ability to deploy the Admin UI to a static server (#734, #1258, #1257)
- Add a DateRange field type (#215, #1642)
- Add case options to text fields (#1641)
- A React App (#1669)
- Transaction Support (#211)
- Admin UI Hooks (#1665)
- StateMachine Type (#1528)
- Make Hooks an Array (#1495)
- Finalise query limits (#1469)
- JSON & Memory Adapters (#947, #324)
whereclauses on single relationships (#699)
- Allow upsert mutations (#182)
- Auth Strategy and Authentication improvement (#878)
- Creating custom field types (#1054)
- Creating new adapters
- Error messages (#1659)
- Improve the speed of our CI (#1672)