A guide to help understand the scope of web operations work

This is based on a Google document I wrote about a year ago that has
seen extensive use on a number of exemplar projects and that is being
shared a little too widely.

I'm stil skeptical that anything that appears to be this prescriptive is
a good idea, but in practice this has worked very well and had the
desired effect, namely to make people much more aware of the amount of
work required. So it's well tested, if on the face of it a bit crazy.

For work like this that is broadly similar for many services starting
with many things and then adding a few and removing a few appears better
than starting from scratch everywhere.
Trim trailing whitespace
Revert "Trim trailing whitespace"

This reverts commit 1a420a7dc7c674b638cce27128730a04e37a9a3b.
I messed this up.
Link to the new things

Also prefer URLs without .html in them.
Link to the sample stories
Initial sweep

Typos, hemingway etc
Emphasise that this isn’t an exhaustive list

Agile, placeholder for a conversation aspect.
Add intentional whitespace

Markdown <br/> behaviour.
Define a stable anchor

Having an anchor derived from the heading seems fragile.
Fix dash
Fix typo
Merge pull request #376 from alphagov/web-operations-stories

A guide to help understand the scope of web operations work