Jekyll is your page and blog template framework…
I actually got my Reclaim Your Domain blog up and running on Jekyll through GitHub. I’ve been experimenting with mapping a domain on GitHub and getting a basic Jekyll site up ad running. So, for my next trick I decided to push myself a bit and fork Kin Lane’s Reclaim Your Domain site and figure out how the code of Jekyll is working so that I can make the template my own.
After a fair amount of trial and error it worked, and I now have my own reclaim your domain site up and running. I outright stole Kin’s template, but turns out he’s giving it away already. I guess you can’t steal what’s being freely shared. Regardless, I’ll only be using it until I’m on my feet again 😉 I even blogged about my Reclaim process, which I’ll be cross-posting here shortly.
So, the Jekyll experiments are moving right along, and I even got another Ghost blog to play with because Tim Owens has set up a virtual server for Reclaim Hosting that we will be using to provide folks with the next level of services beyond the LAMP stack.
All of which brings me back to the epigraph by Kin Lane at the beginning of this post. More and more the distinction between what you write and the framework you publish it through is blurring. To publish on Jekyll I am locally editing a text file and committing the changes to those files online using GitHub. The page you are writing on is actually your blog engine, it’s kind of old school, and genuinely simple at once, and it provides a sense of your work as more accessible. It’s always already in files rather than pieced together across thousands of tables in an increasingly bloated and fragile database.