anchor.diff:  		.col-sm-3: #docs-sidebar
   			ul.sidebar-nav
   				li.nav-label Database
  -				li: a(href='#lists_intro') Concepts
  +				li: a(href='#concepts') Concepts
   				li.nav-label Lists
   				li: a(href='#lists_intro') Overview
   				li: a(href='#lists_usage') Usage
  
positive.code: 		
  		.col-sm-9: #docs-content
  			
  			h1 Setting up &amp; Using Data Models in Keystone
  			
  			p A List in Keystone is similar to a Schema; it defines the Fields and options for a collection in the database, as well as providing an interface to access the Mongoose Schema and Model, through which you can execute queries.
  			
  			
  			h2 Lists
  			
  			h3 Usage
  			
  			p The syntax for creating a Keystone List is very similar to the syntax for creating a Mongoose Schema, with the exception of the constructor, which is <code>var MyList = new Keystone.List(key, options)</code>.
  			p Once you have created a new List, add fields to it using <code>MyList.add(fields)</code>, where fields is an object of keys (for field paths) and values (for field types, or options).
  			p Fields are defined by an object with a <code>type</code> property, which must be a valid Field Type or basic data type. Using the object syntax you can specify additional options for the field. Common field options and field-type-specific options are detailed in the fields documentation.
  			p When all the fields and options have been set on the list, call <code>MyList.register()</code> to register the list with Keystone and finalise its configuration
  			
  			p <strong>For example: </strong> a simple Post model for a blog might look like this:
  			
  			.code-header: h4 Post.js
  			pre
  				| var keystone = require('keystone'),
  				| 	Types = keystone.Field.Types;
  				| 
  				| var Post = new keystone.List('Post');
  				| 
  				| Post.add({
  				| 	title: { type: String, required: true },
  				| 	slug: { type: String, index: true },
  				| 	author: String,
  				| 	publishedDate: Date,
  				| 	image: { type: Types.CloudinaryImage },
  				| 	content: {
  				| 		brief: { type: Types.Html, wysiwyg: true, height: 150 },
  				| 		extended: { type: Types.Html, wysiwyg: true, height: 400 }
  				| 	}
  				| });
  				| 
  				| Post.register();
  			
  			h3 Options
  			
  
negative.code: 					td A comma-delimited list of default columns to display in the Admin UI List View.
  						|  You can specify width in either pixels or percent after a <code>|</code> pipe character.
  				tr
  					td: code map
  					td An object that maps fields to special <strong>list</strong> paths. Each path defaults to its key if a field with that key is added. Mappable paths include
  						ul.options
  							li <code>name</code> - the field that contains the name of the item, for display in the Admin UI
  				tr
  					td: code autokey
  					td Adds a plugin to the list that automatically generates a key for each document when it is saved, based on the value of another field or path. The value of the option should be an object with the following keys:
  						ul.options
  							li <code>from</code> <code class="data-type">string</code> - the field or path to generate the key from, can be a space-delimited list of fields
  							li <code>path</code> <code class="data-type">string</code> - the path to store the key at
  							li <code>unique</code> <code class="data-type">boolean</code> - whether the key should be unique or not
  						| <em>Autokey paths are automatically be indexed; you may also want to include them in compound indexes.</em>
  				tr
  					td: code noedit
  					td Prevents editing of items in the list through the Keystone Admin UI
  