I'm with you 100% with the preference for the ability to completely undo any action. That is a more preferable experience.
However, as also mentioned by atian, it always depends on context, and what's available to you. There are situations where I'm writing an app that won't have the ability to "undo" deletes for particular objects. This can arise from API restraints, unnecessary overhead for a trivial object (todo list item as a contrived example), etc. Those scenarios are what I use the deleted library for.
I don't run Windows, so I don't know whether it will work or not. Charts can also be added using a js library. You will have to include the data statically in your Jekyll build, as part of the js, or you can make an API call if available.
Adding to the comment by tacticus about Disqus: It's the preferred solution for Jekyll sites since they are static. Disqus takes care of all the commenting heavy lifting on the client side, while also taking care of the database.
There's definitely something that isn't quite right about the footer. I will have to ponder how to make it fit in more with the rest of the theme. I've just added Github issues for the lists/line height weirdness, I will fix that ASAP.
The Pixyll theme uses a different DOM structure for the templates and includes, so it would require some tweaking to work with Pixyll's stylesheets. Though, it would be feasible.
Yeah, you're definitely right on that. I'm going to be increasing the nav font size so that it's easier to read, and easier to tap on mobile devices. I overlooked that aspect a little bit =/.
It definitely drew lots of inspiration from mdo's theme, and basscss.
Yeah, regarding the navigation bar, I was wondering if I should make that font a slightly larger size. I think your nitpick has persuaded me to go ahead and make it a little bigger.