symposion_app/symposion/schedule
Sachi King a36ff64a82 Support monospace TextFields instead of Markdown
Drop markdown for monospace

With markdown, we're only allowing about 1/10 of what is possible.
This creates a false reality and expectation.  Lets not suggest this.
Nor do we have in-editor preview.  So the user has to save, look at it,
then go back and edit.  And seeing a bunch of sanitized HTML or just
missing sections isn't firendly.

Monospace, what you type, is what you're going to get.  It gives the
presenter enough power to build a readable abstract, but not so much
that they can break the page and it's CSS, nor the ability to confuse
onselve through not getting what you expect.

We keep bleach sanitation and we should probably run linkify on this in
the long term.  (Turn links into clickable links)
2017-05-07 13:22:28 +10:00
..
migrations Py2 compatability has been broke elsewhere drop it 2017-04-29 15:47:19 +10:00
tests Massively upgrade symposion 2015-10-16 12:37:35 -05:00
__init__.py Namespace the apps 2014-12-18 08:19:01 -06:00
admin.py Py2 compatability has been broke elsewhere drop it 2017-04-29 15:47:19 +10:00
apps.py Py2 compatability has been broke elsewhere drop it 2017-04-29 15:47:19 +10:00
forms.py Add a CSS class on required fields labels 2017-04-29 15:47:19 +10:00
helpers.py Py2 compatability has been broke elsewhere drop it 2017-04-29 15:47:19 +10:00
models.py Support monospace TextFields instead of Markdown 2017-05-07 13:22:28 +10:00
timetable.py Py2 compatability has been broke elsewhere drop it 2017-04-29 15:47:19 +10:00
urls.py Py2 compatability has been broke elsewhere drop it 2017-04-29 15:47:19 +10:00
views.py Py2 compatability has been broke elsewhere drop it 2017-04-29 15:47:19 +10:00