Collapse online history by default (fixes #476)
Add stub about, contact, and term pages, and flesh out footer some more
Add a sitemap and change to permissive robots.txt. Fixes #434 and #429
Implement non ajax item activity lists (so bots don't give us loads of errors)

Some refactoring of history-fetching methods to do ranged instead of paged loading.
Update play to 2.3.7
Refactoring activity lists, API and templates.

 - Activity list methods now return a `RangePage`
 - Backend methods now do the logic to fetch 'one more' from the stream
   in order to determine if there's anything more to come
 - Implemented pagination of item history lists and portal and admin
 - Various refactoring of templates to reduce code dup
Clean up portal integration tests and add a test for item history
FiX oh-so-broken JS
More reworking of access points, this time on the recieving end.

We now list the 'reverse' relation with a category label. Presentation
needs some work here.
Make the promotion of items trigger a re-index
WIP changes to enable new voting behaviour
Add hamcrest test dep SBT inexplicably can't find
Lots of WIP changes to promotion/demotion on annotations.

 - More methods on the Promotable trait
 - Extracted a separate backend trait for promotion operations
 - Lots of work on the promote/demote/undo web methods for annotations
 - Front end work on voting notes up and down
Rename/generalise lots of promotion-related i18n keys. Add score details.
Allow facetting by promotion score (negative, neutral, or positive)
Fix lagging rename, missed 'cos of no clean build
Ensure annotations and links produce a creation callback (for indexing)
Bug fixes and refactoring concerning query facets.

 - combining query facets in a tag/exclude union now works
 - multiple query facets are correctly handled as a union by being
   applied within the same fq parameter (instead of multiple)
 - simplification to the filter application code
Use a choice facet for LOD estimation

 - this allows, e.g. using both medium and high LOD
Consolidate rendering of annotations in different contexts.

An enum is now used as a path parameter to specify which one of
field, block, or list annotation rendering is required.