Package and publish to NuGet
Not sure how best this can work - not really experimented with packaging anything with NuGet that contains what is a whole bunch of file types (source files etc).
But it would be nice if somebody could basically pull FsBlog from NuGet. They wouldn't need to run the build task - as FsBlogLib will be built, and the dependencies on the other libs would be resolved etc.
But they would need fsblog.fsx and the shell scripts etc.
I believe I got it working so I pushed a build based on #23 to nuget https://www.nuget.org/packages/FsBlog/ I didn't add FAKE as a dependency to the package since it gets added to the parent packages folder instead to the current directory.
Just tried this out now - the NuGet route doesn't work, when you run fake commands, they can't find Razor etc.