Opened 13 years ago

Last modified 11 years ago

#351 accepted enhancement

Markdown editor

Reported by: Tryggvi Björgvinsson Owned by:
Priority: trivial Milestone:
Component: programming Keywords:
Cc: Parent Tickets:


Add a markdown editor for textareas which use markdown (to improve
user experience). Solutions exist under *possibly* free licenses.
Most are based off StackOverflow's reversed engineered WMD editor
(which might or might not be under a free license). Original
reverse engineering project:
` <>`_
(with 112 forks)

So implementation is in three steps:

-  Check with lawyers about possible implications of using a
   reverse engineered WMD editor version
-  If OK, find a good fork which suits MediaGoblin's needs
-  Find all markdown input fields in code and add the editor (along
   with tweaking and making it pretty)

Change History (5)

comment:1 by maiki interi, 13 years ago

Based on `#689 </issues/689>`_, I think this should be plugin,
which means that we probably need a way to determine which fields
can accept Markdown.

Also, we may not need to look to some that is Markdown specific. We
probably won't need the entire range of options, and can probably
get by with a set similar to the one Redmine uses (see the above
workbar when updating or creating an issue).

As far as I can tell, the description and the comment field are the
only ones that accept Markdown, though I haven't tested titles.
Does anyone have a definitive answer on that?

comment:2 by Will Kahn-Greene, 12 years ago

The original url for this bug was .

comment:3 by joar, 12 years ago

Component: programming

A Markdown editor I like:

However I'm unsure if it will fit UX-wise. It seems only possible to either switch between rendered and source, or have them side by side in fullscreen. Perhaps do a StackOverflow and put the rendered content below the source. Will it be handled effectively?

Speaking of StackOverflow, they're using PageDown which is available at

comment:4 by Jakob Kramer, 12 years ago

Type: defectenhancement

comment:5 by Emily O'Leary, 11 years ago

I think this relates with my recently completed patch on #492. It gives you direct feedback but doesn't have any editing tools available.

Note: See TracTickets for help on using tickets.