This was brought up by @zachleat and he provided this tutorial.

I had issues with getting a subdirectory htaccess file working with the permalink stuff, but it looks like if I use the include configuration option, I can leave it as a dotfile (.htaccess) and then ditch the permalink stuff.

Instead of manually specifying all these page specific redirects, can a more generic approach (with regex) be used?

Something similar to the approach used in this SO post.

Everything is managed manually right now, I should be using bower for this.

Building the contents of the repo relies directly on ruby gems (namely, jekyll), so it should probably have a Gemfile. Get on it!

Now that the posts are listed on my main page, the blog index page can display the content (or at least an excerpt) rather than just listing the posts by title and summary.

So far I haven't taken advantage of the tags feature provided by jekyll, I think it would be useful to start tagging posts and displaying the tags discretely toward the top, likely right next to the post date.

Make this more HTML5-tastic with some time tags.

The site is currently using and being built with Jekyll 1.5.1, but that is so last year now. Time to get moved over to 2.0 ASAP. Shouldn't make much of a difference in any of the code, just need to bump the gem.

There are a lot of posts with code blocks, but no syntax highlighting is being applied. This means the code is less fun to read which in turn means the posts are less fun to read. This needs immediate attention!

Consider moving this repository from blog to jbranchaud.github.io. It is more of a full website than just a blog now and it would be helpful to follow the username.github.io convention for an account related website.

The version of font awesome currently being used on this site is sorely out of date (as in major version numbers out of date). I should update it if I am going to continue to use it.

Add some custom favicon images to this repo so that it doesn't use the default gandi.net ones anymore.

Some posts require listing a few resources at the end. Consider adding some styling for this portion of content so that it is visual set apart from the rest of the document. That will make it easier to scroll to as well.

Look into adding twitter card markup to the posts so that they look better when linked in a tweet. Not really sure what all this requires at this point.

I made a decision the other week to move all the css, js, etc. to the assets directory instead of having Grunt do it. This decision is related to an issue with Jekyll which going all or nothing on excluding the css directory (thus, also excluding the assets/css directory).

The problem now is that my local development environment is crowded with a list of untracked files in the assets whenever I do a git status.

Either go back to the original strategy and see how to get Jekyll to play nicely or try moving the third-party stuff to a vendor directory and ignore just that.

We've had some fun with Grunt, see what Gulp is like by setting it up to automate the same tasks as Grunt is currently automating.

All of the places where posts are listed on the site use a series of div tags that are enumerated by liquid templating engine, rather than list items in an unordered list. I think it is a better practice to use an unordered list and it also gives access to css features like :first and :last.

The atom feed is not getting set up properly because the feed.xml file - which contains liquid templating syntax - is not being properly processed by jekyll. The output in the _site directory is the same as the original file. Figure out why this is happening.

When updating the design of the website, I temporarily ditched the mobile responsiveness of the site (is this mobile-not-first development?). Now that the new design is basically settled, it is time to make it friends with the mobile phone again.

If I can, images should just be properly sized before hand. Also, I should tell images that their max-width is 100% so they don't expand beyond the parent container. What about tall images? Set max-height to something?

This doesn't seem to impact the html that is generated, but there a bunch of errors/warnings that pop up when Maruku tries to process the links that contain liquid syntax for links to other posts. It would be good to clean these up at some point.