Add some words about Mark McLeod

This also adds documentation to clarify when and how we can update
gov.uk/humans.txt in future.

README.md

@@ -16,6 +16,7 @@ This application defines global templates for [GOV.UK](https://www.gov.uk) pages
 - [Slimmer templates](docs/slimmer_templates.md)
 - [Emergency Banner](docs/emergency-banner.md)
 - [Analytics](docs/analytics.md)
+- [`humans.txt`](docs/humans.md)
 
 ### Running the application
 

docs/humans.md

@@ -0,0 +1,15 @@
+# humans.txt
+
+Sometimes we want to publicly celebrate someone who's leaving GOV.UK. The convention for this is to temporarily update [gov.uk/humans.txt](https://www.gov.uk/humans.txt) with some words about their time on the programme.
+
+Anyone can write these words, but we should try to use a consistent style. Look back through [history](https://github.com/alphagov/static/commits/master/public/humans.txt) of `humans.txt` to see what others have written before you, and then compose your own text.
+
+## How to update the page
+
+1. Append some nice words to [`public/humans.txt`](../public/humans.txt).
+
+2. Raise a PR and get a technical and a content review.
+
+3. Deploy the PR to production and wait for the cache to clear.
+
+4. Raise a PR to remove the content after a few days.

public/humans.txt

@@ -1,2 +1,13 @@
 GOV.UK is built by a team at the Government Digital Service (with thanks to Martha!) in London,
 Bristol and Manchester.  If you'd like to join us, see https://gdscareers.gov.uk/
+
+Today we're saying goodbye to a senior product manager, Mark McLeod. Mark joined GDS in 2012
+as a policy advisor, and later became a product manager in the early stages of GOV.UK.
+
+Mark has worked on many things, including search, email notifications and retiring Local
+Directgov. He's been instrumental in giving GOV.UK publishers access to data about their
+content, so that they can make more informed decisions.
+
+Anyone who's worked with Mark knows he always throws himself wholeheartedly into the work and
+really cares about making a difference. He's been a huge user needs champion, helping us stick
+to our principles, building products based on evidence.