How to make wiki markup your default Confluence editing mode

By Andrew Petro
May 27, 2008

This third post in a series on using Confluence effectively describes how to set wiki markup as your default editing format.

(In my first post in this series, I discussed the virtues of Tiny Links in Confluence, and in my second, I re-articulated a few searching hints.)

I feel strongly that most people editing Confluence pages would be best off using the wiki markup editing mode most of the time. Distinguishing between the semantic content of a document and the presentation of a document is a very powerful approach. Some other time I will subject my gentle readers to my rant on that approach generally.

Here, today, I'll just offer the quick tip on how to switch to this more civilized editing mode:

Here's what it looks like to edit a Confluence page in Rich Text mode with Rich Text selected as the default mode:

Screenshot fragment showing editing a Confluence wiki page in rich text mode

Here's what it looks like when you click over to the Wiki Markup editing mode.

Screenshot fragment showing editing a Confluence wiki page with rich text selected as the default mode but having clicked over into wiki markup mode, with an invitation to make this wiki markup editing mode the default mode

See that "Make Wiki Markup Default" text? Click it. That will set wiki markup as the default for your Confluence page editing.

I think in time using this approach makes people more efficient, more effective, and happier Confluence page editors. If you're looking to make this change, I hope this how-to helps you. If you're not yet sold on this change, I hope this how-to will help you give it a try.

Your Blogmaster:

apetro's picture

Andrew Petro

After graduating with a B.S. in Computer Science from Yale University in 2004, Andrew stayed on to serve his alma mater as a casual systems programmer with the Technology & Planning group. His interests include automated software testing, application frameworks, and electronic security. Projects in which Andrew has been involved include the Central Authentication Service, YaleInfo Portal (Yale's uPortal implementation). and the JA-SIG uPortal project. Andrew serves as the release engineer for uPortal 2.6.x (previously for 2.5.x) and has been published in the Communications of the Association for Computing Machinery on the topic of electronic voting. In fall 2005, Andrew relocated to Wisconsin and continued to work for Yale on a contract basis while starting part time with Unicon and in spring 2006 Andrew joined Unicon full time, serving roles since then including technical lead on Academus and on Cooperative Support for uPortal.