Jekyll & Hyde


So, as you know, or maybe don’t, there is some debate about CMSes– I posted about it here. People (mainly developers) are falling all over simple, minimalistic blogging platforms like Jekyll and will poo-poo your choice of WordPress if they get the chance.

So while when I first tried Jekyll I was intimidated and quit, after reading some random developer go on about the virtues of Jekyll I fired it up and tried it. I was lost, immediately.

It’s not that I’m stupid. I am used to WordPress and Byword. So having some Octopress and YAML help me format and write posts, understanding the theme I chose, its directory structure, what jekyll commands were and what they did, were extremely new to me. It’s bad enough I don’t always read instructions fully. I thought this can’t be this difficult. Well, my ignorance preceded me. I deleted my Git repo 10 ten times at least. I screwed up and deleted the .git folder out of my main repo while not deleting the cloned theme’s folder with its .git folder within which meant whatever files I was pushing were going to the forked repo on GitHub. Talk about stupid. But what it was is that I had worked on this tirelessly for two weeks. If I had just looked at the theme instructions, I would have had an easier time.

jekyll build

This will populate all your changes into the /_site folder. So if you edit the site wide _config.yml file, the navigation.yml file or add posts or pages, this will build the site locally on your machine.

jekyll serve

This will allow you to serve up your site at this local host :4000. Does it look good? No? Rebuild it. If it does? Push it to GitHub.

To make a new post:

octopress new post “Post Title” –dir posts

This theme I am using uses the ephemeral framework Octopress. I LOVE Octopress. Why? It will format YAML front matter on your markdown file, format the title of your file, and place it in the directory you specify. I don’t have to continue to write YAML by hand or use Octorpress. Guess which one I chose?

So the site is finished and I absolutely love that it is independently hosted on GitHub with an .io domain (trendy and I like it) and most importantly, it’s gorgeous.

The first podcast is up there. You can find it here:

My Coding Journey– First Episode is Live!!

Check it out and keep coming back to that site for more podcasts.

@%$(*&^%[email protected]! .gitmodules


I have a new interest: Jekyll. There is some debate as to WordPress or Jekyll being the best CMS for enterprise blogs, personal blogs, etc. I was following a thread on 1stwebdesigner on Facebook and it heavily promotes WordPress. Tons of readers have renounced WordPress in favor of other CMSes, one being Jekyll, which was built by GitHub.

I started with Jekyll months ago when seeing my buddy Mark build his blog with GitHub Pages. It was after I styled this one. I was starting to get sick and brain farts. So I didn’t do anything with it. Until I saw this Facebook post.

I spent most of my Saturday evening setting up Jekyll Bootstrap for a theme. There were so many errors– a dirty hash (which you can ignore) and jekyll-bootstrap not mapping itself in the .gitmodule file. I tried to clone the repo again. Nope. I deleted the extraneous .git folder and map the jekyll-bootstrp submodule back to the .gitmodule file. Still got the error. Tried to re-clone the repo again. Said jekyll-bootstrap existed. Deleted it, cloned it again, and got the:

The page build failed with the following error:

The submodule jekyll-bootstrap was not properly initialized with a .gitmodules file. For more information, see

In frustration, I deleted the whole repo (because I waited for GitHub to get back to me and I was frustrated and impatient) and remade it, and used an automatic page generator. But I am not done…