params)` inserts the given parameters to the template
+* `render(Template template, Object... params)` proposes an easier way to pass parameters. However, one parameter
+over two must be a string (the parameter name), while the following is the value:
+
+ return ok(render(template, "welcome", "hello", "age", 1, "colors", new String[] {"red", "blue"}));
+
+The `render` method is wrapped within a `ok` method indicating the type of response. Obviously, you can use any other
+ type of result.
+
+Some values are automatically given to the template engine:
+
+* the parameters of the request
+* the values stored in the session
+* the value stored in the flash scope
+
+==== Some Thymeleaf constructions
+
+Now we have seen how template can be used, let's see some general construction patterns we use in templates:
+
+**Variable:**
+
+ this will be replace by the variable
+ this will be replace by the variable (unescape so won't remove the contained HTML elements)
+
+
+**Internationalized variable:**
+
+ this will be replace by the variable using the request locale
+
+WARNING: Internationalized value are directly retrieved from the internationalization service from Wisdom.
+
+**Iteration:**
+
+You can iterate on collections, arrays, maps...
+
+
+
+ | Onions |
+ 2.41 |
+ yes |
+
+
+**Conditionals:**
+
+
+ true or false according to the prod.isStock value
+ |
+
+ display this link comments if not empty
+
+
+TIP: Check the http://www.thymeleaf.org/doc/html/Using-Thymeleaf.html[Thymeleaf documentation] to find more.
+
+==== Fragments and Layout
+
+Templates are generally used to create layouts. Thymeleaf allows to create _fragments_, and to include them in the
+_main_ template.
+
+Fragments are identified part of a template. For example, the following snippet defined two fragments: `my-content`
+and `sub-content`.
+
+[source,xml,indent=0]
+----
+include::{resourcedir}/templates/content.thl.html[]
+----
+
+Fragments can be included either using:
+
+*`th:include`: include the fragment 'under' the element using the directive
+*`th:replace`: replace the element using this directive with the fragment content
+
+The value of theses directive is formed by `name_of_the_template_defining_the_fragments :: fragment_name`. For
+example, if the previous fragment are defined in `content.thl.html`, including them would look like:
+
+[source,xml,indent=0]
+----
+include::{resourcedir}/templates/page.thl.html[]
+----
+
+TIPS: fragments can use any variable given to the template engine.
+
+==== Using the router from the template
+
+A template can use a special object named `#routes` to retrieve the url of action methods. In the following snippet,
+the `action` attribute is assigned to the url of the `upload` method of the current controller (the controller having
+ requests the template rendering).
+
+[source,xml,indent=0]
+----
+th:attr="action=${#routes.route('upload')}"
+----
+
+You can also ask for the url of an action method receiving parameters:
+
+[source,xml,indent=0]
+----
+th:attr="action=${#routes.route('upload', 'param', 'value', 'param2', 'value2')}"
+----
+
+Finally, you can target method from other controllers with:
+
+[source,xml,indent=0]
+----
+th:attr="action=${#routes
+ .route(`org.acme.controller.MyOtherController`, 'upload', 'param', 'value')}"
+----
+
+If the route cannot be found, the template rendering fails.
+
+
+
+
+
+
diff --git a/documentation/src/main/resources/templates/content.thl.html b/documentation/src/main/resources/templates/content.thl.html
new file mode 100644
index 000000000..23a65236b
--- /dev/null
+++ b/documentation/src/main/resources/templates/content.thl.html
@@ -0,0 +1,18 @@
+
+
+
+
+ This is a fragment
+
+
+
+
+
Hello my name
+
+
+
+
This is the first step to Wisdom, follow us...
+
Hello
+
+
+
\ No newline at end of file