DKdkersten·May 9, 2014
This is why I love Enlive[1], Enfocus[2] and Kioo[3] (and Enliven[4] is looking awesome too!).
Your logic stays in your code, the templates are snippets of pure HTML. Dynamic content is generated by manipulating and composing the snippets in code. Snippets can be defined in one large HTML file or many files - up to you. The code uses CSS selectors to choose which parts of the HTML to use and transform.
For example, lets say I have a blog application:
<body>
<div>Welcome to my Blog</div>
<div id="posts">
<div class="post">
<div class="title">My post</div>
<div class="content">Post content here</div>
<div class="comments">
<div class="comment">A comment</div>
</div>
</div>
</div>
</body>
Then my code m
Read the rest
ight look something like this:
(enlive/defsnippet comment-snippet "myfile.html"
[:.comments]
[comments]
[:.comment] (enlive/clone-for [comment comments
(enlivecontent comment))
(enlive/defsnippet post-snippet "myfile.html"
[:#posts]
[posts]
[:.post] (enlive/clone-for [{:keys [title content comments} posts]
[:.title] (enlive/content title)
[:.content] (enlive/content content)
[:.comments] (comment-snippet comments)))
That is, parts of snippets are selected and transformed in some way (changing the content, adding/removing css classes or styles, setting attributes, prepending or appending content, wrapping or unwrapping tags, duplicating for each element in a list, etc). This lets you write your page elements as mocked up snippets with dummy data and then merge them together, fill in content, dynamically update attributes and classes all without putting any logic into the HTML.
This also makes it very designer friendly because they can work in pure HTML and CSS without worrying about templating - they only need to make sure to follow your basic structure outline (ie making sure your selectors match the right thing).
[1] https://github.com/cgrand/enlive
[2] https://github.com/ckirkendall/enfocus
[3] https://github.com/ckirkendall/kioo
[4] https://github.com/cgrand/enliven