Feature/dato integration

[thclark]

Summary

Quality Checklist

• [ ] New features are fully tested (No matter how much Coverage Karma you have)
• [ ] [v0.2 onward] New features are included in the documentation
• [ ] [v0.2 onward] Breaking changes are documented with clear instructions of what

Coverage Karma

• [ ] If your PR decreases test coverage, do you feel you have built enough Coverage Karma* to justify it?

*Coverage Karma can be earned by disproportionally increasing test coverage in the rest of your contributions. It's an honesty policy - you keep count of your own.

[thclark]

@muhammadqamar I've begun hooking up to a new CMS. This has meant the images are coming in of better quality now, and I've done some refactoring and tidying up.

I've resolved conflicts so you should be able to merge directly into your branch, but I will leave it to you to merge so you can see what changed. The biggest thing is the gatsby-plugin-image where I've had to move away from a deprecated version, so the image API is a bit different.

I've not added all the pages by far to the CMS, so I'll come along behind you and wire up the CMS queries as I go. In the meantime, if you keep querying for images from the file source you'll be fine, no need for you to worry about the dato integration.