- **status**: in-progress --> review - **Comment**: Closed #804, #814. `ib/7897`
I needed to change editor code itself a bit, refer to `git show 2008f8d` for details. We probably shoud fork & contribute back to the editor, so it will be less painful to update editor in the future. Some places to check for QA: - comments and replies add/edit - ticket create/edit - wiki create/edit - merge request create/edit - blog post create/edit - discussion (aka forum) --- ** [tickets:#7897] Live syntax highlighting for markdown editing** **Status:** review **Milestone:** unreleased **Labels:** 42cc sf-8 ux sf-current **Created:** Mon Jun 15, 2015 02:30 PM UTC by Dave Brondsema **Last Updated:** Tue Jun 16, 2015 09:02 AM UTC **Owner:** Igor Bondarenko An editor like https://github.com/lepture/editor which shows some Markdown style rendering as you are editing (not full WYSIWYG though) could be very helpful. Demo at http://lab.lepture.com/editor/ We should figure out how to change the help & preview buttons to use our help & preview URLs. However I don't think we should try to customize the syntax highlighting for our customizations (e.g. `~~~~`, artifact links, etc) yet. Can be a followup ticket. I like this because it doesn't attempt to do a full WYSIWYG exact render, so we don't have to worry about some of our customizations. Yet it does do enough formatting that people will notice if they unintentionally cause formatting with a `_` or a `*`. And it even helps with the sneaky gotcha of a bullet list without a preceding blank line (it doesn't work, it is rendered as italics) (This idea came from discussion on [#6822]) --- Sent from forge-allura.apache.org because [email protected] is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
