:markdown
## Heading Content
This is just some *emphatic* text. Maybe I'll talk about `$BASH_VERSION` here.1. :markdown doesn't accept classes, ids, or any other modifiers like %tags. This makes for some difficult fugging.
2. You cant do - ruby or = ruby under :markdown or similar.
This is terribly inconsistent and requires some stupid work arounds.
2. You can do the equivalent of = in Haml filters by enclosing the Ruby in #{}. For example, where sign_up_path is a Ruby helper method:
:markdown
[Sign Up](#{sign_up_path})
Personally, in the past I've put large blocks of mostly-static content (eg, a TOS) in a erb template or partial. I now often use the markdown filter for things like help documentation in my sites. :markdown.red#item2
%list:markdown.red#item2
%list.red#item2:markdown
... #id.class
:markdown
[A link](/path)
outputs: <div id="id" class="class">
<a href="/path">A link</a>
</div>PS - You spelled "flame-bait" wrong.
PS - Pointing out my misspelling of "flame-bait" is flame-bait.
No doubt, except that I hate Haml. You're absolutely right that it was a quick sloppy post on my part. That said, I stand by my feelings (as personal reactions to how Haml looks and the choices it makes) and the HTML2Haml site suggested (by implication of how it converts things) that newlines was the way to do it. I absolutely didn't realize that you could include straight HTML inside Haml (and the docs don't make this overwhelmingly obvious). I now see this in the docs under "Plain Text":
> Note that HTML tags are passed through unmodified as well. If you have some HTML you don’t want to convert to Haml, or you’re converting a file line-by-line, you can just include it as-is.
But I wasn't looking in the section on "Plain Text" since I wanted marked-up text. Still, my fault for not reading the docs more carefully before ranting.
Thanks for the tip and response (to you and to everyone here). I'm updating the post now. Changes should go up in no more than an hour. Edit: Changes are live. Thanks again to all commenters.
So hey, to make something of this discussion: Am I correct in thinking HAML is fairly closely tied to Ruby? I'm quite familiar with Markdown* , but don't use Ruby. As long as we're committing to a given language for an ersatz HTML syntax, I prefer CL-WHO (http://weitz.de/cl-who/) or a similar approach in Lua, JSON, etc.
Also, it doesn't look like there's cross-language support, which is a major advantage for Markdown, JSON, and other such formats.
* My favorite implementation is discount (http://www.pell.portland.or.us/~orc/Code/discount/), which is written in C, quite fast, and has a good test suite and pretty clean API.
%div{:class => [ruby code here]}
Although there are PHP ports out there in progress.
There is also a Ruby Discount gem, rdiscount.
2. It would be deadly easy to have inline markup. Say: %p La la %strong la % la la.
3. The whole point of using HAML is to get rid of using the annoying HTML syntax. (Remember the tagline 'Markup haiku'?
The OP provides the following example as a irrefutable damnation of haml:
%h2 Heading content
%p This is just some
They complain about the inability to nest em and code tags on a single line.Hey OP, try this:
%h2 Heading content
%p This is just some <em>emphatic</em> text. Maybe I'll talk about <code>$BASH_VERSION</code> here.
or did you forget that you can mix html in with haml where needed? Pointless, sloppy, flame-bait. /endrant
I was reluctant to learn HAML myself, but after being "forced" to do so on a project last spring, I actually cringe when I see standard HTML and CSS now. Not only has haml shrunk the size of my code by almost half, it has made it easier to scan, maintain, and my css matches up much more closely to my markup. Simply put, HAML/SASS is one of the biggest productivity/sanity boosts I've experienced in my young development career.
*edit: spelling, and formatting.