PHAMLP for WordPress enables theme creation using the HAML template system. HAML replaces the tag soup of most HTML/PHP templates with a cleaner, hierarchical markup language.
This is a simple plugin that only parses haml and sass/scss with included php code to their respective php source and renders that.
It DOES NOT include any of rail's sophisticated templating tags, like link_to, image_tag etc..
If you want something like that you should take a look at the wordless plugin.
Any plain HTML/PHP theme will work while PHAMLP for WordPress is enabled. But the individual templates that make up a WordPress theme, from index.php to author.php, can be replaced with a corresponding .php.haml file and PHAMLP for WordPress will process them.
If enabled it will also check for sass/scss stylesheet files, compile them and replace the links in the final output.
Just link to them normally like you would to any other .css file.
The plugin parses haml and sass files into cached files in wp-content/phphaml4pw/tmp/php and wp-content/phphaml4pw/tmp/css respectively, for obvious reasons these folders need to be writable by your webserver.
As PHPHaml does not support the complete HAML syntax, take a look at
https://github.com/Baldrs/phphaml for any syntax questions you might have.
Sass parser uses the parser from phamlp (
http://code.google.com/p/phamlp/).
HAML Example
For an example HAML theme check the themes/ folder.
There are two ways you can make a theme:
a) The ruby way is to use layouts. For that place a layout.php.haml file in your theme which basically comprises WP's header and footer.
b) The WP way is to have seperate header.php and footer.php files. Since these are statically included by WP their names cannot be changed (meaning no header.haml - sorry!).
As a workaround, I've implemented partials, just call render("header")/render("footer") in your index.php.haml and _header/_footer.php.haml will be included.
Content_for does not yet work - sorry!