Add basic error handling to YAML parsing script
Update Gruntfile.js to include error reporting
Add new security question pages to routes

Four additional pages needed to be added to routes file.
Pass invalid responses through to display

When there are validation errors with submitted answers those answers need to be passed through to the page display controller so that that can be used to re-populate form fields and users' work is not lost.
Pass invalid responses through to display

When there are validation errors with submitted answers those answers need to be passed through to the page display controller so that that can be used to re-populate form fields and users' work is not lost.
Make Grunt fail if it can't generate the content
Merge pull request #76 from alphagov/add-error-checking-to-content-processing

Add error checking to content processing
Allow hints on the assurance approach questions
Use correct title for page 33

Was pulling in page 30 title instead of page 33.
Make sure the YAML-combining script returns true

- The Gruntfile now checks whether or not the content-generating script returns
  false (i.e. an error)
- Unfortunately we forgot to tell the script do return true if it doesn't error
- Oops
Merge pull request #80 from alphagov/fix-content-generation-bug

Fix bug which causes content generation to fail
Add new security question pages to routes

Four additional pages needed to be added to routes file.
Use correct title for page 33

Was pulling in page 30 title instead of page 33.
Fix validation on page 28

Validation was incorrectly implemented for this page and prevented user progressing to the next page. This commit fixes the validation.
Remove radio buttons with no value

There were some extra radio buttons on questions here. This commit removes them.
Merge pull request #81 from alphagov/assurance-hint

Allow hints on the assurance approach questions
Make page 10 question 1 into checkboxes
Merge pull request #82 from alphagov/working_version_to_deploy_for_demo

Working version to deploy for demo
Put the Jenkins tasks into a shell script

This can then be run by any of the jobs, and creates artefacts that can
be deployed to all the environments, if they build successfully.

To run successfully, Jenkins needs:
- SSH access to the Github repo
- Submodule processing tickbox not ticked
- SSH agent tickbox ticked, with the appropriate user selected
- Cookie encryption key should be specified as a bash variable before running
  this script
- Git publisher set up to push $BUILD_TAG as a new Git tag to Github (optional,
  but should be used for so we look on Github and see exactly what's in each
  build)

For an example of a Jenkins job, see Supplier-Submission-Build
Merge pull request #85 from alphagov/put-jenkins-into-script

Put the Jenkins tasks into a shell script