Improved wikis with more markup options

By on January 9, 2013

Are you a Markdown wizard? Perhaps you have spent the last few years learning the ins and outs of reStructuredText.

Let’s be honest: when you know a markup language well, that’s what you want to use to create rich content.

Now, wiki pages on Bitbucket render Markdown, reStructuredText, Textile—and they’re still fluent in Creole. New wiki pages default to Markdown, but it’s easy to switch:

Even more improvements…

We’ve freshened up the look of our markup toolbar and added buttons to insert links and images into your pages. Now you have everything you need to write full-featured wiki pages. Just in case you can’t remember the syntax, the toolbar is available everywhere on the site where you can enter markup.  Even better, you can use the improved toolbar to preview wiki markup in any language with just one click.

We’ve also made it easier to manage your wiki directly from Bitbucket. You can now rename or delete pages right from the site. You can manage your files without having to clone the wiki repository  — but you still have the option to clone, if you prefer.

Git or Mercurial repositories continue to back our wikis. You can clone your wiki, compose with your favorite editor, and push your changed pages back up to Bitbucket.  Just make sure each page’s file uses the appropriate extension for your markup and Bitbucket will handle the rendering.



  • Dave
    Posted January 10, 2013 at 4:51 am | Permalink

    What are the appropriate extensions? e.g. Should markdown files have the extension .markdown or .md or something else?

    • Posted January 10, 2013 at 6:27 am | Permalink

      I’ve seen plenty of in my life.

    • Posted January 21, 2013 at 7:10 am | Permalink

      I am sticking with .markdown than of any other extensions. While .md is valid, but personally I have much feeling it’s a machine description file, because of my Linux background maybe 😛

  • Anonymous
    Posted January 10, 2013 at 4:53 am | Permalink

    Awesome sauce!!

    Can we set a default for a project? For one project we’d like all our pages to be in .rst by default.

    Also, there doesn’t seem to be an “editing help page” with instructions for .rst editing (or for the other non-creole formats).

  • Marius
    Posted January 10, 2013 at 5:14 am | Permalink

    Love to see markdown added and set to the default setting – thank you so much!

  • octopus
    Posted January 10, 2013 at 9:29 am | Permalink

    +1 for power rangers

  • Posted January 10, 2013 at 9:45 am | Permalink

    Thank you guys. Finally, reStructuredText everywhere!

  • David
    Posted January 18, 2013 at 2:06 am | Permalink

    Did you make changes in the API ? How to know what type of syntax used ?

  • Posted January 19, 2013 at 10:46 am | Permalink

    Could you add those markdown types to issues trackers, too?

  • Posted January 20, 2013 at 4:57 am | Permalink

    Would be great to get this on repository description field too!

  • Graham Hannington
    Posted January 28, 2013 at 6:30 pm | Permalink

    > Let’s be honest: when you know a markup language well, that’s what you want to use to create rich content.

    Have you had your mouth washed out by the Atlassian Confluence developers yet? 😉

    Or perhaps you guys (Atlassian) are fans of Walt Whitman: “Do I contradict myself? / Very well then I contradict myself, / (I am large, I contain multitudes.)”.

  • nothappy
    Posted February 6, 2013 at 8:53 am | Permalink

    If only we could also have MathJAX, the wiki would become useable by scientists

  • Anonymous
    Posted March 22, 2013 at 7:15 am | Permalink

    How do I link to another wiki page in markdown?

  • Dassburger
    Posted June 5, 2013 at 12:47 pm | Permalink

    What about markup for issues descriptions? Can I use Markdown there too?

  • Posted December 2, 2015 at 3:30 am | Permalink

    Would also be nice to have the possibility to display youtube and/or Vimeo videos