Markdown support for graphs plantUML and or mermaid

618 views
Skip to first unread message

Luke Ashe-Browne

unread,
Jan 15, 2017, 12:05:54 PM1/15/17
to taigaio
It would be fantastic if Taiga could render markdown extensions that allow graph syntax rendering,  Both wiki's and ticket's could include versioned graph definitions for seuqence and flow diagrams, gant charts and anything you can do with PlantUML. 
Mermaid and Plant/Smart UML extensions are becoming popular in tools like Atom's Markdown-Preview-Enhanced, Typora, stackedit.io and many others.

It would be an amazing advantage to Tiaga to allow this graph rendering.

What would have to change to allow it?


Otherwise, would it be possible to find a chrome extension, or just an additional JS library to be included in the html to view the graph renderings?

gitlab is discussing switching to a library that enables extensions, kramdown, but this is a ruby library, not python. the waylan/python-markdown allows extensions. Though i dont have a full understanding of  what changes would have to be made ro what the implications would be to existing formats of markdown in use.

What are the options long and short term?

Alejandro Alonso

unread,
Jan 16, 2017, 4:54:15 AM1/16/17
to Luke Ashe-Browne, taigaio
Hello Luke,

I've just created and enhancement request based on your feedback: https://tree.taiga.io/project/taiga/issue/4888

Right now we have added a new rich/visual editor so it won't be easy to achieve including it in taiga core, it would require changes in both taiga-back and taiga-front. A browser extension will probably be a more viable option.

Regards,


--

  
Alejandro Alonso Fernández
CIO & Co-founder
www.kaleidos.net/FC8EAC/

lukas

unread,
Jan 16, 2017, 5:55:36 AM1/16/17
to Alejandro Alonso, taigaio
That's great, thankyou. 
Not sure how long such change might take to become a reality, but it would be really useful powerful feature. Yes, Gitlab has the same issue in terms of prerequisites to get front and backend changes made, they are trying to maintain github flavour markdown feature parity with their effort, i think their main issue is kramdown doesn't support task lists yet, though the kramdown ticket on task lists looks like it has gitlab contributors now trying to implement it. 

The rich text editor, that is part of the upcoming 3.1.0 release? There's no date on that. But extensions graph extensions to markdown are done through the tripple backtick preformatted text blocks. if the rich text editor can support allowing extensions in the header line of preformatted blocks then it could be possible without hindering the rich text editor enhancement?

Luke Ashe-Browne
M: +44 (0)77 1728 0386

Alejandro Alonso

unread,
Jan 17, 2017, 3:23:05 AM1/17/17
to lukas, taigaio

Not sure how long such change might take to become a reality, but it would be really useful powerful feature. Yes, Gitlab has the same issue in terms of prerequisites to get front and backend changes made, they are trying to maintain github flavour markdown feature parity with their effort, i think their main issue is kramdown doesn't support task lists yet, though the kramdown ticket on task lists looks like it has gitlab contributors now trying to implement it. 

We (the taiga development team) were talking about this yesterday and it didn't look easy to make our actual implementation supporting extensions (but we would love supporting them), we would need some deeper work to really know what and how could be implemented.
 
The rich text editor, that is part of the upcoming 3.1.0 release? There's no date on that.

Yes, it will be part of the next release. There is no final date but will probably be at the beginning of february.

Reply all
Reply to author
Forward
0 new messages