Rich Text Functionality being enabled for Akvo RSR Updates about akvo-rsr

[adriancollier]

BAsed on the conversation we had in the RSR Discussion meeting today, we think that providing a full featured box is risky in terms of layout, and also complicated in terms of usability.

It makes a lot more sense to add something like this:
http://openedweb.com/blog/wp-content/uploads/2008/08/tinymce_default.jpg

This allows us to offer and limit functionality we want to allow or restrict.

I'm hoping that this change would not incur a significant increase in time required to implement...

[zzgvh]

I'm getting conflicting messages here. Markdown or widget? They are fundamentally two different ways of solving the problem.

[adriancollier]

The problem with Markdown is the extra documentation we would need to provide to show people how this can be used.

By adding in a Rich Text formatting frame, we can make this a lot simpler for our partners.

This also allows us to retain control over the update's visual layout, and we can prevent people from embedding videos and other clever stuff which could be possible in markdown causing us to fix or amend updates that don't look right on the screen.

Unless there's something else missing from the discussion - then we should go with Rich Text over Markdown.

[zzgvh]

Assigning the issue to you Daniel, to look at the small fixes needed in the css when markdown renders

tags where there previously were none.