anchor.diff:  			p For more information about setting up and using database models with Keystone, see the <a href="/guide/data">database guide</a>.
   			
   			
  -			a(name='emails')
  -			h2 Emails
  -			
  -			p ...
  +			//- a(name='emails')
  +			//- h2 Emails
  +			//- 
  +			//- p ...
   			
   			
   			h2 Services
  -			
  -			a(name='cloudinary')
  -			h3 Cloudinary
  -			
  -			p ...
   			
   			
   			a(name='google')
  
positive.code: 					td <code>nav</code> <code class="data-type">Object</code>
  					td 
  						p An object that specifies the navigation structure for the Admin UI. Create a key for each section that should be visible in the primary navigation. Each key's value can be a single list path (as is seen in the URL when you view a list) or an array of list paths. When an array is used, secondary navigation is rendered in the Admin UI.
  						p The nav is also used to generate the links on the Admin UI home page; any lists that are registered but not including in the <code>nav</code> will be grouped at the bottom of the screen under the 'Other' heading.
  			
  			.code-header
  				h4 Custom Navigation Example
  
negative.code: //- *	`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
  