anchor.diff:  				|     'users': 'users',
   				|     'content': ['posts', 'post-categories']
   				| });
  -
  +		
   			a(name='options-server')
   			h3 Web Server Options
  -
  +			
   			p The following options control the configuration of your web server and the express app:
  -
  +			
   			table.table
   				col(width=210)
   				col
  
positive.code: 
  block content
  	.container: .row
  
  		.col-sm-3
  			+docsnav(docssection)
  
  		.col-sm-9: .docs-content
  
  			h2 Keystone Options
  
  			a(name='options-concepts')
  			h3 Setting Options
  
  			p The options for KeystoneJS cover a range of behaviours, from how the express app is configured to enabling features and authentication options for integrated services.
  
  			p There are three ways to set options:
  
  			ul.options
  				li Passing a <code>{ key: 'value' }</code> configuration <code class="data-type">Object</code> to the <code>keystone.init(options)</code> method
  				li Calling <code>keystone.set('key', 'value')</code>
  				li Setting environment variables in <code>process.env</code>. Only some options support this (noted below).
  
  			p If you want to keep secret keys and configuration out of your codebase (especially important for open source projects, or projects where not all developers should have access to production config settings) the <a href="https://npmjs.org/package/dotenv" target="_blank">dotenv</a> module makes this very easy to manage.
  
  			a(name='options-project')
  			h3 Project Options
  
  			p The following options control the branding and navigation of the KeystoneJS application in the Admin UI:
  
  			table.table
  				col(width=210)
  				col
  
negative.code: 				| keystone.set('mandrill username', 'your-username');
  
  
  			
  			
  			//- h2 Error Handling
  			//- 
  			//- a(name='404s')
  			//- h3 <code>404</code> (not found) errors
  			//- 
  			//- //-  path to your 404 view template, or a function to handle 404s (standard Express signature of `function(req, res)`)
  			//- 
  			//- a(name='500s')
  			//- h3 <code>500</code> (server error) errors
  			
  			
  			
  			a(name='updates')
  			h2 Application Updates
  			
  			p Keystone includes an updates framework, which you can enable by setting the <code>auto update</code> option to <code class="default-value">true</code>.
  			
  			p Updates provide an easy way to seed your database, transition data when your models change, or run transformation scripts against your database.
  			
  			p Update files should be named using a semantic version followed by an optional key, like <code>0.0.1-init.js</code>. The version numbers are used to order the update scripts correctly, while the keys are a nice way to identify what each update does.
  			
  			p Each update file should export a single function, which should accept a single argument - the <code>next(err)</code> callback, to be called when the update is complete.
  			
  			p All the update files will be executed (each one waits for the previous update to complete) before the web server is started.
  			
  			p If the <code>next</code> callback is receives an error it will be reported to the console, and application initialisation will halt.
  			
  			p You can temporarily disable updates from running in development by setting a <code>__defer__</code> property on the exported function to <code>true</code>. Any subsequent updates will be skipped, but the application will be started.
  			
  			p Updates are only run once, and each completed update is logged in an <code>app_updates</code> collection in your database.
  			
  			.code-header
  				h4 Update Script Example
  				p Creates a new admin User
  			pre: code.language-javascript
  				| var keystone = require('keystone'),
  				|     User = keystone.list('User');
  				| 
  				| exports = module.exports = function(done) {
  				|     new User.model({
  				|         name: { first: 'Admin', last: 'User' },
  