Programming language: Go
Tags: Template Engines    

damsel alternatives and similar packages

Based on the "Template Engines" category.
Alternatively, view damsel alternatives based on common mentions on social networks and blogs.

Do you think we are missing an alternative of damsel or a related project?

Add another 'Template Engines' Package


Damsel GoDoc Build Status

Markup language featuring html outlining via css-selectors, extensible via pkg html/template and others.


This package expects to exist at $GOPATH/src/dasa.cc/damsel and can be installed with:

go get dasa.cc/damsel

Command Line

A command line utility can be installed with:

go get dasa.cc/damsel/cmd/damsel

View help with:

damsel -h



Package damsel provides html outlining via css-selectors and common template functionality.


Tags are specified with %tag, #id, .class where #id and .class become a div if no %tag is specified. Multiple classes can be specified but only one #id tag should be specified for an element. It's also important that an #id tag is unique in the document as damsel facilitates overriding content of a document via an #id tag.

%html %body
  #content.border Hello, World


Attributes can be inlined, line-breaked, or a combination of such. Provide quotes around the attribute value to escape brackets.

%html %body




  %span[a][b] Attributes do not require values

Text and Whitespace

Whitespace can be manipulated as described below, but it's worth pointing out that large amounts of content are simply not suitable for such document types (Damsel, Haml, etc).

%p One
  \ Two
  \ Three

%p    One Two Three

Both paragraphs will be rendered the same. Use of a backslash controls whitespace, including inlined text.

%p \ One Two Three

This would insert a space before One.

Whitespace can be preserved using `

%p `this is some
text and all whitespace
    is preserved as-is`

HTML Comments

Supports commenting out blocks of code via html comments with optional text and browser specfic IFs. This also includes DOCTYPE declarations.

%html %body
  ! %ul
    %li 1
    %li 2

The use of ! as a block element, causing %ul to become inlined, will cause the entire block to become commented out. The ! could also be placed after the body tag in this case. You can also nest items under a comment.

%html %body
  ! here's a comment though it's not required
    %h1 Hello World

    ! this comment doesn't enclose any tags
    %span Hello World

  ![if IE] %p Internet Explorer


There is basic support for actions. An action is just another way of calling a function while also preserving indention of the inner content lines, making this suitable for parsing other indention based markup. Once an action has been processed, the lexer will parse the result as though it was part of the original document.

In time, this package will facilitate custom functions. Currently included actions are js, css, include, and extends.

%html %head
  :css /css/

This would generate the following document.

%html %head

Reusable Templates

Damsel allows any element with an id specified to be overridden. Also required is at least one root node that will serve as the main document output. Additional root nodes are checked against the first for overridable content.

%html %body
    %p Hello

#content OVERRIDE

The would produce the following output.

  <div id="content">OVERRIDE</div>

This functionality is also facilitated with the action extends.

:extends overlay.dmsl

#content OVERRIDE

If you wish to append child nodes instead of overriding the original content, specify a super attribute.

:extends overlay.dmsl

  %p A second paragraph

The action include uses the whitespace preceding its declaration to insert content from a separate document into the current. For example, given the following document:

  %li One
  %li Two

included in the following document:

%html %body
    %h1 My Numbers
    :include numbers.dmsl

would produce the following document:

%html %body
    %h1 My Numbers
      %li One
      %li Two

Other Template Integration

This package should be ok for use with most text templating options. Helpers that provide integration with html/template take the following steps.

- Call dmsl/parse.ActionParse(b []byte)
- Pass the result to package html/template and execute
- Call dmsl/parse.DocParse(b []byte)
- Display result

Calling dmsl.NewHtmlTemplate will return an instance that parses actions and passes the result to html/template.Template. Call Execute(interface{}) to produce the final result. For example, given [10][10]int:

%html %body
  %table {range .}
    %tr {range .}
      %td {.}

At one-point the {end} was optional with deeper integration of html/template, but in practice this created confusion and errors except for the most trivial of examples (above).

Here's another example.

%html %body
  {range .}

    {if .}

    {range .}
      %td {.}

    %tr %td None

    %p some trailing text