anchor.diff:  //- *	`email tests` - 
   //- *	`mandrill api key` - your mandrill API key to use with the `keystone.Email` Class
   //- *	`email rules` - find & replace rules for pre-parsing email templates, useful to help with local vs. production absolute paths for images
  -
  -//- *	`cloudinary config` `{cloud_name: '', api_key: '', api_secret: ''}` - alternatively set `process.env.CLOUDINARY_URL`
  -//- *	`cloudinary prefix` - prefix for all native tags added to uploaded images
  
positive.code: 			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 which are picked up in `process.env`. 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.
  			
  
negative.code: 				| keystone.set('embedly api key', 'your-key');
  			
  			
  			//- 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
  			
  			
  			
  