node package manager
Painless code sharing. npm Orgs help your team discover, share, and reuse code. Create a free org »



  (        )
 '          '

An s-expression template engine with no external dependencies.

Templates look like this:

    (title "Hello")
    (script src="/js/my-app.js"))
        (p "Welcome to my site, " :name "!")))
            (a href="/index.html" "Home"))))))

Use it like this:

var template= settee(source),
    html= template({ name:"Matt" })

It's great to drink coffee while lounging on the settee!

template= settee source
html= template name:"Matt"


Templates are rudimentary s-expressions (think LISP). S-expressions, if you aren't familiar, are just lists of lists. Each list is surrounded in (parenthesis).

In Settee, the first list item is the tag name.




You can set attributes using attr=value syntax.

(div class=body)
<div class="body"></div>

You can use css-style syntax on the tag name to set the class names and id:

<div id="main" class="body"></div>

Nested lists generate nested HTML:

  (header "Heading")
    (p "Content")
  <section class="body">

Note: The indented whitespace is added for readability, the generated output will not have any whitepace between tags.

Settee also supports a shorter syntax. You don't need the indentions or closing parenthesis for the last list. So that previous template could also look like this:

(article (header "Heading")(section.body (p "Content"

You can insert values from the rendering context using :varname syntax:

(div "hello " :name)

Given a context of { name:'Matt' }:

<div>hello Matt</div>

There some built in tags to help you build your templates:

(if (eq :name "Matt")
  (div "Hello Matt")
  (div "You aren't Matt!"))

Builtins: if, unless, eq (aliased as = and is), neq (aliased as != and isnt).

There is a special helper . that returns all the child lists with adding anything around them. This is because Settee expects to have only one root list.

  (div "One")
  (div "Two")

Settee also support simple looping. Each loop has access to :item and :index in the render context.

  (loop :items
    (li data-id=:index :item)
settee.render( src, { items:["A", 'B'] } );
  <li data-id="0">A</li>
  <li data-id="1">B</li>

Method Signatures

As function:

settee( source ); // source= String | Array 
// => returns template function 

If source isn't a String, Settee will assume it's precompiled source and build the template function with it. Otherwise the source is parsed first.

The resulting template function looks like this:

template( context ); // context= Object  
// => returns rendered template as a String 

Just send the rendering context as an object.

If you want to do it in one pass, use render:

settee.render( source, context ); 
// => returns rendered template as a String 

Custom Tags / Partials

You can define custom tags, or partials, in two ways. The first way is as a sub-template:

settee.define 'layout''''
  (header "My App")
  (section.body :block1)
  (footer :block2))

You can then use it as a tag in your templates:

  (div "Content Area")
  (div "Copyright me"))

The resulting template compiles to (whitespace added for redability):

<article class="layout">
  <header>My App</header>
  <section class="body">
    <div>Content Area</div>
    <div>Copyright me</div>

If you need a little more control, you can specify a handler function that works at a lower level:

settee.define 'widget'(tag, attrs, children)->
  # types: tag= String, attrs= Object, children= Array 
  # This function should return a 'rendered' String. 
  """<div id="#{ or 'widget' }">#{ children.join '' }</div>"""


Want to precompile your templates from node for added speed?

Install settee-templates:

npm install settee-templates


settee= require 'settee-templates'
source= '(html (body'
output= settee.precompile source 
# => function anonymous(b) {return b('html', {  }, [b('body', {  }, [])]); } 

You'll still need to include settee in your page, but it will skip the parse phase.

You can include settee.runtime.js if all you plan to use is precompiled templates. The runtime version omits the parser and compiler code.


Original S-Expression parser code based on: