enliven

Enlive next: faster, better, broader

Explore on GitHub Read Hacker News discussions

2Distinct people

3Mentions

0Explicit recommenders

241GitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

Enlive next: faster, better, broader

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

cgrand/enlive · linked in 2 of the same discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month3 dated mentions

Observed mentions: 2014-05-09 11:37:06 UTC to 2015-05-26 13:41:37 UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Submissions	Comments
May 2014	2014-05-01 00:00:00 UTC	2014-06-01 00:00:00 UTC	1	0	1
Jun 2014	2014-06-01 00:00:00 UTC	2014-07-01 00:00:00 UTC	0	0	0
Jul 2014	2014-07-01 00:00:00 UTC	2014-08-01 00:00:00 UTC	0	0	0
Aug 2014	2014-08-01 00:00:00 UTC	2014-09-01 00:00:00 UTC	1	1	0
Sep 2014	2014-09-01 00:00:00 UTC	2014-10-01 00:00:00 UTC	0	0	0
Oct 2014	2014-10-01 00:00:00 UTC	2014-11-01 00:00:00 UTC	0	0	0
Nov 2014	2014-11-01 00:00:00 UTC	2014-12-01 00:00:00 UTC	0	0	0
Dec 2014	2014-12-01 00:00:00 UTC	2015-01-01 00:00:00 UTC	0	0	0
Jan 2015	2015-01-01 00:00:00 UTC	2015-02-01 00:00:00 UTC	0	0	0
Feb 2015	2015-02-01 00:00:00 UTC	2015-03-01 00:00:00 UTC	0	0	0
Mar 2015	2015-03-01 00:00:00 UTC	2015-04-01 00:00:00 UTC	0	0	0
Apr 2015	2015-04-01 00:00:00 UTC	2015-05-01 00:00:00 UTC	0	0	0
May 2015	2015-05-01 00:00:00 UTC	2015-06-01 00:00:00 UTC	1	0	1

What Hacker News says

3 sources

dkersten·May 26, 2015

Flow control does not belong in markup. My favourite templating system is enlive[1] (or enliven[2]). You use CSS-style selectors to select snippets of HTML to manipulate and then use code to duplicate, remove, move or replace these snippets, insert content, set attributes etc. The "template" is pure HTML without any additional markup and without any logic. The code then says "repeat this snippet for every item in this list and insert it over there" (or whatever you need). Markup does what its good at, code does what its good at. Works out really nicely. Although nowadays I use reagent and hiccup-style markup and write everything in code (but keep my components as pure and dumb as possible). [1] https://github.com/cgrand/enlive [2] https://github.com/cgrand/enliven

In Show HN: An Isomorphic JavaScript Framework Faster Than React

lkrubner·Aug 21, 2014Submission

The future of Enliven (Clojure template systems)

3 points · Open discussion

dkersten·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

In Your templating engine sucks and everything you've ever written is spaghetti code