Work towards #56: Splitting up the README

I did the job and splitted up the readme, hopefully everything was
splitted correctly...

template-method/index.md

@@ -0,0 +1,19 @@
+---
+layout: pattern
+title: Template method
+folder: template-method
+categories: pattern_cat
+tags: pattern_tag
+---
+
+**Intent:** Define the skeleton of an algorithm in an operation, deferring some
+steps to subclasses. Template method lets subclasses redefine certain steps of
+an algorithm without changing the algorithm's structure.
+
+![alt text](./etc/template-method_1.png "Template Method")
+
+**Applicability:** The Template Method pattern should be used
+
+* to implement the invariant parts of an algorithm once and leave it up to subclasses to implement the behavior that can vary
+* when common behavior among subclasses should be factored and localized in a common class to avoid code duplication. This is good example of "refactoring to generalize" as described by Opdyke and Johnson. You first identify the differences in the existing code and then separate the differences into new operations. Finally, you replace the differing code with a template method that calls one of these new operations
+* to control subclasses extensions. You can define a template method that calls "hook" operations at specific points, thereby permitting extensions only at those points