anchor.diff:  
   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
  
positive.code: 					td
  						p <code>href</code> to bounce visitors to after they successfully sign out via the built-in signin route
  						p Defaults to <code class="default-value">/keystone</code>
  
  			p For more information about setting up and using database models with Keystone, see the <a href="/docs/database">database guide</a>.
  
  
  			//- a(name='emails')
  			//- h2 Emails
  			//-
  			//- p ...
  
  
  			a(name='services')
  			h2 Services
  
  
  			a(name='services-google')
  			h3 Google Maps
  
  			p Keystone's <a href="/docs/database#field_location">Location field type</a> supports integration with the <a href="http://www.morethanamap.com" target="_blank">Google Maps API</a> to auto-improve values (including discovering latitude and longitude) via the <a href="https://developers.google.com/places/documentation/autocomplete" target="_blank"> Places Autocomplete API</a>.
  
  			p To enable these features, <a href="https://code.google.com/apis/console/" target"_blank">obtain an API Key from Google</a> and enable the Google Maps v3 and Google Places APIs for it, then set the following options:
  
  			table.table
  				col(width=270)
  				col
  
negative.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 included in the <code>nav</code> will be grouped at the bottom of the screen under the 'Other' heading.
  			
  			.code-header
  				h4 Custom Navigation Example
  				p If you had <code>User</code>, <code>Post</code> and <code>PostCategory</code> models, you could group the posts and post categories into a <strong>Content</strong> navigation item like this:
  