Macdown feature requrest full#
Macdown feature requrest code#
Macdown feature requrest professional#

Give me a plain text editor any day, where I can type what I actually mean to produce. Now, the beauty and great usefulness of markdown is that even when displayed non-richly, it’s meaningful… but it’d be really nice if it displayed richly

I absolutely will never remember that Ctrl+Shift+Somethingorother is for bulleted lists, and I’ll never take the time to look it up – I’ll just start a line with *. Here’s another vote strongly requesting Markdown support! Many developers (myself included) are very used to markdown… just working. PS: Thank you for considering our suggestions! Applying this to Asana objects wouldn’t be confusing, in fact, I think most people would expect it to work that way Github adds more shortcuts, such as auto-linking of issues by prefixing their ID with a hash (e.g. These users apparently don’t know (or as in my case can’t use) the shortcuts provided and would generate nicely formatted content anyway.Īlso, developers are quite used to platform-specific markdown “extensions”, the prime example being Github Flavoured Markdown. In these cases, “accidental” markdown usage would actually be very nice. In fact, most of our non-dev team unintentionally uses markdown for comments and descriptions, such as lists prefixed with * or. If you’re wondering: markdown is very easy to learn, much easier than custom shortcuts (in my opinion). This is true for my custom X11 keyboard layout (Linux), so currently I can’t use bullet lists or monospace at all. Some shortcuts may not work on international keyboards. To add to this, as you mention in the Shortcuts FAQ: Links are also important in order to support non-http protocol links (like evernote:// and trello:// or even message: ) – which are very important if you want to create an efficient mobile workflow etc. Especially the ability to specify links is important as just a couple of bloated gDoc-links will totally destroy the readability of any description.

Macdown feature requrest code#

Our primary use for markdown is the ability to make the descriptions more easily readable by adding titles and subtitles (#, #, …), lists (*), code snippets (``) and links in a consistent and non-guessy way.

Macdown feature requrest professional#

So in our opinion you really, really, really should support markdown as soon as possibly in order to stay relevant in the professional commuity. If you still need convincing then try watching this Google Trend graph for the term “Markdown”:Īs you can see markdown isn’t a shortlived fad that will go away anytime soon – on the contrary it’s an integral part of the major “content as code” megatrend, that is coming to all kinds of professional services these years. The only other “professional level” feature I’ve noticed that you’re missing is ticket numbering – which we as a small company can currently live without (but I think it should be an option to turn it on anyway). (I apparently simply couldn’t imagine that a mature and popular task management system like Asana didn’t didn’t support that – so I didn’t even think of checking that as the first thing in my research…)Īll of your major competitors that we know of and use regularly supports markdown: Trello, Jira, Assembla, Trac… etc.

Macdown feature requrest full#

I’ve just spent 2 days evaluating a full switch to Asana for a most of our systems (task management, lead management (CRM) and team productivity etc.) just to end up concluding that Asana could do anything we needed – except support consistent text markup! Lack of markdown is a showstopper for us here at Things in Flow too. We switched from Skype to Slack for several reasons at our company, but the ability to pass each other code snippets in chat, and have it be as readable as in an IDE, was a strong get for to chip into the choir:

Most importantly, I want to be able to embed language-specific syntax-higlighted code into my Asana descriptions and comments.

They type pretty fast, and they’re used to typing in source code to get rendered output. I’m guessing a fair amount of your user base are developers. I fight with it as much or more than I used to fight with Microsoft Word’s intelligent formatting. In particular, Asana’s bulleting system is painful to work with.

I want to be able to type in a window, and not have Asana “correct” my “mistakes”.

I want a text format that can be rendered in an environment other than Asana.

I want to be able to copy and paste from a markdown document directly into an Asana task.

I want to use a couple of backticks, and call it good.

I don’t want to use keyboard shortcuts and highlighting snippets of text to make something monospace.