Add Travis config to run linkchecker against the built site

.travis.yml

@@ -0,0 +1,7 @@
+language: python
+python:
+  - 2.7
+
+script:
+  - mkdocs build
+  - linkchecker ./site/

docs/support/incident_process.md

@@ -31,7 +31,7 @@ Ensure that we schedule the post mortem and publish our incident report Draft th
 ### If you’re incident comms:
 
 1. Let the PaaS team know about the incident on #the-government-paas Slack channel
-2. Tell internal stakeholders: send a summary of the incident as soon as possible to the [GaaP incidents email list]([email protected]) (this tells the GaaP team and a few others - internal to GDS - including IA team members).
+2. Tell internal stakeholders: send a summary of the incident as soon as possible to the [GaaP incidents email list](mailto:[email protected]) (this tells the GaaP team and a few others - internal to GDS - including IA team members).
 3. Tell tenants: log in to our [Statuspage account](https://www.statuspage.io/). This is where you will send the incident alert email from, using the [saved templates](https://manage.statuspage.io/pages/h4wt7brwsqr0).
 5. Update tenants hourly using the templates saved in our statuspage account.
 6. Ensure that all decisions/comms are entered into the timeline section of the incident report.

requirements.txt

@@ -18,3 +18,7 @@ six==1.10.0
 tornado==4.3
 webcolors==1.5
 wsgiref==0.1.2
+
+linkchecker==9.3
+# https://github.com/wummel/linkchecker/issues/649
+requests==2.9.2