Revamp article section

_includes/header.html

@@ -1,15 +1,13 @@
-{% case page.url %}
-{% when '/' %}
-{% assign home = "active" %}
+{% assign home = " " %}
 {% assign articles = " " %}
 {% assign about = " " %}
-{% when '/articles' %}
-{% assign home = " " %}
+
+{% case page.url %}
+{% when '/index.html' %}
+{% assign home = "active" %}
+{% when '/articles.html', '/archive.html' %}
 {% assign articles = "active" %}
-{% assign about = " " %}
-{% when '/about' %}
-{% assign home = " " %}
-{% assign articles = " " %}
+{% when '/about.html' %}
 {% assign about = "active" %}
 {% endcase %}
 

_posts/2011-01-24-new-site.markdown

@@ -2,27 +2,29 @@
 title: New site
 description: Why I chose to design and deploy a new website with jekyll on github
 keywords: lucapette, site, github, jekyll
+category: writing
 layout: articles
 ---
 Hi everyone,
 
-Finally, I have a new site. For months I've been thinking about the idea of building a new one. I was searching for a new way of handling my semi-static content and I think I've found a system I really like.
+Finally, I have a new site. For months I've been thinking about the idea of
+building a new one. I was searching for a new way of handling my semi-static
+content and I found a system I really like.
 
 The content of the site is generated by [jekyll](http://jekyllrb.com) and the site itself is hosted by [github](http://pages.github.com):
 
 - [jekyll](http://jekyllrb.com)
 
-  I like it. It is simple and light and has all the features I need for
-  my site. It is well-designed and it is simple to use. Jekyll has a
-  super lightweight configuration and you can create a site within
-  minutes.
+  I like it. It is simple and light and has all the features I need for my
+  site. It is well-designed and it is simple to use. Jekyll has a lightweight
+  configuration and you can create a site within minutes.
 
 - [github](http://pages.github.com)
 
-  I really like the work done by the github guys and I really like git.
-  I use it for all my project, I use it even at work (I say *even*
-  because I work in Italy, you know). So the idea of pushing a commit on
-  a git repository and having my changes published on my site
-  immediately is something I find wonderful.
+  I really like the work done by the github folks and I really like git.  I use
+  it for all my project, I use it even at work (I say *even* because I work in
+  Italy, you know). So the idea of pushing a commit on a git repository and
+  having my changes published on my site immediately is something I find
+  wonderful.
 
 I like my new creation (especially considering my web design limits) and I hope it will help me to post more often.

_posts/2011-02-11-a-review-of-ruby-best-practices.markdown

@@ -2,124 +2,116 @@
 title: A review of Ruby Best Practices
 description:  A review of Ruby Best Practices by Gregory Brown. Published by O'Reilly in June 2009
 keywords: ruby best practices, book, review, Gregory Brown
+category: reading
 layout: articles
 ---
 
 Introduction
 ------------
 
-[Ruby Best Practices](http://rubybestpractices.com/) is the latest book
-of a Ruby-related series I have read in the past weeks. In this period,
-I’m focusing myself on learning real Ruby, I mean there is a big
-difference between *using Ruby to write code* and *coding in Ruby to
-solve problems*. I think I’m on the right path to master Ruby and a big
-part of my recent improvements derives from reading books. In the
-following weeks I’m going to review all the Ruby-related books I have
-recently read as a way to give back to the community and as a way to
-wrap-up what I learnt.
-
-<div class="clearfix"> </div>
+[Ruby Best Practices](http://rubybestpractices.com/) is the latest book of a
+Ruby-related series I have read in the past weeks. In this period, I’m
+focusing myself on learning real Ruby, I mean there is a big difference
+between *using Ruby to write code* and *coding in Ruby to solve problems*. I
+think I’m on the right path to master Ruby and a big part of my recent
+improvements derives from reading books. In the following weeks I’m going to
+review all the Ruby-related books I have recently read as a way to give back
+to the community and as a way to wrap-up what I learnt.
+
 The book
 --------
 
-Ruby Best Practices is well-organized and it covers many interesting
-aspects of the Ruby programming world. I think the main aim of the book
-was to offer an optimal introduction into how a problem can be *well*
-solved and how Ruby should be used to solve it. In my opinion, the book
-is well-written and the aim is respected throughout most chapters. One
-of the most interesting aspects of this book is the complete
-independence of the topics covered in the chapters, in fact you could
-simply read only the ones that interest you and I consider it a good
-point.
+Ruby Best Practices is well-organized and it covers many interesting aspects
+of the Ruby programming world. I think the main aim of the book was to offer
+an optimal introduction into how a problem can be *well* solved and how Ruby
+should be used to solve it. In my opinion, the book is well-written and the
+aim is respected throughout most chapters. One of the most interesting aspects
+of this book is the complete independence of the topics covered in the
+chapters, in fact you could simply read only the ones that interest you and I
+consider it a good point.
 
 My consideration grouped by chapter:
 
 - **Driving Code Through Test**
 
   The first chapter is one of my favourites. Unfortunately, I work in a
-  country where there is no culture about tests. I really liked the
-  examples presented, this chapter helped me to understand better how to
-  write fine tests.
+  country where there is no culture about tests. I really liked the examples
+  presented, this chapter helped me to understand better how to write fine
+  tests.
 
 - **Designing Beautiful APIs**
 
-  The concepts behind the topics covered in this chapter deserve more than
-  a chapter. This aspect of programming can be very important especially
-  while using Ruby, when you are new to it you often feel you are using it
-  without understanding its true beauty. You write Ruby code but you don’t
-  speak Ruby yet. Then, you need something that puts you on the right path
-  to speak this wonderful language. This chapter can help you to enter the
-  path because it is full of great advice about how APIs can be written.
-  The examples about *parameters* is the most interesting part of the
-  chapter.
+  The concepts behind the topics covered in this chapter deserve more than a
+  chapter. This aspect of programming can be very important especially while
+  using Ruby, when you are new to it you often feel you are using it without
+  understanding its true beauty. You write Ruby code but you don’t speak Ruby
+  yet. Then, you need something that puts you on the right path to speak this
+  wonderful language. This chapter can help you to enter the path because it
+  is full of great advice about how APIs can be written.  The examples about
+  *parameters* is the most interesting part of the chapter.
 
 - **Mastering The Dynamic Toolkit**
 
-  This is the most difficult chapter to read but, in spite of that, it is
-  one of the most interesting parts of the book. Surely it is one of those
-  you shouldn’t miss. If you are relatively new to Ruby you’ll enjoy it
-  because Gregory Brown covers the *“meta”* side of Ruby in it. In my
-  opinion, *this* is the most notable aspect of Ruby that makes it
-  wonderful.
+  This is the most difficult chapter to read but, in spite of that, it is one
+  of the most interesting parts of the book. Surely it is one of those you
+  shouldn’t miss. If you are relatively new to Ruby you’ll enjoy it because
+  Gregory Brown covers the *“meta”* side of Ruby in it. In my opinion, *this*
+  is the most notable aspect of Ruby that makes it wonderful.
 
 - **Text Processing File Management**
 
-  I have to be honest, I didn’t like this chapter. I don’t get the point
-  of it. Maybe it’s a problem of mine, I don’t know, but after two
-  wonderful chapters I started reading this one with great expectations
-  for the topic I really like, and I got a bit disappointed when I found
-  out I didn’t like the chapter.
+  I have to be honest, I didn’t like this chapter. I don’t get the point of
+  it. Maybe it’s my problem, I don’t know, but after two wonderful chapters I
+  started reading this one with great expectations for the topic I really
+  like, and I got a bit disappointed when I found out I didn’t like the
+  chapter.
 
 - **Functional Programming Techniques**
 
-  Generally speaking, functional programming is not a simple programming
-  topic out there but this book covers it in a very nice way and offers to
-  the reader many interesting examples and pieces of code about this
-  techniques.
+  Generally speaking, functional programming is not a simple programming topic
+  out there but this book covers it in a very nice way and offers to the
+  reader many interesting examples and pieces of code about this techniques.
 
 - **When Things Go Wrong**
 
-  Yes, I know that a book about best practices must contain a chapter
-  about debugging and I agree with that. However, I think it is not so a
-  Ruby-related topic, It’s a more general topic that deserves even more
-  than a chapter in a book. That’s why I wouldn’t expect to find it in a
-  Ruby book, just saying:) By the way, I read this chapter and it’s worth
-  reading because you can find good advice anyway.
+  Yes, I know that a book about best practices must contain a chapter about
+  debugging and I agree with that. However, I think it is not so a
+  Ruby-related topic, It’s a more general topic that deserves even more than a
+  chapter in a book. That’s why I wouldn’t expect to find it in a Ruby book,
+  just saying:) By the way, I read this chapter and it’s worth reading because
+  you can find good advice anyway.
 
 - **Reducing Cultural Barriers**
 
-  I have to be honest here too. For the most part I didn’t read this
-  chapter. I have to read too many books in my life so I tend to read only
-  things I really care about. Thus, I can’t express a complete opinion
-  about this chapter but surely you should read it if you care about the
-  specific topic.
+  I have to be honest here too. For the most part I didn’t read this chapter.
+  I have to read too many books in my life so I tend to read only things I
+  really care about. Thus, I can’t express a complete opinion about this
+  chapter but surely you should read it if you care about the specific topic.
 
 - **Skillful Project Maintenance**
 
-  The idea behind this chapter is a good one. It is a bit unusual to read
-  why a real project like [haml](http://haml-lang.com/) can be considered
+  The idea behind this chapter is a good one. It is a bit unusual to read why
+  a real project like [haml](http://haml-lang.com/) can be considered
   maintainable. This chapter will enlighten you on generally badly covered
   aspects of the reason behind a good project. You should read it.\
-  Furthermore, the book comes with three nice appendixes and I really
-  liked the first one. It is about writing backward-compatible code and I
-  have to say that I didn’t know much about this particular problem. This
-  appendix helped me a lot. I found the other two appendixes less
-  interesting but still very enjoyable if you care about the topics
-  covered.
+  Furthermore, the book comes with three nice appendixes and I really liked
+  the first one. It is about writing backward-compatible code and I have to
+  say that I didn’t know much about this particular problem. This appendix
+  helped me a lot. I found the other two appendixes less interesting but still
+  very enjoyable if you care about the topics covered.
 
 What I liked most
 -----------------
 
-I have a general good opinion of this book. It has several good aspects
-and above all it offers a very good approach to Ruby programming and to
-problem solving. While reading the book I found out nice things about
-Ruby and Ruby libraries and this is the aspect of the book I enjoyed a
-lot.
+I have a general good opinion of this book. It has several good aspects and
+above all it offers a very good approach to Ruby programming and to problem
+solving. While reading the book I found out nice things about Ruby and Ruby
+libraries and this is the aspect of the book I enjoyed a lot.
 
 What I disliked most
 --------------------
 
-There are a few aspects I disliked in the book. If I have to be critic
-about it I would say it covers aspects of programming that I consider
-neither Ruby-related nor “Best Practices” but, obviously, it is just an
-opinion. However, you **should read** it if you care about Ruby.
+There are a few aspects I disliked in the book. If I have to be critic about
+it I would say it covers aspects of programming that I consider neither
+Ruby-related nor “Best Practices” but, obviously, it is just an opinion.
+However, you **should read** it if you care about Ruby.

_posts/2011-02-16-vim-for-rails-developers-what-you-cant-miss.markdown

@@ -2,8 +2,10 @@
 title: "Vim for rails developers: what you can't miss"
 description: my first article of the series "vim for rails developer". I will use the article as an index for the series
 keywords: vim, rails,rails.vim, NERDTree, FuzzyFinderTextMate, codepath
+category: vim
 layout: articles
 ---
+
 Vim is my editor of choice and Rails is my framework. I think many of us have
 the same taste and I want to share with you my experiences while using both.
 I'm going to write a series of posts regarding this topic. I start with _what

_posts/2011-02-24-a-review-of-metaprogramming-ruby.markdown

@@ -1,7 +1,8 @@
 ---
 title: A review of Metaprogramming Ruby
-description:  A review of Metaprogramming Ruby by Paolo Perrotta. Published by The Pragmatic Bookshelf in 2010
+description: Published by The Pragmatic Bookshelf in 2010
 keywords: metaprogramming ruby, book, review, Paolo Perrotta
+category: reading
 layout: articles
 ---
 

_posts/2011-03-08-why-you-should-spend-some-time-configuring-irb.markdown

@@ -2,6 +2,7 @@
 title: Why you should spend some time configuring irb
 description:  Why you should spend some time configuring IRB.
 keywords: ruby, irb, console
+category: ruby
 layout: articles
 ---
 

_posts/2011-03-10-vim-for-rails-developers-a-screencast-review.markdown

@@ -2,11 +2,12 @@
 title: "Vim for rails developers: a screencast review"
 description: a review of a screencast by Ben Orenstein
 keywords: vim, rails, screencast
+category: vim
 layout: articles
 ---
 
 I have recently published my first
-[article](http://lucapette.com/vim/rails/vim-for-rails-developers-what-you-cant-miss/)
+[article](/vim-for-rails-developers-what-you-cant-miss/)
 of this series. It got a very nice feedback and I am very glad about that, it
 encourages me to keep it on. As part of the feedback I got a very nice email
 from [Ben Orenstein](http://codeulate.com/). He was so kind to send me a copy
@@ -20,11 +21,11 @@ work is definitely worth spreading.
 ## The screencast
 
 The screencast has a good recording quality and Ben speak a very clear
-language (it does count for non-native speakers you know :)). So I think you
+English (it does count for non-native speakers you know :)). So I think you
 should be able to follow all the part of it without problems. Furthermore, the
 screencast is neither long nor short, the length is just perfect.
 
-###  Introduction
+### Introduction
 
 The screencast starts with a short and nice introduction. It shows you how
 to improve your typing skills, Ben gives you nice suggestions on resources

_posts/2011-03-18-improving-irb-history.markdown

@@ -2,11 +2,12 @@
 title: Improving IRB history
 description: Improving IRB history. Some ways to improve your interaction with IRB history
 keywords: ruby, irb, console
+category: ruby
 layout: articles
 ---
 
 I’ve started to consider irb
-[configurations](http://lucapette.com/irb/why-you-should-spend-some-time-configuring-irb/)
+[configurations](/why-you-should-spend-some-time-configuring-irb/)
 as a way to improve my productivity. Following this path I’ve got some nice
 stuff in my [irbrc](https://github.com/lucapette/dotfiles/blob/master/irbrc).
 In the last days I was thinking about how to make irb history more similar to

_posts/2011-03-31-vim-for-rails-developers-indenting-code.markdown

@@ -2,6 +2,7 @@
 title: "Vim for rails developers: indenting code"
 description: How you can indent your code preserving the cursor position with a Vim mapping
 keywords: vim, rails, indenting code, tip, map, mapping
+category: vim
 layout: articles
 ---
 

_posts/2011-05-06-a-review-of-the-rails-3-way.markdown

@@ -1,7 +1,8 @@
 ---
 title: A review of The Rails 3 way
-description:  A review of The Rails 3 way by Obie Fernandez. Published by Addison Wesley in Dicember 2010
+description: Published by Addison Wesley in Dicember 2010
 keywords: the rails 3 way, book, review, Obie Fernandez
+category: reading
 layout: articles
 ---