Source control is essential for managing code but for handling a few text files on a blog it's probably unnecessary overhead.
Also most people aren't programmers, there is a large audience who could edit a markdown file but have no idea what Git is. I'm sure I could teach my mum markdown in an hour or so but there is no way she could ever grasp Git.
There's over 300 jpgs just in blog post related images.
Then I also have a photo gallery where there's about 500x 1920x1080 jpgs.
The .git/ folder ended up taking up gigs upon gigs of space.
Sounds very big for 500 small (IE not 10/20 mega pixel) jpegs?
Even at a generous 500k that should be just ~250 mb of that, unless you have on average four or more "versions" of each image? But I'm assuming the 1080p jpegs are "prints" and so doesn't change much?
At that point I blew out the directory and have gone gitless on my blog.
You might not need all the features, but a public git repository is usually easier to setup than a private WebDAV setup or something like that…