Brion Vibber wrote:
The ideal markup situation for the article namespace is that markup shouldn't even *be* exposed to most users. A long-term goal is migration to a more WYSIWIG-like editing experience -- to which one of the potential stumbling blocks has been "but how will we do templates, which currently are built with our horrifying wiki markup?"
Since templates forbid looping, whatever manages it can't be considered a programming language (missing iteration in {sequence, selection, iteration}).
Perhaps we should consider this a markup problem and not a programming problem. If templates have styles (not to be confused with CSS concepts necessarily) then we just describe the template instead of program the template. {{{var}}} can become something like content: in CSS. Conditionals are... interesting. Apply style x if the condition satisfied else apply style y (.e.g display: "nicely"; vs display: none;)
Just an idea...
Mike