anchor.diff:  
   pass:[<br/><br/>]
   
  -listed the ``Ingredient``s imported from the fixture data spreadsheet:
  +returns a list of ``Ingredient``s that are imported from the fixture data spreadsheet:
   
   image::https://raw.githubusercontent.com/incodehq/radrace2015/master/images/210-ingredients-list-all.png[link="https://raw.githubusercontent.com/incodehq/radrace2015/master/images/210-ingredients-list-all.png"]
   
  
positive.code: Anyway...
  
  
  === Logging in as club administrator
  
  On the login page we configured the http://isis.apache.org/guides/rg.html#_rg_services-spi_manpage-UserRegistrationService[UserRegistrationService] SPI domain service along with the supporting http://isis.apache.org/guides/rg.html#_rg_services-api_manpage-EmailService[EmailService] API domain service in order that Apache Isis displayed the sign-up link:
  
  image::https://raw.githubusercontent.com/incodehq/radrace2015/master/images/010-logon-page-sign-up-now.png[link="https://raw.githubusercontent.com/incodehq/radrace2015/master/images/010-logon-page-sign-up-now.png"]
  
  
  pass:[<br/><br/>]
  
  However, we also set up `domainapp-admin` as an our "club administrator".  This was part of our fixture data; when we develop Isis applications, we always run with an in-memory database (more on this later); our fixture data gets the app to a known initial state.
  
negative.code: 
  === Publishing a Menu
  
  Once a `Menu` has been defined, one of the requirements was to be able to "publish" it, eg so that it could be downloaded from a website for would-be attendees to peruse:
  
  image::https://raw.githubusercontent.com/incodehq/radrace2015/master/images/070-publish-menu.png[link="https://raw.githubusercontent.com/incodehq/radrace2015/master/images/070-publish-menu.png"]
  
  