Closed amickan closed 1 day ago
Using MarkDown for pages has been on my mind for a while. I think it is nicer and you can use full html. However, taking the existing pages and putting them into the MarkDown editor will make them really difficult to modify. We could try adding pandoc to convert the HTML to MarkDown and seeing what the result is like, but for some pages it might be manual work (which given we have more than 2000 may be a problem).
I think if we were to modify this we would need to have an opt-in to MarkDown for existing pages, but new ones could be created with that setting being true.
Along with the pages we also use summernote in:
\$
and \<
in generated markdownA similar migration process would need to be followed for those.
The markdown editor for pages should:
Describe the bug Our summernote editor for challenge pages doesn't correctly align text.
To Reproduce Steps to reproduce the behavior:
Expected behavior The text should be justifed.
Additional context It turns out that if you use the editor for justify full <p align="justify“> is added to the html code, which is obsolete. If you change it to <p style="text-align: justify;“> everything works fine.
It looks like django-summernote is no longer maintained. Maybe it would make sense to switch to our markdown editor for challenge pages instead?