add GitHub to the sponsors
Add SkillsMatter to the sponsors
add Pluralsight to the sponsors
Merge pull request #255 from adrianbanks/add-github-to-sponsors

Add GitHub to the sponsors

Conflicts:
	DDDEastAnglia/Views/Home/Sponsors.cshtml
	DDDEastAnglia/Views/Shared/_Sponsors.cshtml
Merge pull request #262 from adrianbanks/add-skillsmatter=to=sponsors

Add SkillsMatter to the sponsors

Conflicts:
	DDDEastAnglia/Views/Home/Sponsors.cshtml
	DDDEastAnglia/Views/Shared/_Sponsors.cshtml
Merge pull request #256 from adrianbanks/add-pluralsight-to-sponsors

Add Pluralsight to the sponsors

Conflicts:
	DDDEastAnglia/Views/Home/Sponsors.cshtml
	DDDEastAnglia/Views/Shared/_Sponsors.cshtml
Merge pull request #266 from adrianbanks/database-migrations

Re-introduce database migrations

We lost the ability to do schema changes when we removed EF (although in
reality we could never do them easily). This re-introduces the ability
using [Fluent Migrator](https://github.com/schambers/fluentmigrator/wiki).

When this gets pushed to staging and production, a manual database upgrade
will need to be run to get the database into the correct initial state.
The ManualUpgrade.sql is a script for this, but it might need tweaking
depending on the actual names of the auto-generated key names.

Once the manual upgrade has run, further schema changes can be made by
simply adding a new migration to the DDDEastAnglia.DatabaseMigrations
project and it will get automatically applied next time the website
starts.