Skip to content
Browse files

Small edit.

  • Loading branch information...
1 parent 810689a commit 42bc160df334c2a72ae31480e43b439bf46d30e3 @marano committed May 2, 2013
Showing with 1 addition and 1 deletion.
  1. +1 −1 articles/2013_05_01_Introducing_rollin.mk
View
2 articles/2013_05_01_Introducing_rollin.mk
@@ -1,6 +1,6 @@
## Yet another Ruby blog
-I recently moved to China, and the past three days was a big holiday here. My Chinese is still pretty bad and it kinda of limits my, let's say, entertainment options. And that's why I ended up studying Javascript frameworks in order to do a presentation at the office. After jumping from blog to blog I've gathered some amount of data around this topic in a big markdown file. And then I thought - wouldn't it be great if could publish it on blog? I have several stuff that I want to post about and now seemed a perfect time to start it. So let's stop talking about me.
+I recently moved to China, and the past three days was a big holiday here. My Chinese is still pretty bad and it kinda of limits my, let's say, entertainment options. And that's why I ended up studying Javascript frameworks in order to do a presentation at the office. After jumping from blog to blog I've gathered some amount of data around this topic in a big markdown file. And then I thought - wouldn't it be great if could publish it on blog? I have a bunch of stuff I want to post about and now seemed a perfect time to start it. So let's stop talking about me.
So I went after blogging engines. If you ask me why I didn't scaffold it with Rails I'm gonna blow your head. My requirements were that it needed to be easy to style so I could make it look pretty, that it was filesystem based so I could manage it with git, and that it was markdown. [The Ruby Toolbox](https://www.ruby-toolbox.com/) has listed a bunch of Ruby engines in it's [Blog Engine](https://www.ruby-toolbox.com/categories/Blog_Engines), no wonder! And couldn't find much more than that at the webz.

0 comments on commit 42bc160

Please sign in to comment.
Something went wrong with that request. Please try again.