By default, a single implementation of this interface is registered of the class org.thymeleaf.linkbuilder.StandardLinkBuilder, which is enough for both offline (non-web) and also web scenarios based on the Servlet API. These attributes will be evaluated once the fragment is included into the target template (the one with the th:insert/th:replace attribute), and they will be able to reference any context variables defined in this target template. Tokens dont need any quotes surrounding them. Our org.thymeleaf.TemplateEngine object is initialized like this: There are many ways of configuring a TemplateEngine object, but for now these few lines of code will teach us enough about the steps needed. See Appendix C for more info. vspace: It defines the vertical spacing around the applet. This is therefore equivalent to: As with conditional values, they can contain nested expressions between parentheses: The No-Operation token is represented by an underscore symbol (_). Note that no validation (against a DTD or XML Schema) will be performed. x[@z="v"] means elements with name x and an attribute called z with value v. If not found on the template where the expression appears, the stack of template calls (insertions) is traversed towards the originally processed template (the root), until selector matches at some level. But what will happen when we process it with Thymeleaf? name: It defines a name for an applet. By default HSPACE is a small non-zero number. Thymeleaf parser-level comment blocks, 11.3. Lets have a look at a more complete example of a TEXT template, a plain text email template: After executing, the result of this could be something like: And another example in JAVASCRIPT template mode, a greeter.js file, we process as a textual template and which result we call from our HTML pages. Example: Now we know about these utility objects, we could use them to change the way in which we show the date in our home page. Note that HTML or XML templates can be also processed as TEXT, in which case they will not be parsed as markup, and every tag, DOCTYPE, comment, etc, will be treated as mere text. The key difference between textual template modes and the markup ones is that in a textual template there are no tags into which to insert logic in the form of attributes, so we have to rely on other mechanisms. Actually, this is something that can be applied to any piece of data, but given the size that in-memory collections might have, retrieving collections that are meant to be iterated is the most common case for this scenario. A big advantage of this approach to fragments is that you can write your fragments in pages that are perfectly displayable by a browser, with a complete and even valid markup structure, while still retaining the ability to make Thymeleaf include them into other templates. The default direction of scrolling is left. Note: Value less then 60 is not acceptable, unless truespeed is specified. latex latexrotatingusepackage{rotating}\begin{command}{x}{command} sideways, turn, rotate{x} Thymeleaf pays quite a lot of attention to logging, and always tries to offer the maximum amount of useful information through its logging interface. Thymeleaf also allows the use of inlining in CSS