sadly, enterprise software isn't driven by users...

It would be great if you reconsidered you're decision to ignore markdown. Even better would be an integration with Bitbucket readme.md. As a developer I want my documentation close to the code. It's hard enough to keep it in sync in one tool. But having to switch to another one makes it even hard.

Your technical dificulties to introduce the xhtml kind self made syntax is not an argument against the simple to use and defacto standard markdown. After acquisition of github by Microsoft i think, it is not a good idea to ignore the popularity of Markdown. The plugin is not an option for someone who writes quickly a meaningful nice looking technical documentation.

Regards, Gena

PS. We need the kind ghpages features in our confluence to be happy with it next years and recommend it to our customers.

And there is also a supported (licensed) add-on: Markdown for Confluence written independently but based on the same underlying library.

We have released an unsupported macro to help with this. https://marketplace.atlassian.com/plugins/com.atlassian.plugins.confluence.markdown.confluence-markdown-macro

+1, reopened: CONF-27030

http://www.codinghorror.com/blog/2012/10/the-future-of-markdown.html

That's really sad. I'm sure at east most developers would love to see markdown support. You should be able to support multiple storage formats..

Hi Phil,

Thanks very much for taking the time to give us your idea.

As you may have read, we recently removed wiki markup from Confluence 4.0 and now use an XHTML based syntax for storing pages which can be edited in the new RTE.

This was a pretty big decision and a massive technical change that gives us the capability to deliver a LOT more functionality in the editor. Unfortunately for your request though this means we won't be looking into changing to markdown or any other storage format soon.

Regards,
John