KeystoneJS is a powerful Node.js content management system and web app framework built on express and mongoose. Keystone makes it easy to create sophisticated web sites and apps, and comes with a beautiful auto-generated Admin UI.
Check out keystonejs.com for documentation and guides.
You can also deploy a starter project to Heroku for free to try it out:
Keystone gives you:
modelswith additional field types and functionality, building on those natively supported by Mongoose
... plus a lot of other tools and utilities to make creating complex web apps easier.
We have a friendly, growing community and welcome everyone to get involved.
Here are some ways:
We love to hear feedback about Keystone and the projects you're using it for. Ping us at @KeystoneJS on twitter.
If you are using KeystoneJS in any projects we encourage you to add it to our Related Projects Page. This is also the place to find generators and such that bundle KeystoneJS.
If you can, please contribute by reporting issues, discussing ideas, or submitting pull requests with patches and new features. We do our best to respond to all issues and pull requests within a day or two, and make patch releases to npm regularly.
If you're going to contribute code, please follow our coding standards.
Check out the KeystoneJS Getting Started Guide to start using KeystoneJS.
The easiest way to get started with Keystone is to use the Yeoman generator:
$ npm install -g generator-keystone$ yo keystone
Answer the questions, and the generator will create a new project based on the options you select, and install the required packages from npm.
Alternatively, to include Keystone in an existing project or start from scratch (without Yeoman), specify
keystone: "^0.3.9" in the
dependencies array of your
package.json file, and run
npm install from your terminal.
Running in default mode, Keystone takes care of everything required to configure your application with Express, connect to your MongoDB database, and start the web server.
Here is an example of what your
app.js, etc) file may look like:
var keystone = ;keystone;keystone;keystone;keystonestart;
Config variables can be passed in an object to the
keystone.init method, or can be set any time before
keystone.set(key, value). This allows for a more flexible order of execution (e.g. if you refer to Lists in your
routes, you can set the routes after configuring your Lists, as in the example above).
See the KeystoneJS configuration documentation for details and examples of the available configuration options.
To understand how these settings are used, and how the Express application is initialised, see
Keystone builds on the basic data types provided by mongo and allows you to easily add rich, functional fields to your application's models.
You get helper methods on your models for dealing with each field type easily (such as formatting a date or number, resizing an image, getting an array of the available options for a select field, or using Google's Places API to improve addresses) as well as a beautiful, responsive admin UI to edit your data with.
See the KeystoneJS database documentation for details and examples of the various field types, as well as how to set up and use database models in your application.
Keystone's field types include:
Keystone also has Relationship fields for managing one-to-many and many-to-many relationships between different models.
When you deploy your KeystoneJS app to production, be sure to set your
ENV environment variable to
You can do this by setting
NODE_ENV=production in your
.env file, which gets handled by dotenv.
Setting your environment enables certain features, including template caching, simpler error reporting and html minification, that are important in production but annoying in development.
If you want to test or develop against the
master branch of KeystoneJS (or against your own branch), rather than a published version on npm, you just need to check it out then use
npm link to link it to your project. On Mac OS, this is done like this:
sudo npm link(you will need to enter your system password)
~/Development/MySite(the one with your
package.jsonfile in it) run
npm link keystone. This will create a link between
require('keystone') normally in your app - the development copy will be used. Note that running
npm update will ignore new versions of keystone that have been published.
To go back to using a published version of KeystoneJS from npm, from your project directory, run
npm unlink keystone then
To run the test suite run
Thanks to the following companies and projects whose work we have used or taken inspiration from in the making of KeystoneJS:
(The MIT License)
Copyright (c) 2015 Jed Watson
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.