Sorry for being unclear, I asked because I am genuinely curious and I think all the yesod people love hearing feedback. If you check the yesodweb google group, you'll see that Greg and Michael are constantly begging for and responding to constructive feedback.
> Okay, whats wrong with hamlet. It begins on google: "yesod hamlet" does not yield any meaningful documentation.
Yes, documentation sucks, they're working on it.
> I like how you put thought into generating URLs, but thats nothing the templating language should take care of.
All the template does is provide some syntactic sugar with the @{...} notation. The actual URL generation is handled by the dispatch module entirely.
As for templating, shakespeare-text will do plain text, compile time templates. In general, as Greg has said, you can use anything you want.
Sorry for being unclear as well: I meant the initial reply by gregwebs but didn't want to start a second comment.
Thanks for the rest of your answers.
Okay, whats wrong with hamlet. It begins on google: "yesod hamlet" does not yield any meaningful documentation. "Shakespearean Templates" does. So "Shakespearean Templates"[1] is a whole family of languages that solves a lot of problems already solved, but type-safe. Well... okay, so I do not only have to learn a whole new framework, I also have to learn 3 new languages (-2, if I only care about HTML templating). So, to me, the whole approach rings a bit of "the world is wrong and we fix everything". Considering gregwebs answer: even more so.
Hamlet just doesn't suit my tastes. I don't like auto-closing tags on intendation - any decent text editor should assist you enough to do that properly. I like how you put thought into generating URLs, but thats nothing the templating language should take care of. Also, Hamlet assumes that you are templating HTML - I often template other types as well, for example plain text - hence a need for replacing it by something that fits all needs better. In the end, I also prefer strictly logic-less templates, so hamlet doesn't cut it.
Also, the documentation should see some love. There is no way to have a look at the features (and languages) in isolation: Its a stream of consciousness that introduces features in a half-sentence (I had to grep it to find what "^" means - it was what I expected it to be, but nevertheless).
That said, I still find Yesod a compelling framework and it will be the first haskell framework I'll try out next time I have some spare time. But the first thing I'll do is replace the templating.
[1]: I would prefer if they had anything to do with shakespeare, the esoteric programming language. ;)