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: 					td: code nodelete
  					td Prevents deletion of items from the list through the Keystone Admin UI
  			
  			h2 Fields
  			
  			p ...
  			
  			h3 Common Options
  			
  			p ...
  			
  			h2 Field Types
  			
  			p ...
  					
  
negative.code: 		
  		.col-sm-9: #docs-content
  			
  			a(name='concepts')
  			h1 Setting up &amp; Using Data Models
  			
  			p In KeystoneJS, your data schema and models are controlled by <strong>Lists</strong>, and documents in your database are often called <strong>Items</strong>.
  			
  			p To define a data model, you create a <code>new keystone.List</code>, and pass it <a href="#lists_options">list options</a>. 
  			
  			p You then <code>add</code> fields to the list. Behind the scenes, a Keystone List will create a <a href="http://mongoosejs.com/docs/guide.html" target="_blank">mongoose schema</a>, and add the appropriate paths to it for the fields you define.
  			
  			p The <code>schema</code> is accessible, allowing you to plug in other mongoose functionality like virtuals, methods and pre / post save hooks.
  			
  			p When you have finished setting up your List, call <code>list.register()</code> to initialise it and register it with Keystone.
  			
  			p To query your data, you use the <code>list.model</code> (which is a <a href="http://mongoosejs.com/docs/models.html" target="_blank">mongoose model</a>).
  			
  			p List Items are <a href="http://mongoosejs.com/docs/documents.html" target"_blank">mongoose documents</a>. To create new items, use <code>new list.model()</code> and when you're ready to save it (or to save changes to an existing Item), call <code>item.save()</code>.
  			
  			h2 Lists
  			
  			h3 Usage
  			
  			p The syntax for creating a <strong>Keystone List</strong> 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', {
  				|     autokey: { path: 'slug', from: 'title', unique: true },
  				|     map: { name: 'title' },
  				|     defaultSort: '-createdAt'
  				| });
  				| Post.add({
  				|     title: { type: String, required: true },
  				|     slug: { type: String, index: true },
  				|     state: { type: Types.Select, options: 'draft, published, archived', default: 'draft' },
  				|     author: { type: Types.Relationship, ref: 'User' },
  				|     createdAt: { type: Date, default: Date.now },
  				|     publishedAt: Date,
  				|     image: { type: Types.CloudinaryImage },
  				|     content: {
  				|         brief: { type: Types.Html, wysiwyg: true, height: 150 },
  				|         extended: { type: Types.Html, wysiwyg: true, height: 400 }
  				|     }
  				| });
  				| Post.defaultColumns = 'title, state|20%, author, pubilshedAt|15%'
  				| Post.register();
  			
  			p.note This example implements the optional <code>map</code>, <code>autokey</code> and <code>defaultSort</code> options, described below.
  			p.note It also specifies <code>title</code>, <code>state</code>, <code>author</code> and <code>publishedAt</code> as the default columns to display in the Admin UI, with state and publishedAt being given column widths.
  			p.note The <code>author</code> field is a relationship with the <code>User</code> model, as described in the <a href="/guide#models_users">getting started guide</a>.
  			
  			h3 Options
  			
  