Haml

Haml is a templating engine for HTML. It's designed to make it both easier and
more pleasant to write HTML documents, by eliminating redundancy, reflecting the
underlying structure that the document represents, and providing an elegant syntax
that's both powerful and easy to understand.

Basic Usage

Haml can be used from the command line or as part of a Ruby web framework. The
first step is to install the gem:

gem install haml

After you write some Haml, you can run

haml document.haml

to compile it to HTML. For more information on these commands, check out

Using Haml with Rails

To use Haml with Rails, simply add Haml to your Gemfile and run bundle.

gem 'haml'

Haml 4.1 requires an actively maintained version of Rails (version 3.2 or later).
If you are using Rails 3.0 or 3.1, you should use Haml version 4.0.x:

gem 'haml', '~> 4.0.5'

If you'd like to replace Rails's Erb-based generators with Haml, add
haml-rails to your Gemfile as well.

Formatting

The most basic element of Haml is a shorthand for creating HTML:

%tagname{:attr1 => 'value1', :attr2 => 'value2'} Contents

No end-tag is needed; Haml handles that automatically. If you prefer HTML-style
attributes, you can also use:

%tagname(attr1='value1' attr2='value2') Contents

Adding class and id attributes is even easier. Haml uses the same syntax as
the CSS that styles the document:

%tagname#id.class

In fact, when you're using the <div> tag, it becomes even easier. Because
<div> is such a common element, a tag without a name defaults to a div. So

#foo Hello!

becomes

<div id='foo'>Hello!</div>

Haml uses indentation to bring the individual elements to represent the HTML
structure. A tag's children are indented beneath than the parent tag. Again, a
closing tag is automatically added. For example:

%ul
%li Salt
%li Pepper

becomes:

<ul>
<li>Salt</li>
<li>Pepper</li>
</ul>

You can also put plain text as a child of an element:

%p
Hello,
World!

It's also possible to embed Ruby code into Haml documents. An equals sign, =,
will output the result of the code. A hyphen, -, will run the code but not
output the result. You can even use control statements like if and while:

Indentation

Haml's indentation can be made up of one or more tabs or spaces. However,
indentation must be consistent within a given document. Hard tabs and spaces
can't be mixed, and the same number of tabs or spaces must be used throughout.

Contributing

Contributions are welcomed, but before you get started please read the
guidelines.

After forking and then cloning the repo locally, install Bundler and then use it
to install the development gem dependencies:
~~~sh
gem install bundler
bundle install
~~~

Once this is complete, you should be able to run the test suite:
~~~sh
rake
~~~

You'll get a warning that you need to install haml-spec, so run this:

git submodule update --init

At this point rake should run without error or warning and you are ready to
start working on your patch!

Note that you can also run just one test out of the test suite if you're working
on a specific area:

ruby -Itest test/helper_test.rb -n test_buffer_access

Haml supports Ruby 1.9.2 and higher, so please make sure your changes run on
both 1.9 and 2.0.

Permission is hereby granted, free of charge, to any person obtaining a copy of
this software and associated documentation files (the "Software"), to deal in
the Software without restriction, including without limitation the rights to
use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
the Software, and to permit persons to whom the Software is furnished to do so,
subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.