How closely does Podio use the Markdown spec?
Somewhere I saw a reference to this markdown spec:
I am trying to get a table to format in an item comment and it doesn't seem to work... are tables supported? Is there a list of items that are and are not supported?
Please sign in to leave a comment.
George, thanks for the reply! That would be awesome... I think this would help lots of people be able to supply better formatted comments... would help us tremendously within our API app... we want to use tables to show a different style comment and help differentiate it from all other comments so that it makes more sense to our users...
After you all discuss, can you let me know if this is something you will be turning on and when? thanks!
Actually you might well be the first one that attempted to format a table, most users are not even aware of markdown :) So it probably won't affect lots of people but if it's as easy to add as it seems I'll try to squeeze it in sometime soon and get back to you.
Markdown tables have been squeezed in. I just made the final changes. You will see markdown tables working after the next update of Podio. I believe this is scheduled for Thursday. :)
Let us know how it goes!
This is awesome!
I just discovered Markdown support by accident when writing private message. I typically use Markdown style formatting regardless to improve readability.... and it was parsed!
What a nice surprise. Where all can it be used? I see it doesn't get parsed on rich text fields.
It can be used most places where you write text, except for item fields. So it works in status posts, comments, task descriptions etc.
Hey guys I noticed this weekend my markdown is not being parsed by the iPad app correctly... Thx
Markdown rendering is not supported on the mobile platforms, it will just display the raw text. This is actually on purpose as there are no good ways of rendering markdown on iOS and Android. However markdown is specifically made to work and be readable in its raw form.
I don't understand what you mean by it isn't supported... I guess you can't display HTML in the app?
Anyway, yes this is true regarding the formatting unless you are formatting a table, images and links. Doesn't look good at all. Is there some way to support this?
There are ways to make this work, but they are not straight forward. To be honest Markdown is only used by a very small subset of our users, and while we do what we can to support it, we cannot spend more time on it than we already do.
Is there a reason you don't use a proper HTML editor for rich text like :
Some of my user would like to move content from webpages and word docs but markdown does not cut it.
We are actually using TinyMCE for the large text fields in apps. We believe a full text editor like that is overkill for comments and status messages.
It may be that other users don't have a need for it, but I find I am constantly trying to remember markdown and usually give up in frustration, despite having many comments/posts that really need it. The irony of this post, is that if I look at the bottom of this comment box, there is a very helpful and ample formatting toolbar that at the least would be helpful to implement in comments in Podio. I'm not saying we need kitchen sink here, but something would be of benefit to users. Our conversations often get very detailed and we'd love that ability along with easy link insertion. I assume though, that this isn't a podio based help system?
I wish Markdown was supported in text widgets...
Hey Podio developers...
I am getting more clients asking why our markdown links in PodioTools don't work on Android / IOS... can you please implement support for this on mobile...
I think if you are going to allow markdown, then you need to support it everywhere... :)
"I think if you are going to allow markdown, then you need to support it everywhere... :)"
I agree that supporting markdown only in some places is unintuitive and misleading. I would like to use markdown not only in comments and sidebar widgets but also in those large text areas with formatting toolbar. Being forced to format text in different ways depending on the place where it is entered is ridiculous.
What's even worse, I can create tables in comments etc. but I am unable to use them in the item descriptions (in the editor with formatting toolbar). Quite odd, don't you think?
I think the best solution would be to support markdown everywhere and use formatting toolbar only as a markdown inserting helper (see http://markdownpad.com/ for instance).
When are you going to make it more consistent?
We also like markdown, but we cannot in anyway have only markdown formatting.
It is a requirement to have a WYSIWYG editor in the large text fields. Having a WYSIWYG editor that produces markdown, would be great, but we have looked countless times to find such an editor that works properly in all browsers and have the required functionality.
What about thinks like (found at http://stackoverflow.com/questions/4843649/wysiwyg-edit-with-markdown-output):
The second one is quite smart in the sense that the toolbar is displayed when the editor is focused. It would perfectly fit your requirement of not cluttering the interfece with overusing formatting toolbars.
The last one is a script that could be potentially integrated with the editor already used at podio.
We care a lot about the experience of our users, and we work hard every day to make Podio better. I am extremely offended by your attitude and to think that a 5 minute Google search will bring solutions is ridiculous.
http://code.google.com/p/ittyeditor/ - A project that hasn't been modified in 5 years?
http://fguillen.github.com/MDMagick/ - A very basic editor that doesn't support IE
https://github.com/aaronsw/html2text - A tool to convert HTML to markdown. We already use this for some parts like HTML email replies to comments, but it has nothing to do with a WYSIWYG editor.
There are some promising tools out there like the new editor for Wikipedia, and the second we have one that is better than TinyMCE we will switch to that immediately. However your suggestions are not even close.
I have to take Christians side on this. WYSIWYG-editors are usually a pain in the ass to work with. Podios editor is so far the best I've seen. Probably because of the simple design and low number of options and functions. There has been some discussion on my article about Markdown as well. http://www.podiohelp.com/rich-text-formatting-in-podio-ui/#disqus_thread
Both the wordpress editor AND Google Docs lacks table support. And yes, you can install a plugin for table support in WP but it's almost impossible for a non-tech user handle (in my experience). I've also used Mindtouch (FCK editor) that has table support. This editor is actually so bad we've had people that refuse to use it. I think that's exactly what Podio wants to avoid.
Forgive me for writing this but this discussion only relates to super user concerns, and Podio isn't really focused on the super users right? I'm relieved that Podio sticks to what it believe is the right for the user, much like Apples "We don't let you do that because we think it would suck." attitude, and doesn't listen to much for all the feature requests coming from us super users.
Christian, I am very sorry if you have felt offended by my suggestions. This was absolutely not my intention. I apologize for being so pretentious. I do appreciate your work and I think you are great people making a really great product!
Well, I too much focused on markdown support and underrated the need for WYSIWYG editor for non-technical people (thanks Carl for making it clear to me).
The main thing I was concerned about was actually the inconsistency between ability to use markdown in comments etc. and inability to use it in large text fields. Unfortunately, the problem seems to be harder than I thought.
Just want to give you Christian a tip: http://imperavi.com/redactor/
I've tried it all little and it seems pretty nice, probably you have already seen this but if you don't, this could be worth a test.
Also, I forwarded an email to podio which had a markdown formatted horizontal ruler "----" which was parsed into a html horizontal ruler in the editor on Podio.com.
Can you confirm this Christian?
Is it possible to include Markdown support in the profiles? We are using a Click to Call SIP solution, and having the link be formatted as "John Public" instead of "sip:email@example.com" would make the company directory pretty useful. Also the ability to include more than one field as the default view in the Employee Directory could make this even easier!! (podio.com/employeenetwork/members).
It's currently not possible to use markdown in your profile, but that might be something we should consider for the future.
All the best,
Hi guys and have a good week.
Can we use markdown tables in calculation fields.?
As I read here in this post, yes we can use it. But my calculation field doesn't support. Am I wrong or..?
TinyMCE sports quite a few features that I think would resolve most of the issues people are describing in this thread. Is it possible to turn on support for Tables and Source Code?
Source Code in particular allows me to convert my markdown into html locally with pandoc and paste it into tinyMCE. Then any tables I have could be edited with the Tables features.
I'm specifically talking about the text area widget.