I see from #362, #363 and #410 that a lot of effort was put into Markdown support. And #379 demonstrates that the fields have to be scrubbed anyhow. So, I am wondering if it is possible allow/configure HTML in all the applicable fields.

Without getting into it, I use HTML, Textile and Markdown (and various wiki syntaxes) habitually, but hardly anyone else I know does. All my cool friends know how to create an anchor element in HTML, though.

Of course white-listing elements is probably useful. I imagine that this could be configured with overrides, but it is fairly simple to find a reasonable default set of elements to allow.

Thoughts?

Riding on top of #689, it took me a while to figure out that Markdown could be used (after HTML and Textile, I ended up figuring it out from looking at closed issues). I don't have any particular suggestion, but maybe an info box on the side or the footer could indicate what can be used to format their text.

(this is to discuss this and then possibly implement it. Implementing is very easy).

Currently jinja2 replaces {{ not_known }} by the empty string. The question is, wether it would be better for it to throw an error? Rationale being: Either it's a typo, or it's an error for the variable to be referenced but not being there.

Does that make sense?

Enabling this:

mediagoblin/tools/template.py:
@@ -43,6 +43,7 @@ def get_jinja_env(template_loader, locale):

     template_env = jinja2.Environment(
         loader=template_loader, autoescape=True,
+        undefined=jinja2.StrictUndefined,
         extensions=['jinja2.ext.i18n', 'jinja2.ext.autoescape'])